How to check X Ads (Twitter) traffic quality: every visit scored 0–100 and pinned to the social sub-source that sent it — worst first, with the evidence to act on.
app in X Ads (Twitter)The buyer types the bad publishers' @usernames into the Excluded Publishers field of the pre-roll ad group (max 50 handles for standard Content Categories, 5 for Curated Categories) or checks off the specific third-party apps to exclude in the X Audience Platform section of campaign setup — there is no bulk list upload
ValidVisit reports the device, OS, browser — down to the version — plus the language and ISP behind every flagged visit, and X Ads (Twitter) supports OS version, language, device type and connection type targeting. The segments we flag are segments you can exclude.
See which X Ads (Twitter) publishers, placements and sub-sources send real clicks versus bots, attributed via X Ads (Twitter)’s own tracking tokens and scored 0–100 per source.
X Ads (Twitter) 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 X Ads (Twitter) tokens, not by creative (which says nothing about whether a click was human).
X Ads (Twitter) traffic scored 0–100 per sub-source, worst first — down to the placement you buy.
X Ads (Twitter) exposes campaign-level tokens; we break invalid traffic down by campaign and per-click id, and surface the offending networks and devices behind the bot clicks.
Per-click id: X Ads (Twitter) 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 X Ads (Twitter) sub-sources scored this way.
Each X Ads (Twitter) 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=x-ads&utm_medium=social&vv_click_id=twclid| Token | X Ads (Twitter) macro | Maps to | Identifies |
|---|---|---|---|
| X Click ID | twclid | click_id | click |
twclidEvery 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 X Ads (Twitter) 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 X Ads (Twitter)'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 X Ads (Twitter).
No. Detection runs from one lightweight script — no extra hop, no link rewriting, no change to your X Ads (Twitter) 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