TacoLoco tracking tokens & macros
Push and pop are different animals even when they're bought from the same network. Push traffic lives or dies on subscription velocity — how fast and how cleanly new subscribers accumulate per zone — while pop traffic quality is more about the inventory chain a tab was served through before it ever reached your page. TacoLoco runs both formats through the same four-token macro set, so the pattern worth watching depends on which format a given visit actually came from. Append the tokens below and ValidVisit attributes each TacoLoco visit to its source and zone, then scores it 0-100 regardless of format.
Cross-check any macro against the network’s official documentation. TacoLoco official docs →
{click_id} is the required macro across both TacoLoco formats — it's the unique value stamped on every click that lets ValidVisit match an arriving visit back to its origin. {source_id} identifies the publisher behind the click, and {zone_id} goes a level finer, naming the specific placement within that publisher's inventory — for push that's typically a subscriber zone, for pop it's a placement slot. {camp_id} ties everything back to the campaign. TacoLoco fills in all four automatically the moment a click fires; your only job is adding them, exactly as written, as query parameters on your destination URL, and the same four tokens work whether the traffic behind them is push or pop.
Because push and pop degrade in different ways, having both {source_id} and {zone_id} matters more here than on a single-format network: a push source can look fine in aggregate while one zone quietly fills with stale re-subscribes, and a pop source can look fine while one zone sits deeper in a chain of inventory than the rest. Splitting by zone is what surfaces either pattern instead of averaging it into a campaign-wide number that moves too slowly to catch. As with every network ValidVisit connects to, catching the pattern and fixing it are two separate steps — ValidVisit's part stops at attribution and scoring, and excluding a zone or source from your TacoLoco traffic is something you go do yourself, inside TacoLoco, once you've seen which one is dragging the campaign down.
TacoLoco macro → ValidVisit param
| Token | TacoLoco macro | ValidVisit param | Example |
|---|---|---|---|
| Click ID *click | {click_id} | vv_click_id | abc123xyz |
| Campaign IDcampaign | {camp_id} | vv_campaign_id | 123456 |
| Source IDpublisher | {source_id} | vv_publisher_id | pub_42 |
| Zone IDplacement | {zone_id} | vv_placement_id | plc_7 |
- TacoLoco macro
{click_id}- ValidVisit param
vv_click_id- Example
- abc123xyz
- TacoLoco macro
{camp_id}- ValidVisit param
vv_campaign_id- Example
- 123456
- TacoLoco macro
{source_id}- ValidVisit param
vv_publisher_id- Example
- pub_42
- TacoLoco macro
{zone_id}- ValidVisit param
vv_placement_id- Example
- plc_7
* required for TacoLoco attribution.
Ready-to-use TacoLoco tracking URL
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}Append these params to your landing-page URL — TacoLoco fills the macros at click time, so every visit arrives attributed and ready to score. No funnel hop.
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.
TacoLoco tracking token FAQs
Do push and pop clicks on TacoLoco use different macros?+
No, the same four — click_id, camp_id, source_id, zone_id — apply to both formats. What differs is what to watch: push quality tracks subscription patterns per zone, pop quality tracks placement depth per zone.
What's the difference between {source_id} and {zone_id}?+
{source_id} identifies the publisher running the traffic. {zone_id} is more specific — the individual placement or subscriber zone within that publisher's inventory — and it's usually the finer lever to act on when only part of a source is underperforming.
Is {click_id} required, or can I attribute with just source and zone?+
{click_id} is required. Without it, ValidVisit has no way to match an arriving visit to the click that produced it, even if source_id and zone_id are both present.
Score every TacoLoco click — and find the fake ones.
See which TacoLoco publishers and placements send real buyers vs. bots.
Free trial at launch · just your email
One script · no cookies · no fingerprinting · raw IP never stored