Is SourceKnowledge traffic real?
How to check SourceKnowledge traffic quality: every visit scored 0–100 and pinned to the native sub-source that sent it — worst first, with the evidence to act on.
SubID in SourceKnowledgeThe buyer adds each bad SubID to a Block list (or Global Block List) — or an Allow list to whitelist only good ones — either one-by-one from the Sub ID Summary dropdown or in bulk via the Tools > Allow & Block Lists interface, and can alternatively bid down/pause a SubID or automate it with Rules.
How invalid traffic shows up on SourceKnowledge.
SourceKnowledge is a native channel — exactly where invalid traffic concentrates. See which SourceKnowledge publishers, placements and sub-sources send real clicks versus bots, attributed via SourceKnowledge’s own tracking tokens and scored 0–100 per source.
Pinpoint the bot publishers & placements in SourceKnowledge.
SourceKnowledge 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 SourceKnowledge tokens, not by creative (which says nothing about whether a click was human).
SourceKnowledge traffic scored 0–100 per sub-source, worst first — down to the placement you buy.
Bot / invalid-traffic score broken down by:
- Sub/Source ID
{subid}
Per-click id: SourceKnowledge 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 SourceKnowledge sub-sources scored this way.
How ValidVisit attributes SourceKnowledge traffic
Each SourceKnowledge 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=sourceknowledge&utm_medium=native&vv_click_id={clickid}&vv_publisher_id={subid}&vv_ad_id={oadest}| Token | SourceKnowledge macro | Maps to | Identifies |
|---|---|---|---|
| Click ID | {clickid} | click_id | click |
| Sub/Source ID | {subid} | publisher_id | publisher |
| Destination / Ad | {oadest} | ad_id | ad |
- SourceKnowledge macro
{clickid}- Maps to
- click_id
- Identifies
- click
- SourceKnowledge macro
{subid}- Maps to
- publisher_id
- Identifies
- publisher
- SourceKnowledge macro
{oadest}- Maps to
- ad_id
- Identifies
- ad
How the detection works.
Data points → one score
Every visit is weighed against more than a hundred independent data points and reduced to a single, sortable 0–100 quality score.
Many angles, combined
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.
Proprietary, not a black box
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.
Pinned to the source
Every verdict maps to the campaign, publisher and placement that sent the click — so you know exactly which source to cut.
SourceKnowledge traffic quality, answered.
How does ValidVisit detect invalid SourceKnowledge traffic?+
Every SourceKnowledge 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.
Can I see which SourceKnowledge publishers send bots?+
Yes. Using SourceKnowledge'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 SourceKnowledge.
Does it require a funnel hop on my SourceKnowledge links?+
No. Detection runs from one lightweight script — no extra hop, no link rewriting, no change to your SourceKnowledge destination URLs.
Detect fraud on other native networks
Catch the fake clicks on SourceKnowledge.
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