Not all TacoLoco traffic is equal. ValidVisit scores every visit 0–100 and pins it to the exact zone that sent it — so you can tell real humans from bots and invalid clicks, worst zones first.
zone in TacoLocoThe 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.
ValidVisit reports the device, OS, browser — down to the version — plus the language and ISP behind every flagged visit, and TacoLoco supports OS, language and device type targeting. The segments we flag are segments you can exclude.
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 scored 0–100 per source.
TacoLoco 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 TacoLoco tokens, not by creative (which says nothing about whether a click was human).
Bought as one TacoLoco line, your spend is a single number. Scored per sub-source it runs from 90 down to 17 — the worst is nearly all bots. That’s the leak a blended average hides.
TacoLoco traffic scored 0–100 per sub-source, worst first — down to the placement you buy.
Bot / invalid-traffic score broken down by:
{source_id}Bot / invalid-traffic score broken down by:
{zone_id}Per-click id: TacoLoco 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 TacoLoco sub-sources scored this way.
Each TacoLoco 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=tacoloco&utm_medium=push&vv_click_id={click_id}&vv_campaign_id={camp_id}&vv_publisher_id={source_id}&vv_placement_id={zone_id}| 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}{camp_id}{source_id}{zone_id}Every visit is weighed against more than a hundred independent data points and reduced to a single, sortable 0–100 quality score.
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.
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.
Every verdict maps to the campaign, publisher and placement that sent the click — so you know exactly which source to cut.
Scoring and attribution are the means — the point is cutting the TacoLoco traffic that wastes your spend. Here's how ValidVisit gets you a list you can act on.
You buy TacoLoco clicks; what arrives are visits. ValidVisit scores each one 0–100 so real humans stand out from bots and invalid traffic — one script, no funnel hop, no fingerprinting.
Every scored visit is tied to the exact TacoLoco zone and zone via the network's own tokens — so the bad traffic has an address, not just a headline percentage.
You get the worst offenders as a ready-to-use list plus postbacks to your tracker — so you can exclude them in TacoLoco and put your next dollar behind the traffic that converts.
Every TacoLoco 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.
Yes. Using TacoLoco'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 TacoLoco.
No. Detection runs from one lightweight script — no extra hop, no link rewriting, no change to your TacoLoco destination URLs.
See which publishers and placements send real buyers vs bots — every visit scored 0–100, worst first.
Free trial at launch · just your email
One script · no cookies · no fingerprinting · raw IP never stored