AdsChecks

Verification outcomes

Ad Verification
Status Model

AdsChecks statuses describe what happened during a completed check — not a marketing interpretation of delivery.

OK SLOT_EMPTY CHALLENGE_DETECTED BLOCKED
OK

Slot matched expected selector

The slot was found, visible, and matched the predefined selector and state at check time. This is a confirmed delivery signal for the selected GEO and device context.

Positive match
SLOT_EMPTY

Slot selector matched, no ad content

The selector resolved on the page but no ad content was present at check time. The slot exists but is not delivering in this context.

Empty or missing
CHALLENGE_DETECTED

Anti-bot challenge or interstitial page

An anti-bot challenge (Cloudflare Turnstile, hCaptcha, JS challenge) was returned instead of page content. Screenshot and metadata capture the challenge event as evidence.

Blocked context
BLOCKED

Access blocked in target environment

The CDN or WAF denied access from the check's GEO region or IP range. This is evidence that the ad is not being served to that audience segment — commercially relevant information.

Blocked context

CHALLENGE_DETECTED and BLOCKED are valid verification outcomes, not platform errors. Both are billable because the page load was completed and evidence was captured.

Full scope of what each check includes →

Recovery path for BLOCKED & CHALLENGE_DETECTED

If you see these statuses repeatedly for a specific GEO:

01
Review the screenshot evidence — it shows exactly what was returned at check time
02
Share the report with your publisher or ad ops contact as documented proof
03
Re-run the check after a configuration change to confirm resolution
04
Use the JSON metadata to cross-reference with your campaign delivery logs

For persistent access issues in a specific region, contact us — some environments require check configuration adjustments.

Ready to verify your ad slots?

Start a 3-day free trial — no charge until day 4.

3-day free trial · Cancel any time