Tracking reference · Native

Yahoo Native (DSP / Gemini) tracking tokens & macros

Every Yahoo Native (DSP / Gemini) tracking macro, and the ValidVisit URL parameter it maps to. Append these to your landing-page URL so each click is attributed to the right campaign, ad, creative and publisher — and judged Valid or Invalid, with its evidence.

Cross-check any macro against the network’s official documentation. Yahoo Native (DSP / Gemini) official docs →

Which Yahoo Native (DSP / Gemini) sources send bots? →

Yahoo Native (DSP / Gemini) macros mapped to attribution

required for attribution

no-hop

one script, no link rewriting

Valid / Invalid

a verdict on every visit

MACRO MAP

Yahoo Native (DSP / Gemini) macro → ValidVisit param

Token	Yahoo Native (DSP / Gemini) macro	ValidVisit param	Example
Campaign ID *campaign	`{campaignid}`	`vv_campaign_id`	url.com?campaignid={campaignid}
Ad Group IDadset	`{adgroupid}`	`vv_adset_id`	url.com?adgroupid={adgroupid}
Ad IDad	`{adid}`	`vv_ad_id`	url.com?adid={adid}
Creative IDcreative	`{creative}`	`vv_creative_id`	url.com?creative={creative}
Click ID (Yahoo DSP / Enhanced Attribution) *click	`${CC}`	`vv_click_id`	https://my.tracker.com/click?vmcid=${CC}

Campaign ID *campaign

Yahoo Native (DSP / Gemini) macro: {campaignid}
ValidVisit param: vv_campaign_id
Example: url.com?campaignid={campaignid}

Ad Group IDadset

Yahoo Native (DSP / Gemini) macro: {adgroupid}
ValidVisit param: vv_adset_id
Example: url.com?adgroupid={adgroupid}

Ad IDad

Yahoo Native (DSP / Gemini) macro: {adid}
ValidVisit param: vv_ad_id
Example: url.com?adid={adid}

Creative IDcreative

Yahoo Native (DSP / Gemini) macro: {creative}
ValidVisit param: vv_creative_id
Example: url.com?creative={creative}

Click ID (Yahoo DSP / Enhanced Attribution) *click

Yahoo Native (DSP / Gemini) macro: ${CC}
ValidVisit param: vv_click_id
Example: https://my.tracker.com/click?vmcid=${CC}

* required for Yahoo Native (DSP / Gemini) attribution.

TRACKING URL

Ready-to-use Yahoo Native (DSP / Gemini) tracking URL

yahoo-native tracking URL

https://yoursite.com/landing
?utm_source=yahoo-native
&utm_medium=native
&vv_campaign_id={campaignid}
&vv_adset_id={adgroupid}
&vv_ad_id={adid}
&vv_creative_id={creative}
&vv_click_id=${CC}

Append these params to your landing-page URL — Yahoo Native (DSP / Gemini) fills the macros at click time, so every visit arrives attributed and ready to judge. No funnel hop.

Using Yahoo Native (DSP / Gemini) tokens?

See which Yahoo Native (DSP / Gemini) sources send bots.

Every visit judged Valid or Invalid, worst source first.
Attributed through the Yahoo Native (DSP / Gemini) tokens above, down to the placement.
Works beside your tracker, with nothing added to the click path.

Yahoo Native (DSP / Gemini) traffic quality →

deal-alerts.example13K71% invalid

zone 44716.1K23% invalid

premium-news.example4.7K2% invalid

WHAT IT JUDGES BY

What Yahoo Native (DSP / Gemini) tokens let you break bots down by

Breakdown the tokens allow

Campaign level only: Yahoo Native (DSP / Gemini) passes no publisher, zone or placement token, so invalid traffic is attributed to the campaign and, where a click id exists, to the click.

Carries a per-click id, stored with each visit so a verdict traces back to the click.

Where you can act, in Yahoo Native (DSP / Gemini)

IP exclusiondocumented
Device targetingdocumented
OS targetingdocumented
Browser targetingdocumented
Connection typedocumented
Languagedocumented

Tokens last verified against Yahoo Native (DSP / Gemini)’s docs on 2026-06-24.

Found a bad site domain / mobile app ID / seller ID? Exclude it in Yahoo Native (DSP / Gemini)

In today’s Yahoo DSP the buyer builds a Site List / App List / Seller-ID List in the shared Inventory Lists library (or via the Traffic API SITE_LISTS target type), attaches it to the line’s inventory targeting with excluded=true, and every domain/app-ID/seller on the list is blocked from serving.

Yahoo DSP: line-level Inventory/Supply targeting — attach Site Lists, App Lists or Seller-ID Lists as included or excluded (API: POST /traffic/lines/{id}/targeting, type SITE_LISTS, excluded:true; lists managed at the advertiser or account-level Inventory Lists library)

FAQ

Yahoo Native (DSP / Gemini) tracking token FAQs

What are Yahoo Native (DSP / Gemini) tracking tokens?+

Yahoo Native (DSP / Gemini) tracking tokens are macros the network fills in automatically at click time — like a click ID or publisher ID — that you append as URL parameters on your landing-page link. ValidVisit reads the resolved values to attribute and judge each visit.

Do I need a funnel hop to use these macros?+

No. These are plain URL parameters appended to your destination URL. Yahoo Native (DSP / Gemini) substitutes the real values at click time, so there’s no funnel hop, link rewrite, or extra script required.

Where do I add these macros in Yahoo Native (DSP / Gemini)?+

Add them to your campaign’s destination or tracking URL in Yahoo Native (DSP / Gemini)’s own dashboard. Once clicks arrive with the macros populated, ValidVisit attributes and judges each visit automatically.

Tracking tokens for other native networks

Taboola tracking tokens Outbrain tracking tokens MGID tracking tokens Revcontent tracking tokens MediaGo tracking tokens Kadam tracking tokens

Is Yahoo Native (DSP / Gemini) traffic real? See how ValidVisit judges every Yahoo Native (DSP / Gemini) visit for bot traffic.

deal-alerts.example13K71% invalid

zone 44716.1K23% invalid

premium-news.example4.7K2% invalid

Judge every Yahoo Native (DSP / Gemini) visit — and find the fake ones.

See which Yahoo Native (DSP / Gemini) 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