Which TrafficShop sites send bot traffic?

ValidVisit judges every TrafficShop visit Valid or Invalid and pins it to the site that sent it, worst first.

Not ready? Estimate your invalid clicks →

validvisit · trafficshop cut-list

Exclude the bad site/domain in TrafficShop

Pull {site_id}/{domain} from S2S/tracker stats, then remove those domains from the campaign’s domain targeting (or feed them to the account manager / auto-blacklister) so the campaign stops buying from those publisher sites.

Where: Campaign create/edit → targeting settings (domain filtration / source sampling on RON campaigns); reviews also describe dashboard white lists + blocking filters and an hourly auto-blacklister (requires S2S postbacks); official self-serve documentation is thin, so buyers without S2S tracking typically route exclusions through their account manager

Controls in TrafficShop’s campaign settings

✓ IP lists✓ OS✓ Browser✓ Language✓ Device✓ Connection

TrafficShop macros mapped to report columns

sub-source level judged

no-hop

one script, nothing added to the click path

Valid / Invalid

a verdict on every visit

01 / SIGNAL

How bot traffic slips in through TrafficShop sites.

TrafficShop is a pop / pop-under channel — exactly where invalid traffic concentrates. See which TrafficShop publishers, placements and sub-sources send real clicks versus bots, attributed via TrafficShop’s own tracking tokens and judged Valid or Invalid per source.

02 / VERDICTS

What TrafficShop lets you judge by.

Publisher / site / zone

Invalid share broken down by:

Site ID [site_id]

Per-click id: TrafficShop passes a unique click id, and ValidVisit stores it with each visit, so a verdict traces back to the click in TrafficShop’s own reports.

Compare bot & invalid-traffic breakdown across every ad network →

See your own TrafficShop sub-sources judged this way.

03 / ATTRIBUTION

How ValidVisit attributes TrafficShop traffic

Each TrafficShop macro maps to a normalized parameter, so every judged visit is pinned to the right campaign, creative and publisher.

validvisit · tracking url

Tracking URL for TrafficShop, ready for ValidVisit

https://yoursite.com/landing?utm_source=trafficshop&utm_medium=pop&vv_click_id=[click_id]&vv_campaign_id=[camp_id]&vv_publisher_id=[site_id]&vv_ad_id=[ad_id]

All TrafficShop tracking tokens →

Token	TrafficShop macro	Maps to	Identifies
Click ID	`[click_id]`	click_id	click
Campaign ID	`[camp_id]`	campaign_id	campaign
Site ID	`[site_id]`	publisher_id	publisher
Ad ID	`[ad_id]`	ad_id	ad

Click ID

TrafficShop macro: [click_id]
Maps to: click_id
Identifies: click

Campaign ID

TrafficShop macro: [camp_id]
Maps to: campaign_id
Identifies: campaign

Site ID

TrafficShop macro: [site_id]
Maps to: publisher_id
Identifies: publisher

Ad ID

TrafficShop macro: [ad_id]
Maps to: ad_id
Identifies: ad

Macros not yet checked against TrafficShop’s documentation.

The verdict works the same way on every network. ValidVisit never changes your TrafficShop account: you make the exclusion there yourself. How the verdict works →

FAQ

TrafficShop traffic quality, answered.

How does ValidVisit detect invalid TrafficShop traffic?

Every TrafficShop visit is checked against 100+ independent data points spanning the network it came from, the device behind it and the page it loaded. One thing a real visitor cannot produce makes it Invalid; otherwise it is Valid, with its evidence either way.

Can I see which TrafficShop publishers send bots?

Yes. Using TrafficShop's own tracking tokens, ValidVisit attributes each judged visit to the publisher, placement and sub-source, so invalid traffic is pinned to the exact sub-source — which you can then exclude manually in TrafficShop.

Does it require a funnel hop on my TrafficShop links?

No. Detection runs from one lightweight script — no extra hop, no link rewriting, no change to your TrafficShop destination URLs.