Publisher Independence: Guides, Comparisons and Tools

Publisher independence means choosing how inventory is sold, who makes the ad decision, and which data leaves the publisher’s systems. Separate access to demand from control of the ad server.

Start with the business decision and the data flow. Identify who owns the customer relationship, who receives each signal, who runs the decisioning system, and what evidence supports the result. A vendor feature list alone cannot settle those questions.

This guide brings together the reference material for this topic. Comparisons describe different operating models, rather than declaring a universal winner. The linked pages retain source dates, vendor-claim labels and the limits of each example. Read those limits before applying a figure or architecture to your own organization.

The table merges the opinion with the 2 October 2026 joint filing. "Agreed" means the language carries no brackets in Document 1861. "Disputed" means the court still has to choose between the plaintiffs' and Google's versions (PPC Land, 6 October 2026).

What the court refused. Divestiture of AdX; open-sourcing DFP's final auction logic under a neutral administrator; contingent divestiture of DFP Remainder; a 15-year term; an escrow of 50% of AdX and DFP net revenues; anti-retaliation, non-interference and anti-circumvention clauses (too vague under Rule 65(d)); data sharing for all ad formats; and any remedy touching DV360 (PPC Land, 17 September 2026; NatLawReview, 18 September 2026). The court did keep the position that disgorgement is available under the Sherman Act, while rejecting the specific escrow proposal (Memorandum Opinion, Dkt. 1858, pp. 97 to 98).

Read the full google ad tech antitrust remedies explained for publishers guide for context, sources and limitations.

Three threads run through the opinion. First, the legal bar: structural relief needs a "significant causal connection" between the unlawful conduct and the monopoly, following the D.C. Circuit's Microsoft decision, and the court found lawful factors (advertiser demand in Google Ads, cleared acquisitions, sustained investment) contributed substantially to Google's position (NatLawReview, 18 September 2026). Second, practicality: the plaintiffs identified no committed buyer for AdX, comparable migrations took five to eight years, and the court accepted Google's estimate that every behavioral remedy would be "fully in effect within 15 months" (Memorandum Opinion, Dkt. 1858, p. 42; NatLawReview, 18 September 2026). Third, the market itself: the opinion records that indirect open-web display fell from over 40% of Google Ads impressions in January 2019 to 11% in June 2025, and quotes the Microsoft court's line that imposing a remedy on a fast-moving industry "is not unlike trying to shoe a galloping horse" (PPC Land, 17 September 2026; Memorandum Opinion, Dkt. 1858, p. 103).

Read the full google ad tech antitrust remedies explained for publishers guide for context, sources and limitations.

The reactions sort into three camps, and a publisher should read all three before planning.

Read the full google ad tech antitrust remedies explained for publishers guide for context, sources and limitations.

Nothing changes on the day the judgment is entered. The Effective Date is 60 days later, and the items that touch yield come 6 to 15 months after that. What changes in the meantime is the information available to you and the options you can credibly plan for.

Read the full google ad tech antitrust remedies explained for publishers guide for context, sources and limitations.

• Formats. D = open-web display, V = online video, CTV = connected TV and streaming, App = in-app. Based on vendor pages unless stated.
• Header bidding. Whether the server runs or integrates a Prebid auction, or offers its own unified auction.
• AdX access after remedies. For display servers: "eligible" means the server can receive real-time AdX bids under the court order once Google ships the integration and the vendor builds the receiving side; no vendor had announced a build as of 17 October 2026. For video and CTV servers: "not covered," because the remedies exclude video (PPC Land, 17 September 2026). Today, every rival server reaches AdX only through a Google Ad Manager account; the mechanics are in how to switch ad servers without losing AdX demand.
• Pricing. Public prices are quoted with the page and access date. "Quote" means the vendor publishes no price.
• Self-hosting. Whether you can run the software on your own servers or cloud account.
• Log-level data. Whether event-level logs are available and on what terms.
• Notable publishers. Only names with a public source. Vendor logo walls are reported as "company site" and treated as company claims.

Read the full google ad manager alternatives 2026: 19 ad servers compared guide for context, sources and limitations.

Long tail (names only, from Kevel's list, not evaluated here): AdGlare (above), Adhese, AdPlugg, AdSpeed, AdSpirit, AdvertServe, Avid, iBillboard, InClick, Lite, UpRival, Zedo; self-hosted OIO, dJax, InOut; email Passendo, PowerInbox; WordPress plug-ins AdInserter, Advanced Ads, AdRotate (Kevel, updated 30 April 2026).

Why Yieldmo and the SSPs are not rows. Yieldmo, Index Exchange, OpenX, PubMatic, Magnite DV+ and TripleLift appear in Google's list of Open Bidding yield partners; they are exchanges that bid into an ad server, not ad servers (Google Help, Open Bidding, accessed 17 October 2026). They matter to this page as the demand you keep when you change servers, which is the subject of how to switch ad servers without losing AdX demand.

Read the full google ad manager alternatives 2026: 19 ad servers compared guide for context, sources and limitations.

Managed Prebid hosts. The 21 providers on Prebid.org's list sell the same software as a service, usually for a revenue share that none publishes (Prebid.org managed services, accessed 17 October 2026). After the remedies they will carry the AdX adapter too, so the question becomes who sees your bid data. The economics of that layer are covered in 12 ad tech cost optimization strategies.

Read the full google ad manager alternatives 2026: 19 ad servers compared guide for context, sources and limitations.

Until the court order is in force, there is exactly one way to receive an AdX bid: through a Google Ad Manager account. Google's contractual and technical tie between DFP and AdX was the conduct the court found unlawful, and the opinion records that Google refused to give rival ad servers or Prebid real-time access to AdX bids (Memorandum Opinion, Dkt. 1858, pp. 1 and 66). A publisher who switched servers before the order therefore had to route the new server's remnant impressions back into a Google Ad Manager account so that AdX could bid on them, which added a hop, a second auction and a second set of fees. That is why most migrations stopped at "run a second server for direct and keep GAM for programmatic."

The order changes the mechanics in three places. First, Google must build an API so Prebid can solicit real-time AdX bids for all indirect open-web display inventory, "functionally equivalent" and on "materially identical terms" to the way DFP solicits them, with no added latency (Memorandum Opinion, Dkt. 1858, p. 62). Second, AdX must submit real-time bids to non-Google publisher ad servers for all indirect demand (PPC Land, 6 October 2026). Third, Google must build tools that let a publisher choose AdX via Prebid or via DFP, not both, and may not vary revenue share, latency, response rate or information by which path you use (PPC Land, 17 September 2026; Memorandum Opinion, Dkt. 1858, p. 74). The deadlines, and which of them are still disputed, are tracked in Google ad tech remedies explained for publishers.

Read the full how to switch ad servers without losing adx demand guide for context, sources and limitations.

Decision rule. If you can wait, do the preparation steps (1 to 7 below) now and the cutover steps (8 to 12) after the AdX adapter ships; that avoids the second hop entirely. If you cannot wait, because a contract ends, a vendor is closing, or the second-hop cost is already being paid, run the pre-remedies path with GAM kept as an AdX-only network, and plan the switch of the AdX feed as a second project. Either way the auction should move to Prebid Server first, because that is where the AdX adapter will land; the options are in the Prebid Server self-hosting guide and the server candidates in Google Ad Manager alternatives.

Read the full how to switch ad servers without losing adx demand guide for context, sources and limitations.

Prebid.org's own guidance is to pick the language your team prefers if the feature set and adapters you need are present in both (PBS-Go versions page, accessed 17 October 2026). In practice the choice is driven by the Java-only list: if you need the USGen module for US state privacy, the circuit breaker or per-account stored requests, pick Java; if you need the legacy schain locations or geo-fencing, pick Go.

Read the full prebid server self-hosting guide: aws, on-prem, managed guide for context, sources and limitations.

The host must handle production networking and monitoring, populate account and stored-request data, and "assess the legal implications of ad tech" in its market; no open-source tooling exists for the data pipeline that fills the stored-request database (Prebid Server hosting, accessed 17 October 2026). A multi-region deployment needs a global load balancer and a source database that replicates to each region (same). And the uids cookie that carries bidder IDs is set on the Prebid Server host's domain, so with a managed host the identity cookie belongs to the host's domain, not yours (Prebid Server cookie sync, accessed 17 October 2026).

Read the full prebid server self-hosting guide: aws, on-prem, managed guide for context, sources and limitations.

Prebid Server. CPU and network bound; needs "a fair amount of memory" to cache stored requests and several GDPR vendor-list versions; can host geo lookup for GDPR scope (Prebid Server hosting). Endpoints: /openrtb2/auction, /openrtb2/amp, /openrtb2/video, /cookie_sync, /setuid, /getuids, /status, /version, /info (Prebid Server overview).

Prebid Cache. Stores VAST and bids for video and AMP; uses "very little CPU or memory" and translates between Prebid's protocol and the backend, which can be Redis, Aerospike, Cassandra or Apache Ignite; cluster size depends on traffic volume, mix and how long objects stay cached (Prebid Server hosting).

Stored requests. Blocks of OpenRTB stored server-side and merged into incoming requests, used for mobile app and AMP and for keeping ad-unit definitions out of tags. PBS-Go supports filesystem (stored_requests.filesystem.enabled: true, files under stored_requests/data/by_id/), Postgres (stored_requests.postgres with a query) and HTTP (stored_requests.http.endpoint), with an in-memory cache (in_memory_cache.ttl_seconds, request_cache_size_bytes, imp_cache_size_bytes) and an HTTP events feed for invalidation (http_events.refresh_rate_seconds) (stored requests, Go, accessed 17 October 2026). A request references a stored imp with imp[].ext.prebid.storedrequest.id; request values win on conflict (same).

The bidder parameter names above follow the Prebid bidder docs for each adapter; the IDs are placeholders (Prebid bidder list).

Read the full prebid server self-hosting guide: aws, on-prem, managed guide for context, sources and limitations.

Sourced prices (US East, on demand, accessed 17 October 2026)

Inputs you supply (illustrative values, not benchmarks)

Read the full prebid server self-hosting guide: aws, on-prem, managed guide for context, sources and limitations.

A buyer receives a bid request with a SupplyChain object. For each node it reads asi (the system's domain) and sid (the seller ID). It fetches https://{asi}/sellers.json and looks up sid to learn the seller's legal name, domain and type. It then fetches https://{site domain}/ads.txt (or the developer domain's /app-ads.txt) and checks that a line exists for that asi and that account ID, with DIRECT or RESELLER matching the seller's type. IAB Tech Lab's implementation guidance adds the 1.1 step: compare sellers.domain with the ads.txt OWNERDOMAIN (owner), MANAGERDOMAIN (manager, optionally per country) or neither (reseller) (IAB Tech Lab, Implementation Guidance, accessed 17 October 2026).

Read the full ads.txt and sellers.json validator: check your files free guide for context, sources and limitations.

Data records (one per line, comma-separated; all fields required except the fourth) (ads.txt 1.1 specification):

Variables (NAME=VALUE lines) (ads.txt 1.1 specification):

File rules (ads.txt 1.1 specification): hosted at /ads.txt on the root domain (public suffix plus one label, derived with the Public Suffix List); subdomain files count only when declared with SUBDOMAIN; Content-Type must be text/plain; # starts a comment to end of line; CR, LF and CRLF accepted; 301, 302 and 307 redirects followed within the root domain, plus exactly one redirect to a third-party domain; a 404 means no declarations; a 401 means the crawler should contact the site; other errors fall back to the last good copy; a file with no sellers should carry a placeholder line such as placeholder.example.com, placeholder, DIRECT, placeholder, because the empty-file convention was deprecated and consumers were told to ignore it after 1 March 2020.

Annotated example

The Google line format is from Google's own guide, which says the file "must be formatted as specified by the IAB Tech Lab in order to be verified" (Google AdSense Help, ads.txt guide, accessed 17 October 2026).

Read the full ads.txt and sellers.json validator: check your files free guide for context, sources and limitations.

Top-level object (sellers.json 1.0 specification):

Seller object (sellers.json 1.0 specification):

File rules (sellers.json 1.0 specification): /sellers.json on the advertising system's root domain; HTTPS preferred; redirects followed within the root domain plus one off-domain redirect; on a 404 or error, consumers use the last good copy; honor Expires, otherwise 7 days.

Annotated example (values follow the IAB sample)

Read the full ads.txt and sellers.json validator: check your files free guide for context, sources and limitations.

Annotated example (OpenRTB 2.5 placement; move schain up one level for 2.6)

Read the full ads.txt and sellers.json validator: check your files free guide for context, sources and limitations.

A validator runs four layers.

Read the full ads.txt and sellers.json validator: check your files free guide for context, sources and limitations.

Did Google have to sell AdX? No. On 2 September 2026 the court rejected the divestiture of AdX, the open-sourcing of DFP's auction logic and a contingent divestiture of the rest of DFP, and accepted the overlapping conduct remedies "as modified by this Court" (PPC Land, 2 September 2026). The opinion says the plaintiffs identified no viable buyer and that comparable migrations took five to eight years (NatLawReview, 18 September 2026).

When does Google have to open AdX to Prebid? The court accepted Google's commitment of 12 to 15 months for the Prebid integrations over the plaintiffs' 18, but the joint filing of 2 October 2026 still shows the plaintiffs asking for 6 months and Google for 12 for the AdX-to-Prebid adapter (Memorandum Opinion, Dkt. 1858, p. 58; PPC Land, 6 October 2026). The clock starts at the Effective Date, 60 days after a judgment that has not yet been entered.

Does the ruling cover video, CTV and in-app ads? No. The liability finding and the remedies concern open-web display. The data-portability remedy is confined to open-web display, with video and in-app excluded, and Digiday lists CTV, in-app and retail media publishers among the groups that gain nothing (PPC Land, 17 September 2026; Digiday, 18 September 2026).

Will the remedies apply in the EU? The judgment is worldwide; the court rejected Google's comity argument (Memorandum Opinion, Dkt. 1858, p. 104). Google has asked for up to 24 months to implement outside the US, which the plaintiffs oppose (AdExchanger, 5 October 2026). The European Commission's own case produced a €2.95 billion fine on 5 September 2025 and is under appeal (PPC Land, 17 September 2026).

Can Google appeal, and does an appeal pause the remedies? Google has said it disagrees with the liability ruling and will appeal once judgment is entered (Reuters via The Star, 17 September 2026). An appeal does not by itself pause the judgment; a stay would. Google's draft of the final judgment tolls the Effective Date during any stay ordered by the district court, the Fourth Circuit or the Supreme Court, which is one of the bracketed disputes (PPC Land, 6 October 2026).

• Google Ad Tech Antitrust Remedies Explained for Publishers: No AdX sale. Google must open AdX bids to Prebid and rival ad servers within 12 to 15 months under a six-year monitor. What changes for publishers, when.
• Prebid Server Self-Hosting Guide: AWS, On-Prem, Managed: How to self-host Prebid Server: Go vs Java, AWS vs on-prem vs managed hosts, bidder adapters, stored requests, cookie sync, a sourced cost worksheet.
• First-Party Data Strategy for Publishers: 2026 Guide: First-Party Data Strategy for Publishers: a practical guide to the definitions, operating decisions, measurement and evidence you need.
• Private Marketplace and PMP Deals: Setup Guide 2026: Private Marketplace and PMP Deals: a practical guide to the definitions, operating decisions, measurement and evidence you need.
• Programmatic Advertising Strategy 2027: Enterprise Playbook: A programmatic advertising strategy should connect the buying model to the outcomes, data permissions and operating capabilities a business actually has.

• Google Ad Manager Alternatives 2026: 19 Ad Servers Compared: 19 ad servers compared for publishers: CTV, display, API and open source, with owner, pricing, header bidding and AdX access after the Google remedies.
• How to Switch Ad Servers Without Losing AdX Demand: A migration playbook for leaving Google Ad Manager: pre- and post-remedies paths, 12 steps, parallel-run and holdout design, risk register, contract terms.
• Header Bidding vs Open Bidding vs Server-Side: 2026 Compared: Header Bidding vs Open Bidding vs Server-Side: a practical guide to the definitions, operating decisions, measurement and evidence you need.

• ads.txt and sellers.json Validator: Check Your Files Free: ads.txt 1.1, app-ads.txt, sellers.json 1.0 and the SupplyChain object: fields, annotated examples, 10 common errors and how a validator checks them.

• Publisher Ad Stack: Case Evidence and Measurement: A publisher yield case should explain which inventory was eligible, how fill was calculated and whether revenue changed alongside delivery.

1. PPC Land, 6 October 2026
2. PPC Land, 17 September 2026
3. NatLawReview, 18 September 2026
4. Memorandum Opinion, Dkt. 1858, p. 74
5. Kevel, updated 30 April 2026
6. Google Help, Open Bidding, accessed 17 October 2026
7. Prebid.org managed services, accessed 17 October 2026
8. PBS-Go versions page, accessed 17 October 2026
9. Prebid Server hosting
10. Prebid Server cookie sync, accessed 17 October 2026
11. Prebid Server overview
12. same
13. Prebid bidder list
14. IAB Tech Lab, Implementation Guidance, accessed 17 October 2026
15. ads.txt 1.1 specification
16. Google AdSense Help, ads.txt guide, accessed 17 October 2026
17. sellers.json 1.0 specification

• October 18, 2026: aligned the search title and heading, expanded the source-linked guide and reviewed its page groups.
• October 17, 2026: assembled this guide from the approved reference pages, retaining their source links and limitations.