Which Yahoo Native (DSP / Gemini) site domains send bot traffic?
ValidVisit judges every Yahoo Native visit by publisher sub-source, surfacing which Gemini placements drive IVT so you can exclude them inside Yahoo DSP.
Platform changed: Yahoo Gemini / Yahoo Native shut down in 2023; Yahoo’s native inventory is now bought through the Yahoo DSP and its Taboola partnership. See Taboola →
site domain / mobile app ID / seller ID 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.
{id}/targeting, type SITE_LISTS, excluded:true; lists managed at the advertiser or account-level Inventory Lists library)How bot traffic slips in through Yahoo Native (DSP / Gemini) site domains.
Yahoo Native (formerly Yahoo Gemini), now bought through the Yahoo DSP, places in-feed and content-recommendation ads across Yahoo-owned properties and third-party publisher sites. That dual inventory gives it scale, and it makes publisher sub-source quality the central question: when your creative runs inside a third-party feed, the quality of each click depends on the specific site serving it, not on Yahoo’s inventory as a whole. The ${CC} click ID, with {campaignid} and {adgroupid}, ties each visit’s verdict to its campaign and ad group without interfering with the Yahoo DSP’s own attribution.
The dominant pattern in Yahoo’s third-party publisher inventory is supply-chain inflation: a publisher acquires traffic through low-cost sources such as push, pop or incentivized browsing, then monetizes the resulting pageviews through native placements. The clicks that flow from this reach your landing page and leave without engagement. At campaign level the volume looks unremarkable; it only becomes legible when cut by sub-source.
Every judged visit carries the ${CC} click ID, so low-quality traffic traces back to the ad group and campaign that produced it, and from there to the sites and apps worth excluding.
What to watch on Yahoo Native (DSP / Gemini)
When a disproportionate share of low-quality clicks concentrates in one or a few ad groups, it usually reflects publisher sub-source quality rather than a creative or targeting problem. Cutting the ValidVisit report by Ad Group ID ({adgroupid}) alongside the ${CC} click ID shows which groups are serving inflated-traffic inventory and where a bid reduction or site-list exclusion belongs.
Bot-generated and incentivized clicks from content-feed arbitrage publishers share a pattern: no scroll, no secondary navigation, no meaningful dwell. Tracking it against the verdict per Campaign ID ({campaignid}) and Ad Group ID ({adgroupid}) identifies problem placements before conversion data accumulates and misleads the DSP’s optimization.
What Yahoo Native (DSP / Gemini) lets you judge by.
Yahoo Native (DSP / Gemini) exposes campaign-level tokens; we break invalid traffic down by campaign and per-click id, and surface the offending networks and devices behind the bot clicks.
Per-click id: Yahoo Native (DSP / Gemini) passes a unique click id, and ValidVisit stores it with each visit, so a verdict traces back to the click in Yahoo Native (DSP / Gemini)’s own reports.
Compare bot & invalid-traffic breakdown across every ad network →See your own Yahoo Native (DSP / Gemini) sub-sources judged this way.
How ValidVisit attributes Yahoo Native (DSP / Gemini) traffic
Each Yahoo Native (DSP / Gemini) macro maps to a normalized parameter, so every judged visit is pinned to the right campaign, creative and publisher.
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}| Token | Yahoo Native (DSP / Gemini) macro | Maps to | Identifies |
|---|---|---|---|
| Campaign ID | {campaignid} | campaign_id | campaign |
| Ad Group ID | {adgroupid} | adset_id | adset |
| Ad ID | {adid} | ad_id | ad |
| Creative ID | {creative} | creative_id | creative |
| Click ID (Yahoo DSP / Enhanced Attribution) | ${CC} | click_id | click |
- Yahoo Native (DSP / Gemini) macro
{campaignid}- Maps to
- campaign_id
- Identifies
- campaign
- Yahoo Native (DSP / Gemini) macro
{adgroupid}- Maps to
- adset_id
- Identifies
- adset
- Yahoo Native (DSP / Gemini) macro
{adid}- Maps to
- ad_id
- Identifies
- ad
- Yahoo Native (DSP / Gemini) macro
{creative}- Maps to
- creative_id
- Identifies
- creative
- Yahoo Native (DSP / Gemini) macro
${CC}- Maps to
- click_id
- Identifies
- click
Macros not yet checked against Yahoo Native (DSP / Gemini)’s documentation. Yahoo Native (DSP / Gemini) docs
The verdict works the same way on every network. ValidVisit never changes your Yahoo Native (DSP / Gemini) account: you make the exclusion there yourself. How the verdict works →
Yahoo Native (DSP / Gemini) traffic quality, answered.
Does ValidVisit interfere with Yahoo DSP’s own click measurement or the ${CC} attribution token?
No. The ${CC} click ID Yahoo appends to your destination URL is read as a session identifier, not modified or consumed. Yahoo DSP’s click measurement and Enhanced Attribution both operate on the original click event, which ValidVisit never touches.
How do I exclude sites or apps in the Yahoo DSP?
Build a Site List, App List or Seller-ID List in the Inventory Lists library (advertiser or account level) and attach it to the line’s inventory targeting as excluded; every domain, app ID or seller on it stops serving. The Traffic API does the same with the SITE_LISTS target type and excluded:true. ValidVisit reports at the dimensions you pass, so a cluster of Invalid verdicts in one {adgroupid} tells you which line to investigate before you build the list.
ValidVisit judges visits after they arrive — does that mean my budget is already spent before I learn about IVT?
For the clicks already bought, yes. What changes is the data behind your next decisions: inflated sub-sources distort your conversion data and teach the Yahoo DSP’s optimization to favor the wrong placements. Excluding them stops that pollution from compounding.
Can I exclude IP addresses in the Yahoo DSP?
Yes. The Yahoo DSP also targets by OS and OS version, browser, language, device and connection type.
Detect fraud on other native networks
7Search PPC
Adskeeper
Kadam
MediaGo
MGID
NewsBreak AdsWeighing a blocker for native traffic? How ValidVisit compares to Opticks, PureGuard and Adscore.
Find the bots in your Yahoo Native (DSP / Gemini) spend.
See which publishers and placements send real buyers vs bots — every visit judged Valid or Invalid, worst first.
Join the waitlist with just your email · 7-day trial at launch
One script · no cookies · no device IDs · raw IP never stored