Discovery
Slot discovery scan
Automatically detect ad slot selectors on any page before setting up a template. No manual DOM inspection or CSS selector hunting required.
For affiliate managers, media buyers & publishers
Verify your ad slots with screenshot proof — across any GEO and device.
Know exactly what runs on your pages — verified with screenshots, status codes, and JSON metadata captured in real GEO and device context. Up to 5 slots per page load.
3-day free trial · No charge until day 4 · Cancel any time
World map for geo verification coverage
Why proof matters
Why ad slot QA fails without proof
Verification breaks down when geo, device, and slot state shift faster than a team can document them.
Coverage
Geo uncertainty
Ad slots render differently across countries, devices, and sessions. What passes QA in one region fails silently in another.
Trust
Disputes without evidence
Without consistent proof, QA findings are hard to share, compare, or escalate. Screenshots and metadata reduce ambiguity.
Time
Operational drag
Manual checks take time and still leave gaps in coverage and repeatability. Templates and structured runs remove repeated setup work.
Evidence scope
What we check
Each verified page is constrained on purpose: one completed page load, selected context, and up to five predefined slots.
Verification layer
Slot presence and visibility
- Slot detected on page
- Position and layout context
- Visibility state — visible, partial, or missing
Predefined selectors, not discovery scanning.
Context layer
Geo and device coverage
- Region-specific render checks
- Desktop and mobile snapshots
- Viewport and breakpoint metadata
Runs stay tied to the selected context for comparison.
Artifact layer
Evidence bundle
- Screenshots for each slot
- JSON metadata and timestamps
- Export-ready ZIP bundle
Consistent outputs across all runs, reviews, and disputes.
Ops layer
Operational integrity
- Repeatable checks from templates
- Clear issue flags and statuses
- Structured results for export
Built for repeatability, not one-off screenshots.
Template → Run → Evidence
How it works
The workflow stays compact: define the check context once, run it manually or on schedule, then review a structured evidence package.
Template
Define the check context
Provide URLs, slot selectors, device, GEO, and optional proxy routing settings.
Run
Execute manual or scheduled
Run a manual check or schedule it. Each page load becomes one verified page.
Evidence
Review the evidence bundle
Output includes slot statuses, screenshots, JSON metadata, and a timestamped evidence bundle.
Evidence bundle
Structured proof on every run
Every run produces a consistent output — slot statuses, full-page screenshot, JSON metadata, and a UTC timestamp — regardless of what you find.
{
"check_id": "chk_8f3k2x",
"url": "https://publisher.example/article",
"geo": "US",
"device": "desktop",
"timestamp": "2026-03-15T09:22:41Z",
"slots": [
{
"selector": "#div-gpt-ad-header-0",
"status": "OK",
"dimensions": "970x250"
},
{
"selector": "#sidebar-ad-300x250",
"status": "OK",
"dimensions": "300x250"
},
{
"selector": "#sticky-footer-ad",
"status": "SLOT_EMPTY",
"dimensions": "728x90"
}
],
"evidence": {
"screenshot": "chk_8f3k2x/full.png",
"zip": "chk_8f3k2x/bundle.zip"
}
}Platform capabilities
Everything you need for repeatable ad slot QA
Slot discovery, scheduled runs, and GEO-routed checks — one platform, structured evidence every time.
Automation
Scheduled runs
Set weekly or daily schedules. Checks run automatically and produce a fresh evidence bundle every cycle.
Coverage
GEO-routed proxy
Verify from US, EU, APAC and other regions. Isolate geo-specific delivery issues with residential proxies.
Analysis
Result diff
Compare any two runs side-by-side. Spot regressions, slot drops, or layout changes between cycles.
Ready to see exactly what runs on your pages?
3-day free trial · No charge until day 4 · Cancel any time
Pricing plans
Pricing plans
Public pricing, self-serve checkout. No sales call. No enterprise contract.
Starter
$ 39 /mo
500 verified pages / month
- 500 verified pages/month
- Scheduled runs
- No GEO routing
- Screenshots + JSON evidence
- Cancel any time
- No overages — runs pause at limit
GEO routing from Growth — $79/mo →
Start free trial3-day free trial · No charge until day 4
Growth
$ 79 /mo
1,000 verified pages / month
- 1,000 verified pages/month
- Scheduled runs
- GEO routing included
- Screenshots + JSON evidence
- Cancel any time
- No overages — runs pause at limit
3-day free trial · No charge until day 4
Standard Most popular
$ 149 /mo
3,000 verified pages / month
- 3,000 verified pages/month
- Scheduled runs
- GEO routing included
- Screenshots + JSON evidence
- Cancel any time
- No overages — runs pause at limit
3-day free trial · No charge until day 4
Custom Higher-volume usage and commercial workflow scoping.
Contact us → Full details: pricing page · what we verify · refund policy
Common questions
FAQ
Answers to the most common questions about verification scope, billing, and setup.
What counts as a verified page?
One completed page load for a target URL in a selected check context (GEO + device), with verification of up to 5 predefined ad slots. Each verified page produces statuses, screenshots, JSON metadata, and a UTC timestamp.
What happens if my page has more than 5 ad slots?
Each verified page checks up to 5 predefined selectors. If you need to verify more slots, you can run multiple checks with different selector sets for the same URL.
When does billing start?
All plans include a 3-day free trial. Billing starts on day 4 after you complete checkout. Your full monthly capacity is available immediately — no approval step required.
What does BLOCKED or CHALLENGE_DETECTED mean?
Both are valid verification outcomes, not platform errors. CHALLENGE_DETECTED means an anti-bot page (Cloudflare, hCaptcha) was returned instead of the page content. BLOCKED means the CDN denied access from that GEO or IP range. Both are billable because the page load completed and evidence was captured — the result itself is the finding.
How fast do results come back?
Most runs complete in under 2 minutes. Results appear in the dashboard immediately after the run finishes. There's no batch delay.
Can I use AdsChecks for multiple clients or domains?
Yes. You can run checks across any number of domains and URLs within one account. Each check is scoped to a specific URL and context — which makes AdsChecks practical for agencies managing verification across multiple publisher or advertiser accounts.
More questions about access, result speed, supported devices, or refunds: see the full FAQ.
Access
Start your free trial
3-day free trial on all plans. No charge until day 4 — account ready in seconds.
Select a plan, complete checkout, and start running verified ad slot checks. Provisioned immediately after payment.
01
Sign up
Create an account with Google and select a plan — Starter, Growth, or Standard.
02
Complete checkout
Secure checkout via Paddle. Cancel any time from your billing dashboard.
03
Start verification
Run checks and review statuses, screenshots, and JSON metadata in the evidence bundle.
Start free trial
3-day free trial · No charge until day 4
Custom volume or enterprise setup — contact sales.
Real scenarios
Where teams reach for AdsChecks
From pre-launch QA to billing disputes — teams use AdsChecks when a screenshot and timestamp are the only arguments that matter.
A campaign report shows full delivery, but the buyer's own screenshots show empty slots in DE and FR. AdsChecks GEO-routed checks produce timestamped evidence for both regions — a documented record the seller can't dismiss.
Before a Q4 campaign goes live, the ad-ops team runs checks across 6 target countries and 2 device types. SLOT_EMPTY in JP (mobile) surfaces a misconfigured selector — caught before spend starts.
A programmatic manager schedules 500 page checks every Monday. The diff report flags three slots that stopped rendering in US (desktop) after a publisher CMS update — with before/after screenshots attached.