How to check ROIads 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.
source in ROIadsThe buyer pastes the bad source IDs into the campaign's Sources Blacklist field in Advanced Settings (or restricts delivery to a whitelist of good ones), optionally using per-source micro bidding to down-bid instead of fully cutting a source.
ValidVisit reports the device, OS, browser — down to the version — plus the language and ISP behind every flagged visit, and ROIads supports OS version, browser version, language, device type and connection type targeting. The segments we flag are segments you can exclude.
ROIads is a push channel — exactly where invalid traffic concentrates. See which ROIads publishers, placements and sub-sources send real clicks versus bots, attributed via ROIads’s own tracking tokens and scored 0–100 per source.
ROIads 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 ROIads tokens, not by creative (which says nothing about whether a click was human).
ROIads traffic scored 0–100 per sub-source, worst first — down to the placement you buy.
Bot / invalid-traffic score broken down by:
{publisher_id}Bot / invalid-traffic score broken down by:
{site_id}Per-click id: ROIads 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 ROIads sub-sources scored this way.
Each ROIads 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=roiads&utm_medium=push&vv_click_id={click_id}&vv_campaign_id={campaign_id}&vv_campaign_name={campaign_name}&vv_publisher_id={publisher_id}&vv_placement_id={site_id}&vv_creative_id={creative_id}| Token | ROIads macro | Maps to | Identifies |
|---|---|---|---|
| Click ID | {click_id} | click_id | click |
| Campaign ID | {campaign_id} | campaign_id | campaign |
| Campaign Name | {campaign_name} | campaign_name | campaign |
| Publisher ID | {publisher_id} | publisher_id | publisher |
| Site ID | {site_id} | placement_id | placement |
| Creative ID | {creative_id} | creative_id | creative |
{click_id}{campaign_id}{campaign_name}{publisher_id}{site_id}{creative_id}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 ROIads 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 ROIads'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 ROIads.
No. Detection runs from one lightweight script — no extra hop, no link rewriting, no change to your ROIads 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