Purpose-built tool
Ad slot verification tool — check what's actually on the page
AdsChecks loads your target URL in a real GEO context, inspects your predefined ad slot selectors, captures a full-page screenshot, and returns a structured evidence bundle you can use for QA, commercial review, or dispute support.
3-day free trial · No charge until day 4 · Cancel any time
What is ad slot verification?
Ad slot verification is the process of checking whether an ad placement on a web page is actually rendering — in a specific GEO, on a specific device, at a specific point in time. It is distinct from ad fraud detection (which targets invalid traffic) and from ad serving analytics (which tracks impressions in aggregate). Verification answers a simpler, more direct question: is this slot rendering right now, in this context?
Without a dedicated tool, teams rely on manual screenshots, VPNs, and informal reports from partners. These methods produce inconsistent evidence that is hard to compare across runs and difficult to share in a structured format. A purpose-built ad slot verification tool replaces this manual workflow with repeatable, structured checks that produce the same output every time.
What a verification check includes
A single verification run in AdsChecks covers:
- Page load — the target URL is loaded in a Chromium-based environment with the selected GEO proxy and device emulation active
- Slot inspection — up to 5 predefined CSS selectors are checked for presence, visibility, and render state
- Screenshot capture — a full-page screenshot is taken at check time and stored as part of the evidence bundle
- Status assignment — each slot receives a status code:
OK,SLOT_EMPTY,CHALLENGE_DETECTED, orBLOCKED - Metadata output — a JSON file is generated with selector data, viewport dimensions, GEO context, and a UTC timestamp
- Evidence bundle — all artifacts are packaged into a downloadable ZIP
Why teams use an ad slot verification tool
Ad slot delivery problems are common and often go undetected until a billing dispute or a missed campaign target surfaces them. The core problem is that ad rendering is context-dependent: the same page can serve ads correctly in one region and return an empty slot or a blocked page in another. Without systematic verification, this gap is invisible.
Billing disputes
When a publisher reports full delivery but a buyer sees empty slots, neither side has consistent evidence. An ad slot verification tool produces timestamped screenshots and JSON metadata from the exact GEO and device context in dispute — giving both parties a documented record to work from instead of conflicting reports.
Pre-launch QA
Before a campaign goes live, ad ops teams need to confirm that slots are rendering in all target markets. A verification run across 6 GEOs and 2 device types takes minutes and surfaces configuration issues — a misconfigured selector, a WAF blocking a specific IP range, or a slot that renders on desktop but not mobile — before spend begins.
Scheduled compliance audits
Publishers and agencies with ongoing agreements need repeatable proof that slots are
delivering as contracted. Scheduled verification runs produce a consistent evidence
record each cycle. Diff reports flag regressions between runs — a slot that was
rendering last week and is now returning SLOT_EMPTY is immediately visible.
Publisher delivery documentation
Publishers can use ad slot verification to proactively document delivery on their own properties — providing advertisers with structured proof rather than relying on dashboard screenshots that are difficult to verify independently.
How the AdsChecks verification tool works
Define a check template
Set a target URL, select a GEO region and device type, and specify up to 5 CSS selectors for the ad slots you want to verify. Templates are reusable — define once, run manually or on a schedule.
Run the check
AdsChecks routes the request through a residential proxy in the selected GEO, loads the page in Chromium, and inspects each slot selector. The check completes in seconds to a few minutes depending on page complexity and GEO routing.
Review the evidence bundle
Each check produces a full-page screenshot, per-slot status codes, a JSON metadata file, and a UTC timestamp. The complete bundle is available for download as a ZIP. Results appear in the dashboard immediately after completion.
Compare, export, or escalate
Use the diff view to compare any two runs side-by-side. Export the evidence bundle for use in dispute documentation, publisher reporting, or internal QA records.
Ad slot statuses explained
AdsChecks returns four status codes, each representing a distinct verification outcome. All four are valid results — they describe what happened on the page at check time, not whether the tool succeeded or failed.
For the full status model documentation, see the Status model page →
Who uses an ad slot verification tool
Confirm that bought placements are actually rendering on publisher pages. Use geo-routed checks to verify delivery in specific target markets. Produce timestamped evidence for billing review when delivery reporting doesn't match observed performance.
Run pre-launch verification across all target GEOs before campaign spend begins. Schedule recurring checks during campaign flight. Use diff reports to catch regressions between runs. Manage verification across multiple clients and domains under one account.
Verify that ad slots are rendering as configured across regions and device types. Proactively document delivery on your own properties. Identify configuration issues — blocked GEOs, empty slots in specific contexts — before advertisers raise disputes.
Verify placement compliance across publisher networks. Use repeatable checks to compare expected vs observed slot state. Produce structured evidence for partner reviews rather than relying on one-off screenshots.
Frequently asked questions
What is an ad slot verification tool?
An ad slot verification tool checks whether ad placements on a web page are rendering — in a specific GEO, on a specific device, at a specific point in time. It loads the target URL in a controlled environment, inspects predefined CSS selectors, captures a screenshot, and returns a structured evidence bundle with status codes and metadata.
How is ad slot verification different from ad fraud detection?
Ad slot verification confirms whether a slot is present and rendering on a given page at check time. Ad fraud detection looks for invalid traffic, bot impressions, and click fraud. They solve different problems — verification is about placement delivery and page state; fraud detection is about traffic quality.
Can I verify ad slots across different GEO regions?
Yes. AdsChecks routes checks through residential proxies in 12+ regions. You can run the same check from US, UK, DE, JP, and other GEOs to compare slot rendering across markets — or to isolate delivery issues that only appear in specific regions.
What statuses does an ad slot verification tool return?
AdsChecks returns four statuses: OK (slot matched expected selector and state), SLOT_EMPTY (selector found but no ad content at check time), CHALLENGE_DETECTED (anti-bot interstitial was returned instead of the page), and BLOCKED (access was prevented in the target GEO or environment). All four are valid, documented outcomes — not tool errors.
What evidence is captured per check?
Each check produces a full-page screenshot, per-slot status codes, JSON metadata with selector data and viewport information, and a UTC timestamp. All artifacts are bundled into a downloadable ZIP for sharing with ad ops, publishers, or legal teams.
How many ad slots can be verified per page load?
AdsChecks verifies up to 5 predefined ad slot selectors per page load. If you need to check more slots on the same URL, you can run multiple checks with different selector sets.
Can I schedule recurring verification checks?
Yes. Checks can be scheduled to run daily or weekly. Each run produces a fresh evidence bundle. The diff view lets you compare any two runs side-by-side to surface regressions between check cycles.
Can I share or export verification results?
Yes. Every run produces a downloadable ZIP evidence bundle — slot statuses, full-page screenshot, and JSON metadata — ready to attach to a dispute, send to a publisher, or archive in your own records. The diff view lets you compare any two runs side-by-side for before/after documentation.
Start verifying your ad slots
3-day free trial. No charge until day 4. Starts at $39/mo.
3-day free trial · Cancel any time