How to check ReachEffect traffic quality: every visit scored 0–100 and pinned to the push sub-source that sent it — worst first, with the evidence to act on.
ad zone in ReachEffectThe 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.
ValidVisit reports the device, OS, browser — down to the version — plus the language and ISP behind every flagged visit, and ReachEffect supports OS version, browser version, language, device type and connection type targeting. The segments we flag are segments you can exclude.
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 scored 0–100 per source.
ReachEffect itself 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 ReachEffect tokens, not by creative (which says nothing about whether a click was human).
ReachEffect traffic scored 0–100 per sub-source, worst first — down to the placement you buy.
Bot / invalid-traffic score broken down by:
[pubId]Per-click id: ReachEffect passes a unique click id, so we also run velocity, deduplication and repeat-source checks on every visit.
Compare bot & invalid-traffic breakdown across every ad network →See your own ReachEffect sub-sources scored this way.
Each ReachEffect macro maps to a normalized parameter, so every scored click is pinned to the right campaign, creative and publisher.
https://yoursite.com/landing?utm_source=reacheffect&utm_medium=push&vv_click_id=[clickId]&vv_campaign_id=[campaignId]&vv_publisher_id=[pubId]| Token | ReachEffect macro | Maps to | Identifies |
|---|---|---|---|
| Click ID | [clickId] | click_id | click |
| Campaign ID | [campaignId] | campaign_id | campaign |
| Publisher ID | [pubId] | publisher_id | publisher |
[clickId][campaignId][pubId]Every visit 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 visit — 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.
Every ReachEffect click is weighed against 100+ independent data points spanning the network it came from, the device behind it and how the visitor behaves — combined into a single 0–100 quality score so real humans pass and bots stand out.
Yes. Using ReachEffect's own tracking tokens, ValidVisit attributes each scored click 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.
No. Detection runs from one lightweight script — no extra hop, no link rewriting, no change to your ReachEffect destination URLs.
See which campaigns and publishers send real, converting traffic vs bots — every visit scored 0–100.
Free trial at launch · just your email
One script · raw IP never stored · GDPR legitimate-interest basis