Is Outbrain traffic real? How to check Outbrain traffic quality
publisher / section in OutbrainValidVisit attributes the bots to a publisher / section; add them to Outbrain's Blocked Publishers list.
Outbrain's content recommendation network places your ads inside editorial environments across hundreds of premium publishers and a long tail of content sites. The economics of that model create a specific IVT pressure: recommendation widgets are bought and sold in ways that give certain publishers a financial incentive to inflate outbound click volume. Because the widget sits inside a news article or blog post, the referral context can appear credible even when the click itself is not. ValidVisit connects to Outbrain through its native dynamic macros — capturing `{{publisher_id}}` and `{{ob_click_id}}` on every click — so you can see precisely which publisher account and which content item is driving inflated volume, rather than relying on campaign-aggregate metrics that obscure the source.
https://yoursite.com/landing?utm_source=outbrain&utm_medium=native&vv_campaign_id={{campaign_id}}&vv_ad_id={{ad_id}}&vv_publisher_id={{publisher_id}}&vv_click_id={{ob_click_id}}How invalid traffic shows up on Outbrain
Native content distribution creates an IVT dynamic that is structurally different from search or social. In Outbrain's ecosystem, the supply chain runs from an advertiser's bid through Outbrain's auction to a widget slot on a publisher's page — and the publisher controls the traffic flowing through that page. When a publisher routes cheap, non-organic traffic to a content page in order to generate widget click-outs, the resulting clicks can carry a real editorial URL as the referrer while the underlying session never resembles a genuine human reader.
ValidVisit doesn't lean on any single tell. Every click that lands is weighed against more than 100 independent data points — drawn from the network and connection it arrived over, the device sitting behind it, and the way the visitor actually moves through the page — and those signals collapse into one 0-100 quality score per click. That matters for widget inventory because the patterns that betray arbitrage are spread across all three of those layers at once. A publisher routing low-cost traffic to a content page to manufacture click-outs may produce a plausible editorial referrer, but the connection it travels over and the shallow, mechanical way the session behaves after arrival rarely hold up. Outbrain's own `{{ob_click_id}}` token comes through with the click, so the score attaches directly to the publisher and content item that sourced it, no matter how trustworthy the referring URL looks on its face.
Because the scoring happens after the click reaches your page rather than in the click path, ValidVisit never blocks or auto-excludes anything — it produces a per-click record you can read. That post-arrival vantage point is what lets it catch automated click tools running against high-volume widget placements: the genuine readers pass through cleanly and the manufactured sessions separate out on the score, which is exactly the list you carry back into Outbrain to act on.
What to watch on Outbrain
Sort your ValidVisit dashboard by `{{publisher_id}}` and compare click volume against the share of low-scoring clicks per publisher. A publisher generating a disproportionate slice of total clicks while its quality scores sit well below your campaign baseline is a consistent IVT pattern in widget inventory — flag that publisher ID for review in Outbrain's publisher exclusion settings.
ValidVisit scores the connection and behaviour behind every click, not just the click count. In Outbrain native campaigns, low scores that pile up on a small handful of publisher IDs — rather than spreading evenly across your campaign — point to arbitrage behaviour rather than organic browsing. Use that concentration alongside `{{publisher_id}}` to narrow your exclusion list before taking it to the Outbrain campaign dashboard.
Clicks routed through shared origination infrastructure tend to score alike even when their source addresses rotate, because the same combination of connection and behavioural signals keeps recurring. When ValidVisit shows a tight band of similarly low-scored clicks all attributed to the same `{{publisher_id}}`, that repetition is a strong sign those clicks share a common origin rather than reflecting independent human browsing.
Cross-reference low scores against `{{ad_id}}` — the content item token — in addition to publisher ID. When a specific content item shows consistently weak quality across multiple publisher IDs, the problem may be tied to a particular creative format or placement type rather than a single publisher, pointing toward widget-level exclusion rather than publisher-level exclusion as the more targeted fix.
How ValidVisit attributes Outbrain traffic
Each Outbrain macro maps to a normalized parameter, so every scored click is pinned to the right campaign, creative and publisher.
| Token | Outbrain macro | Maps to | Identifies |
|---|---|---|---|
| Campaign ID | {{campaign_id}} | campaign_id | campaign |
| Ad ID | {{ad_id}} | ad_id | ad |
| Publisher ID | {{publisher_id}} | publisher_id | publisher |
| Click ID | {{ob_click_id}} | click_id | click |
- Outbrain macro
{{campaign_id}}- Maps to
- campaign_id
- Identifies
- campaign
- Outbrain macro
{{ad_id}}- Maps to
- ad_id
- Identifies
- ad
- Outbrain macro
{{publisher_id}}- Maps to
- publisher_id
- Identifies
- publisher
- Outbrain macro
{{ob_click_id}}- Maps to
- click_id
- Identifies
- click
Pinpoint the bot publishers & placements in Outbrain
Outbrainitself isn’t the problem — bots and invalid traffic concentrate in a handful of its sub-sources: the publisher, site or zone, and the placement or widget within it. So we roll the score up by those Outbrain tokens, not by creative (which says nothing about whether a click was human).
Illustrative example — Outbrain traffic scored 0–100 per sub-source, worst first.
See your own Outbrain sub-sources scored this way.
Bot / invalid-traffic score broken down by:
- Publisher ID
{{publisher_id}}
Per-click id: Outbrain passes a unique click id, so we also run velocity, deduplication and repeat-source checks on every click.
Compare bot & invalid-traffic breakdown across every ad network →How the detection works
Data points → one score
Every click is weighed against more than a hundred independent data points and reduced to a single, sortable 0–100 quality score.
Many angles, combined
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.
Proprietary, not a black box
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.
Pinned to the source
Every verdict maps to the campaign, publisher and placement that sent the click — so you know exactly which source to cut.
Outbrain traffic quality — FAQ
Which Outbrain macros do I add to my destination URL, and what does each one tell me about click quality?+
There are four macros worth including: `{{publisher_id}}` identifies the source publisher account and is the most actionable dimension for exclusion decisions because Outbrain's campaign settings include a publisher blocklist. `{{ob_click_id}}` is the unique per-click identifier ValidVisit uses to tie its score back to Outbrain's own reporting. `{{campaign_id}}` and `{{ad_id}}` allow you to segment scores by campaign and content item when you want to isolate whether a quality issue is tied to a specific piece of content rather than a publisher. You append these as standard query parameters on your destination URL — no funnel hop and no tag injection is involved.
Outbrain's platform already runs traffic quality filters. What does ValidVisit add on top of that?+
Outbrain's filters are designed to protect the integrity of the marketplace as a whole — they operate on aggregate signals across all advertisers and are calibrated to maintain inventory scale. ValidVisit is scoped to your campaign: it scores every click that reaches your landing page and attributes each score to the specific publisher ID, content item, and click ID that generated it. The result is an auditable, per-click log that shows you which sub-sources are systematically underperforming on your offer — information that platform-level filtering does not surface in a form you can act on directly. You take that scored list and apply exclusions manually inside Outbrain's campaign settings.
Does the widget-based nature of Outbrain's ad unit affect how ValidVisit scores clicks compared to, say, display or search?+
The delivery mechanic does affect which signals carry the most weight. In display or search, invalid clicks often come from dedicated click tools that betray themselves quickly. In Outbrain's widget environment, the dominant IVT pattern involves publishers routing low-cost traffic to their pages to generate outbound clicks — so the device may look fairly consumer-like, while the connection it arrived over and how the session behaves once it lands tend to be the more telling clues. Since ValidVisit weighs all 100-plus data points together into a single quality score, the math naturally leans on whichever combination is most out of place for a given click, so widget traffic and search traffic each get judged on the evidence that actually fits them.
Detect fraud on other native networks
Catch the fake clicks on Outbrain.
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