Which AdsCompass sources send bot traffic?

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

Not ready? Estimate your invalid clicks →

validvisit · adscompass cut-list

Exclude the bad source in AdsCompass

The buyer takes the bad Source IDs surfaced by their tracker (AdsCompass passes [site_id]/[ad_id]-style macros to trackers) and adds them to the campaign’s Source ID blacklist optimization list, or moves good ones to a whitelist campaign at a higher bid.

Where: Campaign settings, "optimization lists" step of campaign creation (reviews describe it as step 6, "Prepare optimization lists", after targeting/schedule) — lists keyed by Source ID, IP, or ISP acting as whitelist (approved) or blacklist (blocked)

Controls in AdsCompass’s campaign settings

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

AdsCompass 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 AdsCompass sources.

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

02 / VERDICTS

What AdsCompass lets you judge by.

Publisher / site / zone

Invalid share broken down by:

Site ID [site_id]

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

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

See your own AdsCompass sub-sources judged this way.

03 / ATTRIBUTION

How ValidVisit attributes AdsCompass traffic

Each AdsCompass 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 AdsCompass, ready for ValidVisit

https://yoursite.com/landing?utm_source=adscompass&utm_medium=push&vv_click_id=[click_id]&vv_campaign_id=[camp_id]&vv_publisher_id=[site_id]&vv_creative_id=[ad_id]

All AdsCompass tracking tokens →

Token	AdsCompass 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 (Creative) ID	`[ad_id]`	creative_id	creative

Click ID

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

Campaign ID

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

Site ID

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

Ad (Creative) ID

AdsCompass macro: [ad_id]
Maps to: creative_id
Identifies: creative

Macros not yet checked against AdsCompass’s documentation. AdsCompass docs

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

FAQ

AdsCompass traffic quality, answered.

How does ValidVisit detect invalid AdsCompass traffic?

Every AdsCompass 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 AdsCompass publishers send bots?

Yes. Using AdsCompass'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 AdsCompass.

Does it require a funnel hop on my AdsCompass links?

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