/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Adalytics: DoubleVerify, IAS, and Human Security, paid by advertisers to detect bots, regularly miss such traffic; DoubleVerify missed 21% of bot visits

> I was the 15th employee at DoubleVerify in 2009. … Charlie Tysse : A few years ago while still at Further (formerly Search Discovery), Jim Gordon, Samantha Burge and I were engaged by a large multinational logistics firm … Dr. Augustine Fou : nothing new, DV and IAS failed again (to detect basic bots)  —  AND, kicker, they revealed that they use IP addresses and USER AGENTS … Jay Friedman : Why would most advertisers rather save 2% instead of 20%?  That's a question every CFO and CEO should ask their CMO and procurement group. … See also Mediagazer

Wall Street Journal Patience Haggin

Context & Ripple Effects

Bot traffic has long distorted digital-ad buying, with prior coverage describing bot-driven fraudulent ad clicks and an ecosystem in which some exchanges were said to tolerate questionable traffic. The new Adalytics findings put the focus on the effectiveness of the verification vendors advertisers hire as a control.

DoubleVerify had expanded from measurement into campaign optimization through its Scibids acquisition, making detection quality more consequential across the ad-buying workflow. The report challenges whether IP-address and user-agent-based signals are sufficient against the traffic they are meant to identify.

First-order effects

  • Advertisers using DoubleVerify, IAS, or Human Security have reason to reassess bot-traffic reports and seek independent validation, particularly where reported reach or performance informed spending decisions.
  • DoubleVerify faces direct scrutiny after Adalytics’ claim that it missed 21% of bot visits; IAS and Human Security face parallel questions about their detection coverage and methodology.

Second-order effects

  • Media buyers and procurement teams may require more transparent detection criteria, testing, or contractual accountability from verification providers before relying on their reporting.
  • Publishers and exchanges with traffic cleared by these tools could face renewed examination from advertisers, because verification misses can leave invalid inventory in apparently vetted supply.

Third-order effects

  • If independent testing repeatedly finds material gaps, ad verification may shift from a trusted reporting layer toward a continuously audited, multi-vendor control—an instance of the fake-traffic market’s persistent accountability problem.
  • The larger pressure is for verification systems that can demonstrate performance against evolving bot behavior rather than rely chiefly on opaque vendor claims; how quickly that changes buying standards remains uncertain.

The trend: Digital advertising is moving toward stricter, independently testable verification as automated traffic makes conventional trust signals less reliable.