How to check Tonic traffic quality: every visit scored 0–100 and pinned to the pop / pop-under sub-source that sent it — worst first, with the evidence to act on.
Platform merged: TONIC.'s self-serve advertiser platform moved to Zeropark (both are Team Internet companies); zero-click inventory is now bought there. See Zeropark →
source ID in TonicThe buyer pastes the bad Source IDs into the campaign's source list with whitelisting=false, blocking all future traffic from those sources (or flips to whitelist-only of proven converters); source_id was exposed as a %sourceid% macro and a reporting/statistics dimension for building the list.
ValidVisit reports the device, OS, browser — down to the version — plus the language and ISP behind every flagged visit, and Tonic supports OS, browser, device type and connection type targeting. The segments we flag are segments you can exclude.
Tonic is a pop / pop-under channel — exactly where invalid traffic concentrates. See which Tonic publishers, placements and sub-sources send real clicks versus bots, attributed via Tonic’s own tracking tokens and scored 0–100 per source.
Tonic 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 Tonic tokens, not by creative (which says nothing about whether a click was human).
Tonic traffic scored 0–100 per sub-source, worst first — down to the placement you buy.
Bot / invalid-traffic score broken down by:
[sourceid]Per-click id: Tonic 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 Tonic sub-sources scored this way.
Each Tonic 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=tonic&utm_medium=pop&vv_click_id=[clickid]&vv_campaign_id=[campaign_id]&vv_publisher_id=[sourceid]&vv_keyword=[match]| Token | Tonic macro | Maps to | Identifies |
|---|---|---|---|
| Click ID | [clickid] | click_id | click |
| Campaign ID | [campaign_id] | campaign_id | campaign |
| Source ID | [sourceid] | publisher_id | publisher |
| Keyword Match | [match] | keyword | keyword |
[clickid][campaign_id][sourceid][match]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 Tonic 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 Tonic'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 Tonic.
No. Detection runs from one lightweight script — no extra hop, no link rewriting, no change to your Tonic 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