AdsChecks

Ad slot verification & evidence

Verify what’s on the page at the time of the check.

A verified page is one page load that validates up to 5 slots. Each verified page produces statuses, screenshots, JSON metadata, and a timestamped evidence bundle.

Request access How it works
World map for geo verification coverage

Why proof matters

Problem

Verification breaks down when geo, device, and slot state shift faster than a team can document them.

Proof-first checks give the same structure every time: context, slot outcome, and evidence artifacts.
Geo uncertainty
Coverage

Ad slots can render differently across countries, devices, and sessions.

Different render context means different proof requirements.
Disputes without evidence
Trust

Without consistent proof, QA findings are hard to share, compare, or resolve.

Screenshots and metadata reduce ambiguity in reviews.
Operational drag
Time

Manual checks take time and still leave gaps in coverage and repeatability.

Templates and structured runs remove repetitive 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.

Every block below maps to a concrete output that can be reviewed later by operations, QA, or commercial teams.
01 · Verification layer

Slot presence and visibility

  • Slot detected on page
  • Position and layout context
  • Visibility state (visible, partial, missing)

Designed for predefined selectors, not discovery or crawler-style scanning.

02 · Context layer

Geo and device coverage

  • Region-specific render checks
  • Desktop and mobile snapshots
  • Viewport and breakpoint metadata

Runs stay tied to the selected GEO and device context for comparison.

03 · Artifact layer

Evidence bundle

  • Screenshots for each slot
  • JSON metadata and timestamps
  • Export-ready ZIP bundle

Outputs stay consistent across repeated runs, reviews, and disputes.

04 · Ops layer

Operational integrity

  • Repeatable checks
  • Clear issue flags
  • Structured results

Built for teams that need repeatability rather than 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.

The product promise stays narrow on purpose: verify the page state at the moment of the check, then retain proof.
01 · Template

Provide URLs, slot selectors, device, GEO, and optional proxy routing settings.

URLs · List
Slots · Up to 5
GEO · ISO codes
02 · Run

Run a manual check or schedule it. Each page load becomes one verified page.

Mode · Manual / Weekly
Device · Desktop / Mobile
Proxy · Optional
03 · Evidence

Output includes slot statuses, screenshots, JSON metadata, and a timestamped evidence bundle.

Artifacts · Screens + JSON
Timestamp · Included
Structure · Consistent

Commercial and legal baseline

Plans and policy

The commercial model stays explicit: clear plan tiers, a narrow verification scope, and policy pages built around the same billing unit.

Plans are priced publicly. Policy pages stay aligned with the delivered output: verified pages and evidence artifacts.
Starter
Core
$39/month
500 pages · Schedule · No GEO
  • Up to 500 verified pages per month
  • Scheduled runs included
  • No GEO routing
Request access
Growth
Team
$79/month
1,000 pages · Schedule + GEO
  • Up to 1,000 verified pages per month
  • Scheduled runs included
  • GEO routing included
Request access
Standard
Best fit
$149/month
3,000 pages · Schedule + GEO
  • Up to 3,000 verified pages per month
  • Scheduled runs included
  • GEO routing included
Request access
Custom
Scale
Contact sales
Higher-volume usage
  • Commercial scoping by workflow
  • Custom monthly capacity
  • Setup aligned to operational needs
Contact sales
Scope

What we verify

AdsChecks is an audit and verification service. A Verified page means one completed page load for a target URL in a selected check context (GEO + device) and verification of up to 5 predefined ad slots.

Each result includes slot statuses, screenshots, JSON metadata, and UTC timestamp.

Read details
Statuses

Status model

Statuses: OK, SLOT_EMPTY, CHALLENGE_DETECTED, BLOCKED. CHALLENGE_DETECTED and BLOCKED are valid verification outcomes, not system errors.

Read details
Disputes

Refund policy

For completed verified pages, including CHALLENGE_DETECTED and BLOCKED, refunds are not provided.

Dispute review basis: run ID, verification status, artifacts (screenshots/JSON), timestamp, and check context (GEO/device).

Read details
Terms

Terms & Conditions

Public terms define service scope, billing rules, acceptable use, refunds, limitation of liability, and governing law.

Read details

Operational teams

Use cases

Teams that need repeatable verification with proof, not adtech promises.

Each use case below maps to a repeatable review workflow rather than a one-time audit.
Affiliate QA
Ops

Confirm placement compliance across networks and regional placements.

Use repeatable runs to compare expected vs observed page state.
Media buying QA
Spend

Verify high-value placements before campaign launch decisions.

Give buyers evidence before escalations become billing disputes.
Publisher audits
Delivery

Document slot delivery and layout integrity with consistent proof.

Keep screenshots, JSON, and timestamps aligned across repeated audits.

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.

What does CHALLENGE_DETECTED or BLOCKED mean?

These are valid verification outcomes, not errors. CHALLENGE_DETECTED means an anti-bot challenge or interstitial was encountered. BLOCKED means access was prevented in that environment. Both are billable because the page load was completed and evidence was captured.

How do I request access?

Email [email protected] with your target URLs, GEO/device needs, expected page volume, and rollout timing. We confirm fit and next steps directly.

When does billing start?

Billing starts only after access and plan scope are confirmed. There is no automatic conversion or billing before approval.

More questions about access, result speed, supported devices, or refunds: see the full FAQ.

Access

Request access

Share your workflow, rollout needs, and expected volume to get started.

AdsChecks is provisioned directly. We confirm scope, GEO/device requirements, and expected page volume before enabling access.

01
Share scope

Send target URLs, selectors, GEO/device needs, and expected monthly volume.

02
Confirm setup

We align the right plan, coverage, and rollout details before access is enabled.

03
Start verification

Run checks and review statuses, screenshots, and JSON metadata in the evidence bundle.

Request access

For pricing, onboarding, or workflow scoping — contact sales.