Ad Embed Shows But Zero Credited Impressions: Fix Guide

An ad embed zero credited impressions dashboard is one of the most common support tickets on adult exchanges — and the fix is usually simpler than publishers fear. Your script loads, the page looks fine, but credited views stay at zero. This guide covers hourly caps, domain verification, referer checks, bot filtering, viewability rules, and how to test without burning your own credits or polluting analytics.

Start with the embed fundamentals in how to add ads to an adult website. If the Network tab shows no request to adswapx.com/embed/, fix installation first. If requests return 200 but credits never arrive, continue below.

How credited impressions actually work

Exchanges do not count every page load as a billable impression. A credited view typically requires: verified domain, matching referer, human traffic passing bot filters, ad unit meeting viewability thresholds, and no hourly cap violation. Popunders credit on qualified opens after user interaction, not on script load alone.

Banner embed pattern on AdSwapX:

<script async src="https://adswapx.com/embed/YOUR_SITE_KEY.js" data-type="banner"></script>

Popunder uses the same URL with data-type="popunder". Both formats share verification and referer rules. Misconfigured data-type may load but not credit the format you expect in reporting.

Domain verification must be complete

Until adswapx-verification.txt is reachable at your public root and marked verified in the dashboard, impressions will not credit — even if you see a preview creative during development. Re-verify after DNS migrations, CDN changes, or moving from staging to production.

Staging domains almost always cause zero credits when production tags are pasted on staging.example.com. Register each hostname separately or restrict embeds to production templates only. Referer details: referer mismatch fix guide.

Self-traffic, hourly caps, and testing hygiene

Exchanges dedupe publisher self-traffic. Refreshing your own site fifty times from the same IP will not produce fifty credits — and should not. Hourly caps prevent inflation and fraud. Use these testing rules:

• Private/incognito window on a different network (mobile hotspot works).
• One banner test: scroll unit into view for two seconds, wait five minutes, check dashboard.
• One popunder test: single click, confirm background tab, wait before retesting.
• Do not ask staff to hammer the homepage for "testing."

VPN and datacenter IPs are often filtered entirely. If your office routes through a corporate VPN, tests may always show zero. Read VPN and datacenter traffic impact for publisher context.

Viewability and placement issues

Banners below the fold that users never scroll to may not credit. Containers with zero height, overflow:hidden clipping, or opacity:0 fail viewability checks. Lazy-load wrappers that never hydrate also produce zero credits despite a successful script download.

Fix placement before assuming network failure. Our banner ads not showing guide overlaps here — blank slots and zero credits often share the same root cause. Optimize zones using how many ad zones recommendations.

Bot filtering and invalid traffic

Crawlers, uptime monitors, and scrapers load pages without crediting. That is correct behavior. Sudden zero-credit periods on otherwise healthy sites sometimes indicate a traffic quality flag — review spikes in datacenter GEO or referer-less hits in analytics.

Honest publishers benefit from strict filtering; it keeps advertiser demand high and fill rates stable. Learn more in adult site traffic quality and how exchanges protect both sides of the market.

Timing: when numbers should appear

Credited impressions usually show within one to five minutes. Reporting lag beyond thirty minutes with clean off-network tests indicates configuration error, not delay. Check dashboard filters — ensure you selected the correct site_key and date range.

Popunder credits may batch differently than banner impressions. Compare per-format charts if your exchange splits reporting. Mobile popunders credit less frequently than desktop; see mobile popunder fixes.

Infrastructure blockers: CSP, Cloudflare, Nginx

A script that loads but cannot beacon back to the exchange API produces zero credits. CSP connect-src must allow the ad network domain. Cloudflare Rocket Loader reorders scripts and breaks interaction-based pops. Page Rules caching HTML with stale site_keys cause mismatches.

Stack-specific fixes: Cloudflare and ad scripts, Nginx configuration for ad embeds.

Frequently asked questions

Why does my embed load but impressions stay zero?

Often the domain is not verified, the page URL does not match the registered host, you are testing from a blocked IP, or the unit never met viewability rules (banner in viewport ~1s). Work through verification, referer, and testing hygiene before opening a ticket.

Does refreshing my own site count impressions?

Exchanges dedupe publisher self-traffic and apply hourly caps. Use incognito and a different network for realistic tests. Staff refreshes do not represent monetizable inventory.

How long until impressions appear?

Usually within 1–5 minutes. If still zero after 30 minutes with clean off-network tests, recheck verification and referer. Then inspect CSP and Cloudflare settings before assuming platform outage.

Once credits flow, optimize RPM with RPM increase tactics and the credit-based exchange model. Join AdSwapX to verify your domain and confirm credited impressions in your publisher dashboard.