Traffic Nomads tracking tokens & macros
Multi-format self-serve networks that bundle push, pop, native, and banner traffic under one account tend to converge on the same shape of macro set: a click identifier, a campaign identifier, and something naming the publisher, kept deliberately lean so it works the same way regardless of format. Traffic Nomads fits that pattern closely. Append its four tokens to your destination URL and ValidVisit attributes every visit, across whichever format sent it, back to the publisher and zone that served it, then judges it Valid or Invalid, with its evidence.
Cross-check any macro against the network’s official documentation. Traffic Nomads official docs →
{clickid} is the required token, a unique identifier Traffic Nomads issues per visit that ValidVisit uses to tie the click back to this network specifically. {pubid} names the publisher account behind the traffic, but {zone} goes a level finer, identifying the specific ad zone or placement within that publisher's inventory, which matters more than it sounds like across four different formats, a publisher running both push and native zones can easily have one performing fine and the other producing mostly noise. {campaignid} rounds things out for reporting, letting you separate results by campaign once you're running more than one through the same account. All four are plain URL parameters that Traffic Nomads fills at click time, no code snippet or extra integration step needed beyond having the tokens present in the link before traffic starts flowing.
A publisher-level view is a reasonable starting point, but with push, pop, native, and banner all sharing one account, the zone is usually where the real difference in traffic quality shows up, two zones under the same publisher can be pulling from very different audiences depending on format and placement. Judging at {zone} rather than stopping at {pubid} is what actually separates a publisher worth keeping from one worth trimming down to its better zones. As with any source ValidVisit judges, the action itself doesn't happen automatically, ValidVisit attributes and reports the invalid share, but cutting a zone off from the campaign is something you do inside Traffic Nomads' own dashboard once you've decided a zone isn't earning its spend.
Traffic Nomads macro → ValidVisit param
| Token | Traffic Nomads macro | ValidVisit param | Example |
|---|---|---|---|
| Click ID *click | {clickid} | vv_click_id | abc123xyz |
| Campaign IDcampaign | {campaignid} | vv_campaign_id | 123456 |
| Publisher IDpublisher | {pubid} | vv_publisher_id | pub_42 |
| Zoneplacement | {zone} | vv_placement_id | plc_7 |
- Traffic Nomads macro
{clickid}- ValidVisit param
vv_click_id- Example
- abc123xyz
- Traffic Nomads macro
{campaignid}- ValidVisit param
vv_campaign_id- Example
- 123456
- Traffic Nomads macro
{pubid}- ValidVisit param
vv_publisher_id- Example
- pub_42
- Traffic Nomads macro
{zone}- ValidVisit param
vv_placement_id- Example
- plc_7
* required for Traffic Nomads attribution.
Ready-to-use Traffic Nomads tracking URL
https://yoursite.com/landing?utm_source=traffic-nomads&utm_medium=push&vv_click_id={clickid}&vv_campaign_id={campaignid}&vv_publisher_id={pubid}&vv_placement_id={zone}Append these params to your landing-page URL — Traffic Nomads fills the macros at click time, so every visit arrives attributed and ready to judge. No funnel hop.
See which Traffic Nomads sources send bots.
- Every visit judged Valid or Invalid, worst source first.
- Attributed through the Traffic Nomads tokens above, down to the placement.
- Works beside your tracker, with nothing added to the click path.
What Traffic Nomads tokens let you break bots down by
- Publisher ID
- Zone
Carries a per-click id, stored with each visit so a verdict traces back to the click.
- IP exclusiondocumented
- Device targetingdocumented
- OS targetingdocumented
- Browser targetingdocumented
- Connection typedocumented
- Languagedocumented
Tokens last verified against Traffic Nomads’s docs on 2026-07-11.
The buyer edits the campaign, pastes the bad publisher/zone ID list into the Publishers field (values separated by a comma and a space), and selects the "Blacklist" option — or ticks/excludes the same IDs one by one from the stats dashboard.
Traffic Nomads tracking token FAQs
What's the difference between {pubid} and {zone}?+
{pubid} identifies the publisher account, while {zone} identifies a specific placement or zone within that account. Publishers running multiple formats can have zones that vary widely in quality, so {zone} is the more useful level for ValidVisit to judge.
Which token is required for attribution to work at all?+
{clickid}. It's the unique identifier Traffic Nomads issues on every click, and without it ValidVisit can't tie a visit back to this network. The other three tokens add detail on top of that.
Does the same macro set work for push, pop, native, and banner?+
Yes. Traffic Nomads uses one macro set across all four formats, so a single destination URL with {clickid}, {campaignid}, {pubid}, and {zone} covers whatever mix of formats a campaign is running.
Tracking tokens for other push networks
Judge every Traffic Nomads visit — and find the fake ones.
See which Traffic Nomads publishers and placements send real buyers vs. bots.
Join the waitlist with just your email · 7-day trial at launch
One script · no cookies · no device IDs · raw IP never stored