TrafficHunt tracking tokens & macros
A tagged TrafficHunt destination URL looks like yoursite.com/landing?txn=[txn_id]&camp=[camp_id]&space=[adspace]&banner=[banner]: four tokens covering the click, the campaign, the ad space and the creative. TrafficHunt fills each one at click time, and ValidVisit reads them on arrival, so every visit across TrafficHunt's pop, push, banner and native inventory is attributed to the ad space that produced it, then judged Valid or Invalid, with its evidence.
Cross-check any macro against the network’s official documentation. TrafficHunt official docs →
[txn_id] is the one TrafficHunt insists on: it is the click ID TrafficHunt generates, its postback is keyed on it, and TrafficHunt says it must be in every tracking link of every campaign. ValidVisit stores it on the visit, so a verdict and a conversion line up on the same click. [adspace] identifies the exact ad space your campaign ran on, which is the unit TrafficHunt's own CPA optimizer tests and stops, and the one worth building your reporting around. [camp_id] keeps campaigns apart, and [banner] carries the creative's name.
TrafficHunt's macro list goes further than these four. [source_id] and [source_name] pass the AdSpace ID and name the traffic came from, [sub_id] carries a custom value of your own, and [tid] passes a click ID supplied by the publisher. Add them if you want both the ID and the readable name side by side. None of this changes anything inside TrafficHunt by itself: ValidVisit's job ends at attributing and judging the visit, and the follow-through, cutting an ad space or swapping a banner, happens in your TrafficHunt account.
TrafficHunt macro → ValidVisit param
| Token | TrafficHunt macro | ValidVisit param | Example |
|---|---|---|---|
| Transaction/Click ID *click | [txn_id] | vv_click_id | abc123xyz |
| Campaign IDcampaign | [camp_id] | vv_campaign_id | 123456 |
| Ad Spaceplacement | [adspace] | vv_placement_id | plc_7 |
| Banner (creative name)creative | [banner] | vv_creative_id | 987 |
- TrafficHunt macro
[txn_id]- ValidVisit param
vv_click_id- Example
- abc123xyz
- TrafficHunt macro
[camp_id]- ValidVisit param
vv_campaign_id- Example
- 123456
- TrafficHunt macro
[adspace]- ValidVisit param
vv_placement_id- Example
- plc_7
- TrafficHunt macro
[banner]- ValidVisit param
vv_creative_id- Example
- 987
* required for TrafficHunt attribution.
Ready-to-use TrafficHunt tracking URL
https://yoursite.com/landing?utm_source=traffichunt&utm_medium=pop&vv_click_id=[txn_id]&vv_campaign_id=[camp_id]&vv_placement_id=[adspace]&vv_creative_id=[banner]Append these params to your landing-page URL — TrafficHunt fills the macros at click time, so every visit arrives attributed and ready to judge. No funnel hop.
See which TrafficHunt sources send bots.
- Every visit judged Valid or Invalid, worst source first.
- Attributed through the TrafficHunt tokens above, down to the placement.
- Works beside your tracker, with nothing added to the click path.
What TrafficHunt tokens let you break bots down by
- Ad Space
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 TrafficHunt’s docs on 2026-10-02.
The buyer excludes the bad referring domains under Referers (TrafficHunt’s own push walkthrough builds its whitelist and blacklist there), lets the CPA optimizer stop Adspaces that fail their test budget, and asks support or the account manager to cut a specific [adspace] ID.
TrafficHunt tracking token FAQs
What does a tagged TrafficHunt URL look like?+
Something like yoursite.com/landing?txn=[txn_id]&camp=[camp_id]&space=[adspace]&banner=[banner]. [txn_id] is required, by TrafficHunt for its postback and by ValidVisit to tie the visit to the click; the rest add the campaign, ad space and creative.
What's the difference between [adspace] and [source_id]?+
TrafficHunt documents [adspace] as the exact ad space where your campaign is displayed and [source_id] as the AdSpace ID the traffic was received from, with [source_name] as its readable name. Use [adspace] for the verdict breakdown, and add [source_name] if you want a name next to the ID.
Can I isolate a specific creative's performance?+
Yes, with [banner], which carries the creative's name. Once an ad space's invalid share looks high, the banner breakdown shows whether one creative is responsible or the placement as a whole.
Tracking tokens for other pop / pop-under networks
Judge every TrafficHunt visit — and find the fake ones.
See which TrafficHunt 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