OpenAds Signs Its First Publishers. How to Weigh a Wrapper Decision

On January 6, The Trade Desk named the first publishers supporting OpenAds, its new auction environment for publishers and sellers. According to the announcement, the list includes AccuWeather, The Arena Group, BuzzFeed, the Guardian, Hearst Magazines, Hearst TV, Newsweek, People Inc. and Ziff Davis. The company describes OpenAds as an environment where the highest bid wins in a transparent, auditable auction that publishers can independently verify.

For most publishers, the question this raises is practical: add it, switch to it or wait? That is a wrapper decision, and wrapper decisions deserve the same testing discipline as any other change to how your auction runs. Here is the background, what to check in your own setup and a framework for deciding.

How we got here: transaction IDs

The dispute behind OpenAds is about transaction IDs, or TIDs. Prebid generates IDs for auctions and for ad units within an auction. When every SSP passes the same ID, a DSP can recognize that requests arriving through several paths are for the same impression, which helps it deduplicate and choose a path. That same property raises privacy concerns, which is why Prebid.js has disabled TIDs by default since version 8. Publishers have to opt in with enableTIDs.

In 2025 Prebid changed how those IDs behave. According to the Prebid.js configuration docs, in versions 10.9.0 through 10.13.0 transaction IDs are unique for each bidder and cannot be used to correlate requests from different sources, even when enableTIDs is set. Prebid.org said on October 23 that the change followed an August 2025 vote of its Publisher Committee, that the new logic represented about 1% of Prebid traffic, with the rest still sending the original global format, and that publishers on the latest version would be able to choose between global and SSP-specific TIDs. From version 10.14.0, publishers who set enableTIDs can add consistentTIDs: true to restore the earlier global behavior.

The Trade Desk's executives discussed OpenAds publicly in October, describing it as a Prebid wrapper meant to improve supply-chain transparency and give buyers a direct route to publisher inventory. The January announcement is the first public list of publishers backing it.

What each side is arguing

Both positions are about who controls information in the auction.

• The case for global TIDs: buyers can see when the same impression reaches them through multiple paths, which helps them pick the cleanest one and avoid bidding against themselves. The argument is that this supports supply path optimization and rewards publishers whose paths are direct and efficient.
• The case for SSP-specific TIDs: the publisher decides how much impression-level linkage leaves the page. Less cross-path correlation limits what buyers can learn about a publisher's auction, in line with the privacy reasoning that made TIDs opt-in in the first place.

You do not need to settle that argument in the abstract. You need to know what your current setup does and what each option does to your revenue.

Step one: find out what you are sending today

• Check your Prebid.js version. If you run 10.9.0 through 10.13.0 with TIDs enabled, you are sending bidder-specific IDs whether you meant to or not.
• Check whether enableTIDs is set at all. Many sites never turned it on. If yours did not, the TID dispute changes nothing on your pages until you do.
• Ask about server-side paths. If you use Prebid Server or a managed wrapper, ask your provider how TIDs are handled there, since server-side configuration is separate from what runs in the browser.
• Write down your decision. Whichever setting you choose, record why, so the next version upgrade does not silently change it.

Step two: test before you switch

Whether you are evaluating OpenAds, changing TID settings or moving to a new Prebid version, run it as a controlled test against a holdout on your current setup, not as a flip of a switch. Measure revenue per thousand page views rather than CPM alone, and add page performance. Then look at the buyer mix: a change that lifts bids from one DSP while reducing them from others can net out flat or negative, and the only way to see that is to break results out by buyer as well as by SSP.

Step three: questions for any new auction environment

These apply to OpenAds and to any other wrapper or auction product a partner puts in front of you:

• Which SSPs and buyers can participate, and does it change how your existing bidders are called?
• Who hosts and maintains the code, and how quickly are security fixes and new Prebid modules picked up?
• What reporting do you receive, and what logs let you verify the auction outcome yourself?
• How does it interact with Google Ad Manager, your price floors and your identity modules?
• What are the fees, if any, and where in the chain are they taken?
• Can you run it side by side with your current wrapper during a test, and how do you roll back?

Get the answers in writing before you commit. These are the same questions you would put to any wrapper vendor, and a good partner will be glad to answer them.

Step four: keep the basics tight while the debate runs

Whatever you decide about TIDs, the things buyers use to value your inventory have not changed. Keep ads.txt and sellers.json accurate, keep page context clean in the bid request, keep bidder counts sensible and pages fast. Stay on a supported Prebid version rather than freezing on an old one to avoid the question; you give up fixes and new modules for a setting you can now configure directly.

The bigger picture

For years publishers treated the wrapper as plumbing. The TID dispute shows it is also where information policy gets set: what buyers learn about each impression, which paths they favor and who decides. That makes the wrapper a business decision for revenue leaders, not only an engineering ticket, and it should be made with data from your own traffic.

HBDR has worked in header bidding since 2015. If you want help auditing your TID settings or designing a clean test, that is exactly the kind of work a managed ad ops partner should be doing alongside you.