Ad verification and ad fraud detection are both used in programmatic advertising quality review. They are often mentioned together, and sometimes confused. They solve different problems and operate at different points in the ad delivery chain.
This guide explains what each does, where they differ, and which one you need for a given problem.
Ad verification: what it is
Ad slot verification checks whether an ad placement is rendering on a web page — in a specific GEO, on a specific device, at a specific point in time.
It answers: is this slot present, visible, and showing content right now?
A verification tool loads the target URL in a controlled environment, inspects predefined CSS selectors, captures a full-page screenshot, and returns a status for each slot:
OK— slot matched expected selector and stateSLOT_EMPTY— selector found, no ad content at check timeBLOCKED— access was prevented in the target GEO or environmentCHALLENGE_DETECTED— anti-bot challenge was returned instead of the page
The output is a structured evidence bundle: screenshot, JSON metadata, and a UTC timestamp. This evidence can be used for QA, commercial review, or dispute documentation.
What verification does not do: it does not analyse traffic quality, detect bot impressions, or evaluate viewability at scale. It observes page state at check time — nothing more.
Ad fraud detection: what it is
Ad fraud detection identifies invalid traffic (IVT) — bot-driven impressions, click farms, domain spoofing, and other manipulation of ad delivery metrics.
It answers: is this traffic real, and is delivery happening where it was sold?
Fraud detection tools operate primarily at the impression and click level, analysing signals like:
- IP reputation and data center traffic patterns
- User agent analysis and browser fingerprinting
- Click-through rate anomalies
- Domain verification (confirming ads served on the claimed domain)
- Viewability measurement at scale
Fraud detection is typically integrated into DSPs, measurement platforms, or third-party verification services that tag impressions.
What fraud detection does not do: it does not confirm whether a specific ad slot is rendering on a specific page in a specific GEO at a given time. It operates on aggregated traffic signals, not page-level observation.
Where they differ
| Ad slot verification | Ad fraud detection | |
|---|---|---|
| Question answered | Is this slot rendering right now? | Is this traffic real? |
| Level of analysis | Page-level observation | Impression/traffic-level analysis |
| Evidence output | Screenshot + JSON + timestamp | Traffic quality scores, IVT rates |
| When to use | Pre-launch QA, billing disputes, delivery documentation | Campaign performance review, DSP reporting, IVT audits |
| GEO specificity | Checks from specific GEO via proxy | Aggregate traffic analysis by region |
| Integration point | URL + CSS selector | Ad tag or DSP integration |
Where they overlap
Both tools are used when something is wrong with ad delivery. The overlap is in the investigation phase of a billing dispute or a delivery discrepancy:
- Fraud detection flags that delivery in a specific region is performing below expectation (low CTR, high IVT rate, viewability below contracted threshold).
- Ad slot verification produces the page-level evidence — confirming whether the slot was rendering at all in that region, or returning
BLOCKED/SLOT_EMPTYduring the campaign period.
Verification evidence complements fraud detection data: it explains why delivery was abnormal (blocked access, unfilled impression, anti-bot challenge) rather than just flagging that it was.
Which one you need
Use ad slot verification when:
- You need to confirm a slot is rendering before launch
- You’re investigating a delivery discrepancy in a specific GEO
- A publisher disputes a SLOT_EMPTY finding and you need timestamped evidence
- You want repeatable, documented QA across multiple campaigns or domains
- You’re building a delivery documentation record for commercial review
Use ad fraud detection when:
- You need to evaluate traffic quality across a campaign
- IVT rates are above threshold and you need to dispute billing
- You’re monitoring for domain spoofing or ad stacking
- Viewability compliance is a contractual requirement
- You need impression-level data for performance reporting
Use both when:
- Campaign performance is below expectation and you’re unsure whether the cause is delivery failure (slot not rendering) or traffic quality (slot rendering but impressions are invalid)
- A billing dispute requires both page-level evidence (verification) and traffic-quality data (fraud detection) to make the case
Common misconceptions
“SLOT_EMPTY means fraud.”
Not necessarily. SLOT_EMPTY means the slot container was found but no creative was present at check time. Causes include low fill rate, auction timeout, floor price mismatch, or lazy loading. Fraud may or may not be a factor — verification confirms the page state, not the traffic source.
“Ad fraud detection confirms delivery.”
Fraud detection tools analyse traffic quality against claimed delivery. They do not directly confirm that a specific slot was rendering on a specific page. A publisher can show zero IVT while still having slots that return SLOT_EMPTY or BLOCKED in specific GEOs.
“Verification is only useful for disputes.” Verification is a QA tool first. Pre-launch verification runs catch slot configuration issues, selector mismatches, and GEO-specific blocking before spend begins — preventing the disputes that make retroactive evidence collection necessary.
Summary
Ad slot verification and ad fraud detection answer different questions at different points in the ad delivery chain. Verification is page-level and GEO-specific: it confirms whether a slot is rendering, with screenshot proof. Fraud detection is traffic-level: it identifies whether impressions are coming from real users.
For pre-launch QA, delivery documentation, and dispute support, ad slot verification produces the most directly relevant evidence. For traffic quality audits and IVT analysis, fraud detection is the appropriate tool.
Most operational ad teams that deal with placement compliance and delivery accountability use both — starting with verification to confirm page state, and fraud detection to evaluate traffic quality against that delivery baseline.
AdsChecks is an ad slot verification tool. Start a free trial →