UID2.0 vs Contextual Targeting: Why You Need Both
The post-cookie conversation has split publishers into two camps: those who’ve invested in first-party ID solutions, and those who’ve leaned into contextual targeting. Both approaches have merit. But treating them as alternatives is a mistake.
The case for UID
UID2.0 and similar pseudonymous identifiers solve the cross-site audience targeting problem. When a buyer can recognise a user across multiple publisher contexts, they can build frequency management, run sequential messaging, and attribute conversions. For publishers with a logged-in user base or first-party email collection, UID match rates above 80% are achievable. The revenue uplift from identified vs. anonymous impressions can be substantial — in some categories, a 3–5× CPM difference on matched vs. unmatched inventory.
The case for contextual
But UID doesn’t help with the majority of open-web traffic. Most users are not logged in and have not consented to identity resolution. For those impressions — which can represent 60–70% of total inventory — contextual targeting is the only scalable signal.
“Page-level intent is not a fallback for identity. For buyers running brand campaigns, contextual relevance can be more valuable than audience matching.”
The NinaData Dynamic approach: both, at bid time
NinaData’s Dynamic enrichment layer appends both signals to every eligible bid request — UID where available, contextual intent scoring universally. The result is a bid request that gives buyers maximum flexibility: audience targeting where identity is present, contextual targeting everywhere else.
The Dynamic enrichment partnership connects to your existing setup as a standard demand partner. No changes to your Prebid configuration, no new GAM line items. The enrichment happens upstream — on the bid request level — so every buyer in your stack benefits from the improved signals.