Native inventory is where invalid traffic concentrates — and where most tools have the thinnest coverage. ValidVisit scores every click per publisher.
Native content-recommendation inventory is sold across a deep, uneven supply chain: a handful of premium publishers sit alongside a long tail of resellers and content-farm operators, all surfacing your creative under the same sponsored-content wrapper. That structure is where invalid traffic hides — and where most tools have the thinnest coverage.
The dominant pattern in native is publisher arbitrage: a site owner buys cheap visitors from pop, push, or display sources, routes them onto a content page to build widget-impression volume, and earns on the resulting sponsored-content clicks — whether those clicks come from low-intent humans or automated sessions standing in for them. Because each click arrives through a real browser on a real publisher URL, IP-only filters rarely catch it.
The damage almost never spreads evenly. It concentrates in a small set of publisher sites or zones, accumulating across dozens of sub-source ids before campaign-level metrics make it visible. So the unit that matters isn't the network — it's the individual site, widget, or zone behind the click.
Every native click is weighed against 100+ independent data points — spanning the network it came from, the device behind it, and how the visitor behaves — and combined into a single 0–100 quality score. The signals that matter most in native:
Native networks expose their own tokens — a site or publisher id, a widget or zone id, and usually a per-click id. ValidVisit attributes each scored click back to those tokens, so a bot-heavy publisher is pinned to its exact id rather than blamed on the network as a whole. ValidVisit reports the evidence per sub-source; the exclusion itself is a manual decision you make inside the network's own dashboard.
Every click is weighed against more than a hundred independent data points and reduced to a single, sortable 0–100 quality score.
Each data point is combined rather than checked in isolation, so a genuine human almost never trips enough of them to be flagged — and bots that beat one rarely beat the rest.
The detection model is ours and stays that way. What you get is a clear verdict on every click — not a single brittle rule you can game, and not an unexplained number you can't act on.
Every verdict maps to the campaign, publisher and placement that sent the click — so you know exactly which source to cut.
Illustrative example — the same 0–100 score, per source, worst first.
The click path runs through a publisher page the advertiser doesn't control, often after several extra hops, and the referrer is a credible editorial URL. That credible context is exactly what arbitrage operators rely on, so surface-level checks (referrer, IP reputation) under-detect it. Weighing each click against 100+ data points — network origin, device, and behaviour together — is far more diagnostic than any single surface check.
Yes. ValidVisit reads the network's own site/zone and widget tokens and rolls the invalid-traffic score up by them, so you get a per-publisher, per-widget breakdown grounded in your own data rather than the network's aggregate reporting.
See which campaigns and publishers send real, converting traffic vs bots — every click scored 0–100.
Free trial at launch · lock in early-access pricing
One script · raw IP never stored · GDPR legitimate-interest basis