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.
How fast do I get results?
Most verification runs complete within seconds to a few minutes depending on GEO routing and page complexity. Results are available in the dashboard immediately after completion.
Can I use AdsChecks to check competitor pages?
You may only verify pages and environments you are authorized to test. See the Acceptable Use section in our Terms & Conditions.
What browsers and devices do you support?
Checks run in Chromium-based environments with desktop and mobile viewport emulation. The specific device context is attached to every result for comparison.
How do refunds work?
Completed verified pages are not refundable, including results with CHALLENGE_DETECTED and BLOCKED statuses. Duplicate or clearly accidental charges can be reviewed. See our Refund Policy for full details.