Ad verification is the process of independently confirming that digital ads were delivered in the right environment, to the right audience, at the right time, and free from fraud, as contracted.
Quick Answer
Ad verification is the process of independently confirming that digital ads were delivered in the right environment, to the right audience, at the right time, and free from fraud, as contracted.
Implement pre-bid verification segments in your DSP to filter fraud and unsafe inventory before spending, not just measure it after the fact.
Average industry invalid traffic rates on the open programmatic exchange range from 10 to 25 percent; verification reduces effective IVT to 1 to 3 percent in well-managed campaigns.
Require all programmatic partners to accept third-party verification tags as a standard contract term before onboarding.
Key Takeaways
Implement pre-bid verification segments in your DSP to filter fraud and unsafe inventory before spending, not just measure it after the fact.
Average industry invalid traffic rates on the open programmatic exchange range from 10 to 25 percent; verification reduces effective IVT to 1 to 3 percent in well-managed campaigns.
Require all programmatic partners to accept third-party verification tags as a standard contract term before onboarding.
How Ad Verification Works
Ad verification emerged as a critical function because the opacity of programmatic advertising created widespread opportunities for fraud, misrepresentation, and quality deterioration. Advertisers paying for premium placements found ads running on parked domains, apps generating fake traffic, or impressions served to bots rather than humans. Independent verification vendors fill the role of a trusted third party that audits delivery against the advertiser's contractual specifications, providing accountability that neither the publisher nor the DSP can self-report credibly.
Why Ad Verification Matters for B2B Marketing
The technical execution of ad verification relies on JavaScript measurement tags embedded in the ad creative. When the ad loads, the verification tag fires and begins collecting data: Is the ad in the viewport? Is the site content classified as safe? Is the user a bot or a human? Is the geo-location consistent with campaign targeting? All of this data is reported back to the verification vendor's servers and presented in a unified dashboard alongside delivery data from the DSP or ad server. Discrepancies between verification data and platform-reported data reveal quality issues.
Ad Verification: Best Practices & Strategic Application
Invalid traffic (IVT) detection is one of the most important functions of ad verification. The Association of National Advertisers estimated that advertisers waste billions of dollars annually on fraudulent traffic — bots visiting web pages, click farms generating fake engagement, domain spoofing misrepresenting low-quality sites as premium publishers. Verification vendors use machine learning models trained on billions of impressions to distinguish human from non-human traffic, flagging general IVT (simple bots) and sophisticated IVT (advanced bot networks that mimic human behavior) at the impression level.
Agency Perspective: Ad Verification in Practice
Advertisers should implement verification as a standard component of every programmatic and direct campaign. Pre-bid verification segments from IAS or DoubleVerify can be applied directly in DSPs to filter out low-quality inventory before bidding, which is more efficient than post-bid reporting alone. Verification data should feed back into publisher scorecard reviews, informing which publishers are placed on blocklists, awarded preferred deal status, or terminated from media schedules based on measured quality.
Frequently Asked Questions: Ad Verification
Ad verification is the process of independently confirming that digital ads were delivered in the right environment, to the right audience, at the right time, and free from fraud, as contracted.
IAS and DoubleVerify typically charge on a CPM basis, ranging from $0.05 to $0.20 CPM depending on the measurement products activated and the volume of impressions measured. Some DSPs include basic verification as part of their platform fee. The investment is almost always justified by the fraudulent traffic and brand safety costs it prevents, typically returning more than its cost in avoided waste.
Domain spoofing occurs when fraudulent publishers misrepresent their inventory as coming from a premium publisher by falsifying the domain reported in the bid request. An advertiser thinks they are buying CNN.com inventory when the impression is actually serving on a low-quality site. The ads.txt initiative, adopted by most major publishers, partially addresses domain spoofing by creating an authorized seller list that verification vendors and DSPs can check against.
Verification for CTV is more limited than for display and video on the open web, as the closed app environment on smart TVs makes JavaScript tag firing challenging. DoubleVerify, IAS, and others have developed CTV-specific measurement solutions using server-to-server integrations and device-level matching. Mobile app verification is more mature and relies on device IDs and SDK integrations rather than browser-based JavaScript tags.
MV3 Marketing helps B2B companies apply these strategies to drive measurable pipeline growth. Our team executes our services for technology, SaaS, and professional services companies.
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
