Ad tech doesn’t often agree on anything. But one tiny field did it: the transaction ID. Prebid’s recent change set off a chain reaction across Slack groups, partner updates, and LinkedIn think-pieces. DSPs flagged duplication and SPO visibility. Publishers worried about revenue and privacy. Prebid then clarified the rollout and offered a path forward. Here’s the state of play—and a pragmatic plan for the next 90 days.

What actually changed

• TIDs were always optional in Prebid. Support landed in Prebid.js 8 (June 2023). Passing them has always been opt-in based on legal guidance and publisher feedback. That policy did not change. (Prebid)
• In August 2025, Prebid’s Publisher Committee voted to alter TID handling: instead of one global TID per auction, each SSP/bidder gets its own TID. The change shipped in Prebid.js 10.9.
• Adoption is tiny so far. Most sites haven’t jumped major versions. Prebid estimates the new logic is ~1% of Prebid traffic; 99% still send the original global TID where enabled.
• New flexibility is coming. Prebid will add a publisher-selectable setting in the latest Prebid.js so those who opt into TIDs can choose global or SSP-specific. Older versions remain as-is (global).

Why the industry flared up

• DSP perspective: A global TID helps de-duplicate paths, spot resold or repeated auctions, and run cleaner SPO. Fragmenting TID by SSP reduces that cross-exchange line of sight. Several trade posts and briefings echoed this risk.
• Publisher perspective: A per-SSP TID can limit data leakage and reduce unwanted cross-path correlation, which some see as a privacy and yield protection. Commentaries noted that the change “ended universal IDs across exchanges.”
• Standards backdrop: OpenRTB defines the concept and intent of transaction identifiers in the protocol but leaves real-world governance to implementations. That’s why wrapper-level choices like Prebid’s have outsized impact.
• Public discourse: Coverage from PPC Land, Yieldbird, and others amplified confusion about timing, compliance, and intent—prompting Prebid’s official clarification.

What it means for your stack (short and practical)

If you’re a publisher

1. Don’t panic-upgrade. If you haven’t moved to Prebid 10.9+, your current global TID behavior stays when TIDs are enabled. Test before changing.
2. Decide on TIDs at all. They’re still optional. Document why you pass them (or not) and align with legal and revenue goals.
3. When you upgrade, pick a mode intentionally. With the forthcoming setting, choose global for maximum DSP SPO visibility; choose SSP-specific if your priority is leakage control. Pilot on a subset of traffic first.
4. Measure with holdouts. Create a persistent holdout where you keep the old behavior. Track revenue/recipient, complaint rate, win rate, path duplication, and bid density. (Think WSJ-style discipline for experiments.)
5. Communicate with demand. Tell top DSPs which mode you use and on which placements. It reduces troubleshooting time and protects spend continuity (a theme covered widely by trade press).

If you’re an SSP

• Normalize and label. Surface the TID mode (global vs SSP-specific) to buyers. Offer a compatibility flag in reporting and the bidstream notes.
• Help buyers de-dupe. Provide path-level hints (e.g., GPID where supported) so DSPs can maintain auction hygiene even when TIDs are per-SSP. (Google’s Authorized Buyers docs explain GPID intent.)

If you’re a DSP

• Harden dedup logic. Treat TID as one signal, not the only one. Combine with GPID, impression metadata, and supply chain signals.
• Share outcomes back. Tell publishers when per-SSP TIDs break your SPO or frequency caps so they can reconsider modes. Trade blogs noted buyer-side pain points—closing that loop matters.

The bigger picture

Two truths can live together. Global TIDs support market transparency and cleaner buying. SSP-specific TIDs reduce cross-path traceability that some publishers dislike. Prebid’s upcoming choice toggle is a welcome middle path. It lets each side pick an approach, test it, and negotiate. That’s how open ecosystems evolve—out loud, sometimes messily, but forward.

Bottom line: Treat the transaction ID like a product decision, not a default. Write down your objective, test both modes, and share the results. That makes for better auctions today, and a stronger protocol tomorrow—something even Ad Age and TechCrunch readers can get behind when the dust settles.

AdPanorama editors’ note: If you’ve run measured tests on TID modes, we want your charts. Send us anonymized results and we’ll feature the best experiments in a follow-up.