Publisher Independence
Prebid vs Open Bidding vs Amazon TAM and APS: How the Three Demand Paths Differ
Published · Last updated
Next scheduled review:
Header bidding vs Open Bidding comes down to who runs the auction. Prebid is free, open-source software that the publisher runs. Google's Open Bidding runs inside Google Ad Manager and pays out net of Google's share. Amazon Publisher Services runs its own server-side marketplace, and its TAM charges bidders a 2.5% fee (APS).
Contents
Key facts
- Prebid costs nothing to license. Prebid "is free and fully open source"; Prebid.js launched in 2015 (Prebid.org, accessed 9 November 2026), and Prebid.org was formed in September 2017 as a member-funded body (Prebid.org).
- Open Bidding pays net of a Google share. Publishers are paid "net of Google's revenue share" about 30 days after the end of each month (Google Ad Manager Help, accessed 9 November 2026). The UK regulator found the fee was "typically 5% of the SSP's bid" in 2019 (CMA, Appendix R, 1 July 2020).
- Amazon's TAM publishes its fee. It charges "a transparent 2.5% service fee" to bidders, works with "50+ buyers" and pays publishers once, within 60 days (APS, accessed 9 November 2026).
- Amazon now plugs into Prebid. An official
apsadapter exists for Prebid.js and Prebid Server; the server version is in limited beta (Prebid.org, accessed 9 November 2026). - Google lists 36 Open Bidding partners. The list includes Index Exchange, Magnite DV+, OpenX and PubMatic, and some exchanges ask not to be named (Google Ad Manager Help, accessed 9 November 2026).
- The remedies favour Prebid. Google must connect AdX and its ad server to Prebid, and final judgment was still pending at the end of October 2026 (Alphabet 10-Q, Q3 2026).
Definition
Open Bidding: a Google Ad Manager feature that calls invited third-party exchanges server to server and ranks their bids against AdX and direct line items in one auction (Google Ad Manager Help).
Header bidding is the wider method: collecting bids from several exchanges before the ad server decides. The full explanation is in header bidding explained. The client-side versus server-side question has its own page: header bidding vs server-side bidding.
Header bidding vs Open Bidding: where each auction runs
The three paths differ first in where the competition happens and who controls it.
Prebid. The publisher loads Prebid.js on the page, or calls Prebid Server. Prebid asks each chosen bidder for a price, waits until a timeout, then passes the best bids to the ad server as key-values. Prebid can also act as the final decision layer if the publisher wants (Prebid.org).
Open Bidding. The page calls Google Ad Manager with the normal Google tag. Ad Manager sends bid requests to the exchanges in each eligible yield group, they run their own auctions, and their best bids compete with AdX and direct line items (Google Ad Manager Help). Google sets the reserve price and sends it to all bidders.
Amazon TAM and UAM. The page makes one call to Amazon's server, which gathers bids from Amazon and other buyers. The winning bids return to the page and are passed to the ad server (APS). TAM needs Amazon's multi-slot tag and a contract with each demand partner. UAM is invitation-only and aimed at web publishers on Google Ad Manager (APS UAM).
5 of 5 rows
Who runs the auction | The publisher, in the browser or on Prebid Server (Prebid.org) | Google Ad Manager (GAM Help) | Amazon's servers, before the ad server (APS) |
Code on the page | Prebid.js plus one adapter per bidder | Existing Google tag only (GAM Help) | APS tag; one call (APS) |
Contracts | Publisher with each bidder | Publisher with each exchange, plus a Google addendum (GAM Help) | TAM: one click-through agreement plus a contract with each partner; UAM: by invitation (APS) |
Who pays the publisher | Each bidder, on its own terms | Google, about 30 days after month end (GAM Help) | Amazon, one payment within 60 days (APS) |
Formats | Display, video, native; apps through Prebid Mobile (Prebid.org) | Web, app and video; varies by exchange (GAM Help) | Display, pre-roll video; streaming TV in open beta (APS) |
Who runs the auction
- Prebid
The publisher, in the browser or on Prebid Server (Prebid.org)
- Google Open Bidding
Google Ad Manager (GAM Help)
- Amazon TAM / UAM
Amazon's servers, before the ad server (APS)
Code on the page
Contracts
Who pays the publisher
Formats
- Prebid
Display, video, native; apps through Prebid Mobile (Prebid.org)
- Google Open Bidding
Web, app and video; varies by exchange (GAM Help)
- Amazon TAM / UAM
Display, pre-roll video; streaming TV in open beta (APS)
Table by AdSovereign, CC BY 4.0.
Prebid vs header bidding: the method and the software
People search "prebid vs header bidding" as if they were rivals. They are not. Header bidding is the method; Prebid is the most widely used open-source software for it, maintained by Prebid.org (Prebid.org). Other wrappers exist, and some commercial ones are built on Prebid code.
The suite has three parts. Prebid.js runs in the browser. Prebid Server runs the same auction on a server, which suits apps, AMP pages and streaming TV. Prebid Mobile is the app SDK (Prebid.org). Prebid Server ships as source code in Go and Java, with no configuration tools from the open-source project. Most publishers use a hosted version from a member company (Prebid Server overview). Running it yourself is covered in the Prebid Server self-hosting guide.
The bidder directory lists more than 700 entries, including aliases (Prebid.org bidders, accessed 9 November 2026). Prebid's own guidance is that client-side setups "typically use 5 to 15 demand partners", with more on the server (Prebid.org).
Amazon Publisher Services: TAM, UAM and the Prebid adapter
Amazon Publisher Services (APS) sells publisher tools under the A9.com company. Its two header bidding products differ in who holds the buyer contracts (APS, accessed 9 November 2026).
Transparent Ad Marketplace (TAM) is open to publishers that integrate the multi-slot APS tag. The publisher contracts with each demand partner, and Amazon charges bidders a 2.5% service fee. APS says publishers can see "the record of each auction", including each bidder, bid and winner (company claim) (APS).
Unified Ad Marketplace (UAM) is invitation-only. It is "designed for web publishers who directly or exclusively represent their site" and use Google Ad Manager. Amazon brings the buyers, which include OpenX, PubMatic, Magnite and Index Exchange (APS UAM). UAM's fee is not published.
The Prebid adapter. APS demand is now reachable through Prebid with the bidder code aps. APS is listed as a Prebid.org member, supports the SupplyChain object and deals, and has IAB Global Vendor List ID 793 (Prebid.org). The Prebid Server version needs an APS account and is in limited beta. For publishers this means Amazon demand can sit inside a Prebid auction instead of a separate tag.
Fees on each path
Each path has its own fee, and the exchange fee still applies on top. The table lists what is public today.
4 of 4 rows
Software licence | None; Apache licence (Prebid.org) | Included in Ad Manager | None stated | None stated |
Path fee | None from Prebid.org; hosted Prebid Server fees n/d | Google revenue share; "typically 5% of the SSP's bid" in 2019 (CMA) | 2.5% service fee charged to bidders (APS) | n/d |
Exchange (SSP) fee | Each SSP's own rate | Each exchange's own rate | Each buyer's own terms | Set by Amazon's buyer contracts; n/d |
Who invoices | Each SSP | Google, itemised by exchange (GAM Help) | Amazon | Amazon |
Software licence
- Prebid
None; Apache licence (Prebid.org)
- Google Open Bidding
Included in Ad Manager
- Amazon TAM
None stated
- Amazon UAM
None stated
Path fee
Exchange (SSP) fee
- Prebid
Each SSP's own rate
- Google Open Bidding
Each exchange's own rate
- Amazon TAM
Each buyer's own terms
- Amazon UAM
Set by Amazon's buyer contracts; n/d
Who invoices
- Prebid
Each SSP
- Google Open Bidding
Google, itemised by exchange (GAM Help)
- Amazon TAM
Amazon
- Amazon UAM
Amazon
Table by AdSovereign, CC BY 4.0.
Worked example. Suppose an exchange's best bid is a $4.00 CPM. Through Open Bidding at the 2019 typical rate of 5%, Google keeps $0.20 per thousand and the publisher is paid $3.80 (CMA, Appendix R). Through TAM, the 2.5% fee falls on the bidder, which is $0.10 per thousand at the same price (APS).
A bidder that prices the TAM fee in may bid lower, so the publisher still bears some of it. Through Prebid, no path fee applies, but a hosted Prebid Server contract may add one. These are our calculations on published rates (APS); the current Open Bidding rate is not public.
The SSP fee is the larger number in every case. The industry studies on it are summarised in the ad tech tax explained.
Transparency and data access
What you can see differs by path.
- Prebid keeps the auction in the publisher's hands. Analytics adapters send every bid, timeout and win to the publisher's own analytics (Prebid.org). The code is public, so the auction logic can be read.
- Open Bidding reports aggregated impressions, revenue, bid requests and responses by exchange and yield group (Google Ad Manager Help). Google says no bidder sees another's bid before the auction ends, and the highest net bid wins (Google Ad Manager Help).
- Amazon TAM offers auction-level records (company claim) (APS). UAM's reporting detail is not documented on its public page.
One detail matters for brand safety. Ad Manager's protections, such as blocking rules, "do not apply to Open Bidding partners by default"; publishers must turn on creative filtering per partner (Google Ad Manager Help).
Latency: what each vendor says
There is no neutral, current benchmark that measures all three paths on the same pages. What exists are the vendors' own descriptions.
- Google says Open Bidding "reduces the latency historically associated with header bidding", because it needs no extra page code (company claim) (Google Ad Manager Help).
- Amazon says TAM handles bidding from the server after one ad call (company claim) (APS).
- Prebid recommends fewer client-side bidders, moving bidders to Prebid Server, a firm timeout and A/B tests of each setting (Prebid.org).
The honest test is your own. Run each setup on a share of traffic and compare revenue per thousand page views, not just CPM.
Google Open Bidding partners
Google's help page named 36 Open Bidding partners when we checked it on 9 November 2026 (Google Ad Manager Help). They are listed below in alphabetical order.
9 of 9 rows
Ad Generation | InMobi | Ogury | ShareThrough |
Adagio | LoopMe | OneTag | Smaato |
Bidease | Luna Media | OpenX | Sonobi |
Chocolate Platform (Silverpush) | Magnite DV+ | Opera | Sovrn |
Equativ | Media.net | Outbrain | Tappx |
Exte | MobFox | Playstream | TripleLift |
Fluct | MobileFuse | PubMatic | Verve Group |
Improve Digital | Nativo | Rise | Yieldmo |
Index Exchange | Nexxen | Seedtag | YieldOne |
Ad Generation
- I to N
InMobi
- O to S
Ogury
- S to Y
ShareThrough
Adagio
- I to N
LoopMe
- O to S
OneTag
- S to Y
Smaato
Bidease
- I to N
Luna Media
- O to S
OpenX
- S to Y
Sonobi
Chocolate Platform (Silverpush)
- I to N
Magnite DV+
- O to S
Opera
- S to Y
Sovrn
Equativ
- I to N
Media.net
- O to S
Outbrain
- S to Y
Tappx
Exte
- I to N
MobFox
- O to S
Playstream
- S to Y
TripleLift
Fluct
- I to N
MobileFuse
- O to S
PubMatic
- S to Y
Verve Group
Improve Digital
- I to N
Nativo
- O to S
Rise
- S to Y
Yieldmo
Index Exchange
- I to N
Nexxen
- O to S
Seedtag
- S to Y
YieldOne
Table by AdSovereign, CC BY 4.0.
The page adds: "Some exchanges participate in Open Bidding, but have requested not to be listed." It also limits some partners by region, such as Improve Digital, Magnite Streaming and Nativo. A publisher needs its own contract with any partner before Google can connect it.
What the Google remedies change for each path
On 2 September 2026 Judge Brinkema ordered conduct remedies instead of a sale of AdX; the opinion was unsealed on 16 September (AdExchanger, 16 September 2026). Alphabet said on 28 October 2026 that final judgment had not been entered and that it plans to appeal once it is (Alphabet 10-Q, Q3 2026). The timetable below runs from an Effective Date 60 days after entry.
4 of 4 rows
AdX bids available inside Prebid | AdX demand can compete in the publisher's own auction | Less reason to keep AdX and exchanges inside Ad Manager | Amazon and AdX bids can meet in one Prebid auction | |
DFP to Prebid Server link (12 months); second link for guaranteed and preferred deals (15 months) | Server-side Prebid can bid straight into Google's ad server | No direct change | No direct change | |
Header Bidding Trafficking for every DFP customer within six months | Easier line-item setup for small publishers | Removes one reason smaller publishers chose Open Bidding | Same benefit for APS line items | |
Unified Pricing Rules deprecated for indirect demand; First Look and Last Look barred | Floors can differ by exchange again | Same | Same |
AdX bids available inside Prebid
- Prebid path
AdX demand can compete in the publisher's own auction
- Open Bidding path
Less reason to keep AdX and exchanges inside Ad Manager
- Amazon path
Amazon and AdX bids can meet in one Prebid auction
- Source
DFP to Prebid Server link (12 months); second link for guaranteed and preferred deals (15 months)
- Prebid path
Server-side Prebid can bid straight into Google's ad server
- Open Bidding path
No direct change
- Amazon path
No direct change
- Source
Header Bidding Trafficking for every DFP customer within six months
- Prebid path
Easier line-item setup for small publishers
- Open Bidding path
Removes one reason smaller publishers chose Open Bidding
- Amazon path
Same benefit for APS line items
- Source
Unified Pricing Rules deprecated for indirect demand; First Look and Last Look barred
- Prebid path
Floors can differ by exchange again
- Open Bidding path
Same
- Amazon path
Same
- Source
Table by AdSovereign, CC BY 4.0.
PubMatic put the engineering work for the Prebid integration at roughly a year to 15 months (PPC Land, 6 October 2026). We found no remedy aimed at Open Bidding itself in the published summaries. The publisher-side detail is in Google ad tech remedies explained, and the move to a rival ad server is in switch ad servers without losing AdX demand.
Which path fits which publisher
These criteria follow from the documented mechanics. Many publishers run more than one path.
Prebid fits when you have engineers or a managed partner, want every bid in your own data, and plan to use AdX inside Prebid once the remedies take effect.
Open Bidding fits when you want extra exchanges without page code and accept Google's share and aggregated reporting. It also suits app publishers already on Google's SDK.
Amazon TAM fits when you want Amazon's demand plus your own buyer contracts through one server call, with a published fee. UAM fits when you are invited and prefer Amazon to hold the buyer contracts.
The Google Ad Manager vendor profile covers the ad server these paths plug into. The wider series on running your own sell-side stack is in the publisher independence hub.
FAQ
What is Open Bidding in Google Ad Manager?
Is header bidding better than Open Bidding?
What is Amazon Publisher Services?
What is the difference between Prebid and header bidding?
Who are Google's Open Bidding partners?
Can I run Prebid, Open Bidding and Amazon together?
aps adapter (Prebid.org). Open Bidding runs inside Ad Manager after the header auction. Avoid calling the same exchange through two paths, which duplicates the auction.How this works on owned infrastructure
The question on this page is who runs the auction and who keeps the bid data. AdSovereign is an enterprise RTB stack (DSP, SSP, exchange, DMP and clean room) that a publisher can deploy on its own servers, next to a self-hosted Prebid Server. The exchange then runs on the publisher's infrastructure: every bid, timeout and clearing price is logged there, and the fee model is a fixed licence rather than a share of each bid. Google and Amazon demand still arrive through their own contracts and paths. The architecture page shows where the exchange sits, and integrations lists the supported connections.
Sources
- Prebid.org, "Introduction to Prebid" (accessed 9 November 2026). https://docs.prebid.org/overview/intro.html
- Prebid.org, "What is Prebid.org" (accessed 9 November 2026). https://docs.prebid.org/overview/what-is-prebid-org.html
- Prebid.org, "Prebid Server overview" (accessed 9 November 2026). https://docs.prebid.org/prebid-server/overview/prebid-server-overview.html
- Prebid.org, "APS" bidder adapter documentation (accessed 9 November 2026). https://docs.prebid.org/dev-docs/bidders/aps.html
- Prebid.org, bidder directory (accessed 9 November 2026). https://docs.prebid.org/dev-docs/bidders.html
- Google, Ad Manager Help, "Introduction to Open Bidding" (accessed 9 November 2026). https://support.google.com/admanager/answer/7128453?hl=en
- Google, Ad Manager Help, "How Open Bidding works" (accessed 9 November 2026). https://support.google.com/admanager/answer/7128958?hl=en
- Google, Ad Manager Help, "Open Bidding payments" (accessed 9 November 2026). https://support.google.com/admanager/answer/9752368?hl=en
- Amazon Publisher Services, "Transparent Ad Marketplace" (accessed 9 November 2026). https://aps.amazon.com/aps/transparent-ad-marketplace/
- Amazon Publisher Services, "Unified Ad Marketplace" (accessed 9 November 2026). https://aps.amazon.com/aps/unified-ad-marketplace/
More sources (5)
- Amazon Publisher Services, home page (accessed 9 November 2026). https://aps.amazon.com/aps/index.html
- UK Competition and Markets Authority, "Appendix R: fees in the adtech stack" (1 July 2020). https://assets.publishing.service.gov.uk/media/5fe49625e90e071207e10eff/Appendix_R_-_fees_in_the_adtech_stack_WEB.pdf
- AdExchanger, "The Court Just Unsealed Judge Brinkema's Remedies Decision In The Google Ad Tech Antitrust Case. Here's Your TL;DR" (16 September 2026). https://www.adexchanger.com/platforms/the-court-just-unsealed-judge-brinkemas-remedies-decision-in-the-google-ad-tech-antitrust-case-heres-your-tldr/
- PPC Land, "DOJ seeks 6 months, Google 12, to open its ad exchange to rivals" (6 October 2026). https://ppc.land/doj-seeks-6-months-google-12-to-open-its-ad-exchange-to-rivals/
- Alphabet Inc., Form 10-Q for the quarter ended 30 September 2026 (signed 28 October 2026). https://www.sec.gov/Archives/edgar/data/1652044/000165204426000084/goog-20260930.htm