Which ReachEffect ad zones send bot traffic?

ValidVisit judges every ReachEffect visit Valid or Invalid and pins it to the ad zone that sent it, worst first.

Not ready? Estimate your invalid clicks →

validvisit · reacheffect cut-list

Exclude the bad ad zone in ReachEffect

The buyer pastes/adds the bad ad-zone IDs (or domains/SubIDs/IPs/ISPs) into a blacklist created in Advertising → Filters and attaches it to a campaign or applies it globally; per-ad-zone bid adjustments are also available as a softer lever.

Where: Advertising menu → Filters section in the self-serve dashboard; create a whitelist or blacklist there, then apply it globally per ad type or assign it to individual campaigns

Controls in ReachEffect’s campaign settings

✓ IP lists✓ OS✓ OS version✓ Browser✓ Browser version✓ Language✓ Device✓ Connection

ReachEffect macros mapped to report columns

sub-source level judged

no-hop

one script, nothing added to the click path

Valid / Invalid

a verdict on every visit

01 / SIGNAL

How bot traffic slips in through ReachEffect ad zones.

ReachEffect is a push channel — exactly where invalid traffic concentrates. See which ReachEffect publishers, placements and sub-sources send real clicks versus bots, attributed via ReachEffect’s own tracking tokens and judged Valid or Invalid per source.

02 / VERDICTS

What ReachEffect lets you judge by.

Publisher / site / zone

Invalid share broken down by:

Publisher ID [pubId]

Per-click id: ReachEffect passes a unique click id, and ValidVisit stores it with each visit, so a verdict traces back to the click in ReachEffect’s own reports.

Compare bot & invalid-traffic breakdown across every ad network →

See your own ReachEffect sub-sources judged this way.

03 / ATTRIBUTION

How ValidVisit attributes ReachEffect traffic

Each ReachEffect macro maps to a normalized parameter, so every judged visit is pinned to the right campaign, creative and publisher.

validvisit · tracking url

Tracking URL for ReachEffect, ready for ValidVisit

https://yoursite.com/landing?utm_source=reacheffect&utm_medium=push&vv_click_id=[clickId]&vv_campaign_id=[campaignId]&vv_publisher_id=[pubId]

All ReachEffect tracking tokens →

Token	ReachEffect macro	Maps to	Identifies
Click ID	`[clickId]`	click_id	click
Campaign ID	`[campaignId]`	campaign_id	campaign
Publisher ID	`[pubId]`	publisher_id	publisher

Click ID

ReachEffect macro: [clickId]
Maps to: click_id
Identifies: click

Campaign ID

ReachEffect macro: [campaignId]
Maps to: campaign_id
Identifies: campaign

Publisher ID

ReachEffect macro: [pubId]
Maps to: publisher_id
Identifies: publisher

Macros not yet checked against ReachEffect’s documentation. ReachEffect docs

The verdict works the same way on every network. ValidVisit never changes your ReachEffect account: you make the exclusion there yourself. How the verdict works →

FAQ

ReachEffect traffic quality, answered.

How does ValidVisit detect invalid ReachEffect traffic?

Every ReachEffect visit is checked against 100+ independent data points spanning the network it came from, the device behind it and the page it loaded. One thing a real visitor cannot produce makes it Invalid; otherwise it is Valid, with its evidence either way.

Can I see which ReachEffect publishers send bots?

Yes. Using ReachEffect's own tracking tokens, ValidVisit attributes each judged visit to the publisher, placement and sub-source, so invalid traffic is pinned to the exact sub-source — which you can then exclude manually in ReachEffect.

Does it require a funnel hop on my ReachEffect links?

No. Detection runs from one lightweight script — no extra hop, no link rewriting, no change to your ReachEffect destination URLs.