Yeesshh tracking tokens & macros
Yeesshh names its own documentation hub 'traffic-transparency,' which is a bold word choice for a pop network — pop inventory is famously the hardest format to see into once a click leaves your dashboard. The macros below are what actually cash in that promise: append them and every visit arriving from Yeesshh carries the publisher feed, sub-placement, and ad IDs needed for ValidVisit to attribute and score it 0-100, instead of landing in your funnel as one anonymous pop click.
Cross-check any macro against the network’s official documentation. Yeesshh official docs →
The macro that makes everything else possible is {conversion}, Yeesshh's required click id — without it, a visit has nothing to key against in the network's own logs, and ValidVisit has nothing to attribute either. {pubfeed} names the publisher feed a click actually came out of, and {subid} goes a level deeper, isolating the sub-placement inside that feed, which is often where a single 'good' feed turns out to be carrying one bad placement and several clean ones. {banner} records which ad unit fired, and {keyword} captures the term Yeesshh matched against, when the buy is keyword-targeted. None of these require a script, pixel drop, or app install on your end — they're plain query-string tokens on your landing page URL, and Yeesshh's ad server fills each {token} in before the click ever reaches you.
Pop traffic lives or dies at the feed-and-placement level, not the campaign level — a Yeesshh campaign that looks mediocre in aggregate is usually a handful of clean feeds subsidizing one or two placements that are basically bot farms wearing a publisher ID. Splitting every visit by {pubfeed} and {subid} is what lets ValidVisit hand you a score per placement instead of one blended number that tells you nothing about where to cut. From there the work moves off ValidVisit entirely: scoring and attribution happen automatically as clicks arrive, but pulling a feed or sub-placement out of rotation is something only you can do, inside Yeesshh's own campaign settings, once you've decided which IDs earned it.
Yeesshh macro → ValidVisit param
| Token | Yeesshh macro | ValidVisit param | Example |
|---|---|---|---|
| Click ID *click | {conversion} | vv_click_id | abc123xyz |
| Publisher Feed IDpublisher | {pubfeed} | vv_publisher_id | pub_42 |
| Publisher Feed SubIDplacement | {subid} | vv_placement_id | plc_7 |
| Ad IDad | {banner} | vv_ad_id | 456789 |
| Keywordkeyword | {keyword} | vv_keyword | running shoes |
- Yeesshh macro
{conversion}- ValidVisit param
vv_click_id- Example
- abc123xyz
- Yeesshh macro
{pubfeed}- ValidVisit param
vv_publisher_id- Example
- pub_42
- Yeesshh macro
{subid}- ValidVisit param
vv_placement_id- Example
- plc_7
- Yeesshh macro
{banner}- ValidVisit param
vv_ad_id- Example
- 456789
- Yeesshh macro
{keyword}- ValidVisit param
vv_keyword- Example
- running shoes
* required for Yeesshh attribution.
Ready-to-use Yeesshh tracking URL
https://yoursite.com/landing?utm_source=yeesshh&utm_medium=pop&vv_click_id={conversion}&vv_publisher_id={pubfeed}&vv_placement_id={subid}&vv_ad_id={banner}&vv_keyword={keyword}Append these params to your landing-page URL — Yeesshh fills the macros at click time, so every visit arrives attributed and ready to score. No funnel hop.
The buyer pastes the bad combinations into the campaign’s blacklist field in "TQ & Analytics", one per line in the format pubfeed.subid (e.g. 72179.69641); a Whitelist-Only mode accepts the same format, and an optional auto-blacklister blocks any feed SubID that reaches N clicks with zero conversions.
Yeesshh tracking token FAQs
What happens if I drop {conversion} from my Yeesshh tracking URL?+
Without {conversion}, Yeesshh has no click id to log against, and ValidVisit has no key to attribute the visit to a feed or placement. It falls back to being counted as an untagged click, so always keep {conversion} in the URL.
What's the difference between {pubfeed} and {subid}?+
{pubfeed} identifies the publisher feed a click came from; {subid} narrows that down to the specific sub-placement inside the feed. Include both — {subid} is usually the finer unit you'll want to act on.
Does ValidVisit pause a bad Yeesshh feed automatically?+
No. ValidVisit scores and reports which feed or sub-placement is producing invalid traffic, but pulling it out of rotation is a manual step you take inside Yeesshh's own dashboard.
Score every Yeesshh click — and find the fake ones.
See which Yeesshh 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