zone in TrafficFactoryValidVisit flags the bad {zone_id}; exclude it in your TrafficFactory campaign.
TrafficFactory is a self-serve banner and display network sourcing high-volume tube and entertainment inventory. It exposes a {target.id} (the targeting / spot a click came from), {campaign.id} and a {goal_tracking} click token on every click — and the spot is the unit you can exclude in the campaign. ValidVisit reads these macros as each click lands, then measures that click against 100+ independent data points — covering the network path, the device on the other end and the visitor's behavior — and resolves them into one 0–100 quality score, so it can report which spots are carrying non-human traffic.
https://yoursite.com/landing?utm_source=trafficfactory&utm_medium=banner&vv_campaign_id={campaign_id}&vv_publisher_id={zone_id}&vv_click_id={conversions_tracking}High-volume banner/display inventory carries an IVT profile dominated by automation and low-attention placements. The dominant pattern on TrafficFactory is automated or low-attention clicks concentrated in specific {target.id} spots: traffic routed through hosting infrastructure or anonymizing proxies, or stacked/low-viewability placements that fire clicks without any genuine attention behind them.
The technical layer is where this separates out most cleanly. A click can arrive wearing a perfectly ordinary user-agent yet still betray itself across the dozens of network- and device-level checks ValidVisit runs, and clients that load a page but never actually behave like a real browser session stand apart from human visitors. Because {target.id} rides on every click, each of these findings rolls up to the individual spot, so a single bad spot stays separable from the rest of a campaign.
Rank active {target.id} spots by quality and by the share of clicks in the suspicious/bad tier. Spots above your baseline are exclusion candidates.
Banner clicks arriving over cloud-hosting or proxy routes rarely convert. ValidVisit ties each such finding back to the {target.id} so you can exclude the offending spots cleanly.
When a spot shows a cluster of clicks that score poorly on the network and device side and don't behave like genuine browser sessions, that points to automation rather than real people — and those signals are far harder to fake than a user-agent string.
A spike in {campaign.id} clicks without conversions usually traces to a specific spot the per-spot breakdown will identify.
Each TrafficFactory macro maps to a normalized parameter, so every scored click is pinned to the right campaign, creative and publisher.
| Token | TrafficFactory macro | Maps to | Identifies |
|---|---|---|---|
| Campaign ID | {campaign_id} | campaign_id | campaign |
| Zone ID | {zone_id} | publisher_id | publisher |
| Click ID | {conversions_tracking} | click_id | click |
{campaign_id}{zone_id}{conversions_tracking}TrafficFactoryitself 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 TrafficFactory tokens, not by creative (which says nothing about whether a click was human).
Illustrative example — TrafficFactory traffic scored 0–100 per sub-source, worst first.
See your own TrafficFactory sub-sources scored this way.
Bot / invalid-traffic score broken down by:
{zone_id}The targeting / spot the click came from — the unit you exclude in the campaign.Per-click id: TrafficFactory 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 →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.
Add ValidVisit's script to your landing page and append TrafficFactory's macros — {target.id}, {campaign.id} and the {goal_tracking} click token — to your destination URL. The pixel captures them as the click lands and stores a scored verdict per click, segmented by spot, with nothing on the click path.
Yes. Because {target.id} is on every click, ValidVisit ranks your spots by quality and by what's dragging their scores down, and you exclude the offenders in your TrafficFactory campaign. ValidVisit reports the evidence; the exclusion is always yours to apply in the network's own dashboard.
No. The 0–100 score is built from 100+ technical data points across the network, the device and how the visitor actually behaves — not from how engaged someone seems. A real person browsing casually looks completely different from an automated client or a click coming off hosting infrastructure, so genuine low-engagement visits aren't penalized.
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