Which TacoLoco zones send bot traffic?

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

Not ready? Estimate your invalid clicks →

validvisit · tacoloco cut-list

Exclude the bad zone in TacoLoco

The buyer pastes/uploads the bad zone or source IDs into a Zone List at my.tacolo.co/lists and attaches that list to an In-Page Push or Direct Clicks campaign as a blacklist (exclude) — or maintains it programmatically via the Zone Lists API.

Where: Advertiser dashboard at my.tacolo.co/lists ("Zone Lists" section), where zone/source IDs are grouped into whitelists/blacklists that are then included/excluded in a campaign’s zone targeting; also manageable via the Advertiser’s API Zone Lists endpoints

Controls in TacoLoco’s campaign settings

✕ IP lists✓ OS✓ Language✓ Device

TacoLoco macros mapped to report columns

2026-10-02

macros checked against TacoLoco’s own docs

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 TacoLoco zones.

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

02 / VERDICTS

What TacoLoco lets you judge by.

Publisher / site / zone

Invalid share broken down by:

Source ID {source_id}

Placement / widget

Invalid share broken down by:

Zone ID {zone_id}

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

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

See your own TacoLoco sub-sources judged this way.

03 / ATTRIBUTION

How ValidVisit attributes TacoLoco traffic

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

https://yoursite.com/landing?utm_source=tacoloco&utm_medium=push&vv_click_id={click_id}&vv_campaign_id={camp_id}&vv_publisher_id={source_id}&vv_placement_id={zone_id}

All TacoLoco tracking tokens →

Token	TacoLoco macro	Maps to	Identifies
Click ID	`{click_id}`	click_id	click
Campaign ID	`{camp_id}`	campaign_id	campaign
Source ID	`{source_id}`	publisher_id	publisher
Zone ID	`{zone_id}`	placement_id	placement

Click ID

TacoLoco macro: {click_id}
Maps to: click_id
Identifies: click

Campaign ID

TacoLoco macro: {camp_id}
Maps to: campaign_id
Identifies: campaign

Source ID

TacoLoco macro: {source_id}
Maps to: publisher_id
Identifies: publisher

Zone ID

TacoLoco macro: {zone_id}
Maps to: placement_id
Identifies: placement

Macros checked against TacoLoco’s own documentation on 2026-10-02. TacoLoco docs

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

FAQ

TacoLoco traffic quality, answered.

How does ValidVisit detect invalid TacoLoco traffic?

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

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

Does it require a funnel hop on my TacoLoco links?

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