Which TrafficForce sites send bot traffic?
ValidVisit judges every TrafficForce visit Valid or Invalid and pins it to the site that sent it, worst first.
site and channel in TrafficForceThe buyer opens the ad group’s Display Network list, selects the site/channel IDs matching the bad-source list, and clicks "Disable" (disabled entries can later be re-enabled from a Disabled Channels view); channel IDs are captured in tracking via the channel/spot macro so they can be matched back.
How bot traffic slips in through TrafficForce sites.
See which TrafficForce publishers, placements and sub-sources send real clicks versus bots, attributed via TrafficForce’s own tracking tokens and judged Valid or Invalid per source.
What TrafficForce lets you judge by.
Invalid share broken down by:
- Site ID
{site_id}
Invalid share broken down by:
- Channel ID
{channel_id}
Per-click id: TrafficForce passes a unique click id, and ValidVisit stores it with each visit, so a verdict traces back to the click in TrafficForce’s own reports.
Compare bot & invalid-traffic breakdown across every ad network →See your own TrafficForce sub-sources judged this way.
How ValidVisit attributes TrafficForce traffic
Each TrafficForce macro maps to a normalized parameter, so every judged visit is pinned to the right campaign, creative and publisher.
https://yoursite.com/landing?utm_source=trafficforce&utm_medium=banner&vv_click_id={CLICK_ID}&vv_campaign_id={campaign_id}&vv_publisher_id={site_id}&vv_placement_id={channel_id}&vv_ad_id={ad_id}&vv_adset_id={group_id}| Token | TrafficForce macro | Maps to | Identifies |
|---|---|---|---|
| Click ID | {CLICK_ID} | click_id | click |
| Campaign ID | {campaign_id} | campaign_id | campaign |
| Site ID | {site_id} | publisher_id | publisher |
| Channel ID | {channel_id} | placement_id | placement |
| Ad ID | {ad_id} | ad_id | ad |
| Group ID | {group_id} | adset_id | adset |
- TrafficForce macro
{CLICK_ID}- Maps to
- click_id
- Identifies
- click
- TrafficForce macro
{campaign_id}- Maps to
- campaign_id
- Identifies
- campaign
- TrafficForce macro
{site_id}- Maps to
- publisher_id
- Identifies
- publisher
- TrafficForce macro
{channel_id}- Maps to
- placement_id
- Identifies
- placement
- TrafficForce macro
{ad_id}- Maps to
- ad_id
- Identifies
- ad
- TrafficForce macro
{group_id}- Maps to
- adset_id
- Identifies
- adset
Macros checked against TrafficForce’s own documentation on 2026-10-02. TrafficForce docs
The verdict works the same way on every network. ValidVisit never changes your TrafficForce account: you make the exclusion there yourself. How the verdict works →
TrafficForce traffic quality, answered.
How does ValidVisit detect invalid TrafficForce traffic?
Every TrafficForce 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 TrafficForce publishers send bots?
Yes. Using TrafficForce'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 TrafficForce.
Does it require a funnel hop on my TrafficForce links?
No. Detection runs from one lightweight script — no extra hop, no link rewriting, no change to your TrafficForce destination URLs.
Detect fraud on other banner / display networks
TrafficJunky
TwinRed
BIGO Ads
7Search PPC
ExoClick
PlugRushWeighing a blocker for banner / display traffic? How ValidVisit compares to Adscore, TrafficGuard and Opticks.
Find the bots in your TrafficForce spend.
See which publishers and placements send real buyers vs bots — every visit judged Valid or Invalid, worst first.
Join the waitlist with just your email · 7-day trial at launch
One script · no cookies · no device IDs · raw IP never stored