What does ad verification measure, and what can it not prove?
Part of Brand suitability
The short answer
Ad verification is independent checking that an ad ran the way the campaign terms said it would: on the intended pages, in the intended places and countries, where people could see it, and to real visitors rather than bots. It measures delivery against rules the buyer set. It does not decide which sites deserve a place on the plan.
Key takeaways
- The IAB and MRC guidelines of 2012 define verification by five service lines: site context, geography, ad placement, competitive separation and fraud.
- Verification checks delivery against rules a buyer already wrote; targeting is the act of choosing where to bid in the first place.
- Pre bid checks avoid impressions before money is spent, while post bid checks measure and block after the ad is served; the IAB's 2020 guide says the advertiser still pays for the ad space in that case.
- A clean verification report cannot show that a site is a quality publisher, that its audience is in the market, or that an excluded page was really unsuitable.
- Reconcile reports against the approved site list domain by domain, with the report's own method notes beside each number.
What does ad verification measure?
Definition
- Ad verification
- In the words of the IAB and MRC guidelines, a process which attempts to verify that one or more attributes of a served online ad have been executed in a manner consistent with the terms specified by the advertiser or agency.
The Guidelines for the Conduct of Ad Verification (opens in a new tab), written by the IAB with the Media Rating Council in February 2012, still frame the field. They list five primary service lines and say a verification service does not have to offer all of them. Two more measurements, viewability and invalid traffic, have their own MRC standards and sit outside the five lines. Each line answers one narrow question about delivery.
| Measurement | Question it answers | Governing document |
|---|---|---|
| Site context | Did the ad run on pages the advertiser's parameters allow? | 2012 guidelines; 2018 content level supplement for images, video and audio |
| Geography | Did the ad reach users in the targeted locations, as far as IP based location can tell? | 2012 guidelines |
| Ad placement | Was the ad in the agreed position, size and execution on the page? | 2012 guidelines |
| Competitive separation | Was the ad kept away from competing ads the terms excluded? | 2012 guidelines |
| Fraud and invalid traffic | Were impressions served to real people, or to bots, data centers and hijacked devices? | MRC invalid traffic guidelines and 2020 addendum |
| Viewability | Could the ad be seen: 50 percent of pixels for one continuous second for display, two seconds for video? | MRC viewable impression guidelines, 2015 |
Invalid traffic comes in two grades. The MRC's 2020 addendum (opens in a new tab) defines general invalid traffic as traffic identified through routine filtration, such as lists of known data centers and declared crawlers, and sophisticated invalid traffic as cases needing advanced analytics or significant human intervention, such as hijacked devices. The invalid traffic guide and the viewability guide cover each measurement in depth.
How is verification different from targeting?
Targeting decides where a campaign bids. Verification checks what happened against the rules that came with that decision. A buyer who targets an approved list of 80 sites still needs verification to learn whether the ads ran on those sites, in view and to real people. A buyer who verifies but never chose sites carefully learns, in detail, how a broad buy went.
| Aspect | Targeting | Verification |
|---|---|---|
| Job | Choose the inventory to bid on | Measure delivery against the campaign terms |
| When it acts | Before the auction, in planning and in the buying platform | Before the bid, at serving and after the impression |
| Inputs | Site lists, deals, topics, keywords, geography settings | Page context, tags, location signals, traffic analysis, viewability measurement |
| Output | Impressions bought | Rates, flags, blocks and logs |
| Strength | Puts budget where the plan wants it | Independent evidence of what actually ran |
| Weakness | Cannot see what happens after the bid | Measures only against rules someone already wrote |
What is the difference between pre bid and post bid verification?
The difference is timing, and timing decides who pays. The IAB's December 2020 guide (opens in a new tab) describes pre bid detection as avoiding unsafe content before the transaction, with some suitability analysis possible, and post bid detection as identifying unsuitable environments after it, possibly serving a different default creative, then targeting away from those sources in future bidding. The same guide says that most of the time these tools block post bid, and the advertiser still pays for the ad space even when a backup creative is served.
The 2012 guidelines set rules for blocking at serving time. Blocking methods should be disclosed in the campaign terms and conditions in advance, used only when there is strong evidence of brand damage or a violation of the insertion order, weighed against the risk of blocking wrongly, and reported to the seller on a timely basis, with daily notice recommended. The pre bid brand safety guide covers what the pre bid side can and cannot see.
What does verification not tell a buyer?
A verification report can be misread as proof of something it never measured. The limits below follow from how each measurement is defined, and several are written into the MRC's own documents.
Things a verification report does not establish
- That a site is a real publisher with original editorial content; a page can pass context, viewability and fraud checks and still be made for advertising.
- That the site's audience lives in the target market; geography checks look at where each impression's user appeared to be, not who reads the site.
- That a blocked page was really unsuitable; the 2018 MRC supplement lets reports state the likelihood of false positive results by service line.
- That images, video and audio were checked, unless the service is accredited at the content level; property level services must disclose that exclusion under the MRC's October 2025 policy.
- That every impression was observed; where samples are used, the MRC supplement requires the confidence level and standard error to be disclosed.
- That a classification is current; the supplement requires stated data refresh policies because content changes after it is first assessed.
Accreditation sets the outer edge of what a number means. The MRC accreditation guide explains how to read a service's letter, and the October 2025 policy (opens in a new tab) explains why only content level services may present themselves as brand safety.
How should verification results be reconciled with a site list?
Reconciliation turns two documents into one decision: the list the client approved and the report of what ran. The IAB guide names one obstacle, which is that brand safety flagged impressions are reported in aggregate as standard practice, making reconciliation impossible without an impression ID. The 2012 guidelines add that when the verification service, seller and buyer's ad server disagree significantly, a reconciliation should be run to investigate. Ask for domain and URL level exports with impression IDs before the campaign starts.
Six steps to reconcile a verification report with an approved list
- Get the same period and the same scope. Pull the verification export and the buying platform's placement report for identical dates, campaigns and time zones.
- Normalize the domains. Reduce subdomains and app bundles to the form used on the approved list, and keep the raw values in a second column.
- Sort every domain into three groups. On the list and in the report; in the report but not on the list; on the list with no delivery.
- Investigate the off list group first. Each one is a targeting leak, a seller passing a different domain, or a measurement error. Trace it to the deal, seller ID and source.
- Read the method notes beside each rate. Note whether a context rate is property level or content level, sampled or census, and how old the classifications were.
- Write the outcome back to the list. Record which domains stay, which need review, and which rules changed, with the date and the person who decided.
What does a reconciliation look like on a real campaign?
Fictional example
A pool installer in Arizona and Nevada checks its first month
A fictional builder of backyard swimming pools runs a display campaign in Phoenix, Tucson and Las Vegas on an approved list of home improvement and local lifestyle sites. After the first month the verification report shows a high block rate for context on a large regional news site, and a set of impressions on domains nobody approved.
The planner follows the six steps. The off list impressions trace to one reseller passing app bundles that the list never named, so the deal is narrowed to the approved domains. The news site's blocks come from a property level classification of the whole domain as news, which the report's method notes disclose; the pages that ran were home and garden features. The client keeps the site and asks for a content level review of a sample of its blocked pages. Geography shows a share of impressions in California, which the planner records as a location setting to check, not a site problem.
Where does PlacementGraph fit next to ad verification?
Frequently asked questions
Is ad verification the same as brand safety?
No. Brand safety is one use of the site context service line. Verification also covers geography, ad placement, competitive separation, invalid traffic and viewability. A contract that buys only fraud and viewability measurement has bought verification with no brand safety in it.
Does verification work inside mobile apps?
Partly. The IAB's 2020 guide notes that apps have no page domain, so checks often rely on app bundle IDs, and that measurement depends on publishers adopting the Open Measurement SDK, which sellers adopt voluntarily. Ask what share of in-app impressions a service could actually measure.
Who should hold the verification contract?
The buyer side has the strongest case, so the measurement stays independent of the parties being measured. The 2012 guidelines describe verification as checking attributes against terms the advertiser or agency specified, which only works if the buyer controls the rules and receives the raw logs.
What should a buyer ask for before launch to make reconciliation possible?
Ask for domain and URL level exports with impression IDs, the time zone used, how long the platform keeps logs, and the method notes for each rate. Agree the export schedule in writing, because a report delivered only as totals cannot be matched against an approved list afterward.
Sources
- Guidelines for the Conduct of Ad Verification (February 2012) (opens in a new tab)IAB and Media Rating Council
- Enhanced Content Level Context and Brand Safety, Ad Verification Supplement (September 2018) (opens in a new tab)Media Rating Council
- Policy for Property Level Ad Verification Representations (October 18, 2025) (opens in a new tab)Media Rating Council
- MRC Viewable Ad Impression Measurement Guidelines, version 2.0 (opens in a new tab)Media Rating Council
- Invalid Traffic Detection and Filtration Standards Addendum (June 2020) (opens in a new tab)Media Rating Council
- Brand Safety and Suitability Guide (December 2020) (opens in a new tab)IAB
Researched and written by PlacementGraph Research. Read how we research, source and update these pages. Corrections: diana@placementgraph.com.