IAB Tech Lab and IAB Europe specifications: what an AdSense publisher needs to know
Key takeaways
- ads.txt 1.1 (final release July 2022) added the OWNERDOMAIN and MANAGERDOMAIN variables; app-ads.txt applies the same idea to apps.
- sellers.json and the SupplyChain object were finalized together on July 31, 2019, so buyers can see who is paid for each impression.
- OpenRTB 2.6 (November 2022) is the bid request protocol most of the market uses; OpenRTB 3.0 and AdCOM exist alongside it.
- IAB Europe launched TCF v2.3 in April 2025 with a transition deadline of 28 February 2026, so v2.2 material is now out of date on that point.
- The Global Privacy Platform (GPP) carries TCF and US state privacy signals in one string; the IAB Tech Lab page calls it both a protocol and a platform.

The IAB Tech Lab and IAB Europe write the technical standards that ad systems, including Google’s, build on: ads.txt, sellers.json, the SupplyChain object, OpenRTB, the Transparency and Consent Framework (TCF) and the Global Privacy Platform (GPP). As an AdSense publisher you implement only ads.txt yourself, but knowing the current versions explains most warnings, consent errors and buyer questions.
Who writes what
- IAB Tech Lab is the technical standards body of the US-based IAB. It publishes ads.txt, app-ads.txt, sellers.json, SupplyChain, OpenRTB, AdCOM, GPP, VAST and others. Most specs live on GitHub under the
InteractiveAdvertisingBureauorganisation. - IAB Europe runs the TCF, the consent framework used in Europe, together with the IAB Tech Lab for the technical parts.
- Google decides how it applies these specs in AdSense. The specs never override Google’s own policies or Help Center instructions.
The map: specs, versions and what they ask of you
| Spec | Current version (as published) | Who implements it | Your action as an AdSense publisher |
|---|---|---|---|
| ads.txt | 1.1, final July 2022 | you | publish and maintain /ads.txt |
| app-ads.txt | 1.0 | app developers | only if you monetize apps |
| sellers.json | 1.0, finalized July 31, 2019 | ad systems | check how your seller ID appears |
| SupplyChain object (schain) | finalized with sellers.json | ad systems | none directly |
| OpenRTB | 2.6 (November 2022); 3.0 (April 2022) | ad systems | none directly |
| TCF | v2.3 (launched April 2025) | CMPs, vendors | use a certified CMP where required |
| GPP | v1.0 (September 2022), CMP API 1.1 | CMPs, vendors | relevant for US state privacy signals |
Versions and dates come from the IAB pages cited in each section below.
ads.txt and app-ads.txt: the one file you own
The IAB Tech Lab ads.txt page lists ads.txt 1.1 as the current version and links the specification on GitHub. The specification’s change log shows the history: version 1.0.3 (final in March 2021) added INVENTORYPARTNERDOMAIN for CTV and similar cases, and version 1.1 (public comment April 2022, final release July 2022) added OWNERDOMAIN and MANAGERDOMAIN.
Points from the spec worth knowing:
- Location:
/ads.txton the root domain and on subdomains as needed, reachable over HTTP and/or HTTPS, with HTTPS preferred when both exist. - Content type: the file should be served as
text/plain; the spec says other content types should be treated as an error. A file served as HTML by a misconfigured host can fail even if the text is right. - Redirects: crawlers follow redirects within the same root domain; only a single redirect to another root domain is allowed.
- Records: lines of the form
<domain>, <account ID>, <DIRECT|RESELLER>, <certification authority ID>, plus variables such ascontact=,subdomain=,OWNERDOMAIN=andMANAGERDOMAIN=.
The spec recommends including OWNERDOMAIN in every file, even when it equals the domain where the file is found, and says that it should match the domain value of your entries in sellers.json files. MANAGERDOMAIN is optional and only for a primary or exclusive monetization partner. For the AdSense line itself see ads.txt syntax, and for the two new variables see OWNERDOMAIN and MANAGERDOMAIN.
app-ads.txt applies the same model to mobile and CTV apps, with the file on the developer website listed in the app store. The same GitHub repository holds its specification.
sellers.json and the SupplyChain object
ads.txt says who may sell your inventory. sellers.json says who those sellers are. The IAB Tech Lab sellers.json page states that sellers.json and the SupplyChain object were finalized on July 31, 2019.
From the sellers.json specification:
- Each ad system publishes
/sellers.jsonon its own domain, served asapplication/json. - Each entry has a
seller_id(the same ID as in ads.txt), aseller_typeofPUBLISHER,INTERMEDIARYorBOTH, and optionallyis_confidential(0 or 1). nameanddomainare required unless the seller is confidential. The domain should be the root domain only, not a URL.- A
seller_idmust map to a single entity that is paid for the inventory.
The SupplyChain object travels inside OpenRTB bid requests and lists every node (each seller ID) the impression passed through. A buyer can then check each node against ads.txt and sellers.json. For how Google’s own sellers.json shows AdSense accounts and the confidentiality setting, read Google’s sellers.json for AdSense.
OpenRTB and AdCOM
OpenRTB is the protocol bid requests and responses use between exchanges, SSPs and DSPs. According to the IAB Tech Lab OpenRTB page, OpenRTB 2.6 was released in November 2022 with support for CTV, and OpenRTB 3.0 is dated April 2022 and works together with AdCOM, the Advertising Common Object Model. The 2.x and 3.0 specs are maintained in separate GitHub repositories (openrtb2.x and openrtb).
You do not implement OpenRTB as an AdSense publisher. It matters in two cases: when you read about bid request fields such as site.domain, publisher.id or schain, and when you evaluate header bidding with Prebid.js, whose server-side counterpart, Prebid Server, exposes an /openrtb2/auction endpoint.
TCF: consent in Europe
The IAB Europe TCF page states that TCF v2.3 was launched in April 2025, with 28 February 2026 as the deadline for the transition, and that v2.2 had been released in May 2023. Many guides, including the topic plan of this site, still refer to v2.2 for publishers, so check which version an article describes.
What TCF does, in one paragraph: a consent management platform (CMP) shows the consent message, records the visitor’s choices about purposes and vendors, and encodes them in a TC string that ad tags read. For ads served to users in the EEA, the UK and Switzerland, Google has its own requirement to use a Google-certified CMP integrated with the TCF; see the certified CMP requirement and TCF for publishers. The version upgrade itself is handled by the CMP vendor.
GPP: one string for many privacy regimes
The IAB Tech Lab GPP page describes a single container for privacy signals, with sections for TCF EU, TCF Canada, the US National (MSPA) section and individual US states. Version 1.0 dates from September 28, 2022, the CMP API 1.1 from June 2023, and implementation guidelines from February 2025; the page was updated in August 2026. A naming oddity: the page title says “Global Privacy Protocol” while the project is widely known as the “Global Privacy Platform”, the name used by its GitHub repository.
For an AdSense site with US traffic, GPP is how US state opt-out signals can reach ad tags. See US state privacy laws and AdSense for how Google handles them.
Other specs you may run into
The IAB Tech Lab standards list also includes:
- VAST, the video ad serving template, relevant if you run video ads.
- OM SDK (Open Measurement), used by measurement and verification vendors.
- ads.cert, cryptographic signing of bid requests.
- Curated Audiences (formerly SDA), a taxonomy for audience segments.
- Deals API, finalized February 6, 2026, for passing deal information between buyers and sellers.
None requires action from a typical AdSense publisher.
How to keep up
- Watch the GitHub repositories (Supply-Chain-Validation, openrtb2.x, the TCF and GPP repositories) for releases. As far as we found, none of them has a licence file, so the reuse terms of the text are not stated there.
- Check the date on every guide that cites a version, including this one.
- Treat Google’s documentation as authoritative for how AdSense applies a spec. The IAB defines formats; Google decides what its systems accept.
Common mistakes
- Reading an old spec version. ads.txt 1.0 guides omit OWNERDOMAIN and MANAGERDOMAIN; TCF v2.2 guides predate v2.3.
- Serving ads.txt with the wrong content type. The spec expects
text/plain. - Confusing ads.txt with sellers.json. You publish the first; ad systems publish the second.
- Assuming a spec is a Google rule. Google may apply a stricter or narrower version.
Frequently asked questions
Do I need to read the IAB specifications to use AdSense?
Not in full. For AdSense, Google tells you which ads.txt line to publish and its certified CMPs handle TCF strings. Knowing the specs helps when something breaks: an ads.txt warning, a consent error, a buyer asking about your supply path, or a second ad partner joining. Read the ads.txt section on file format and access first, since that is the file you maintain yourself.
Is TCF v2.2 or v2.3 current?
IAB Europe's TCF page states that v2.3 was launched in April 2025, with 28 February 2026 as the deadline for the transition, and that v2.2 had been released in May 2023. In November 2026 v2.3 is therefore the current version. Your CMP vendor implements the change; your job is to keep the CMP updated and certified.
What is the difference between ads.txt and sellers.json?
ads.txt is published by you, on your domain, and lists the ad systems and account IDs authorized to sell your inventory. sellers.json is published by each ad system, on its own domain, and lists the entities behind its seller IDs, with a seller_type of PUBLISHER, INTERMEDIARY or BOTH. Buyers match the two to check that the seller in a bid request is authorized and identifiable.
Are the IAB specifications open source?
They are free to read and are published on GitHub, but the main repositories we checked (Supply-Chain-Validation, openrtb2.x, the TCF and GPP repositories) have no licence file, so reuse terms are not stated there. Implementing a spec is generally expected; copying large parts of the text into your own product is a different question to clarify with the IAB.
Sources
- ads.txt · IAB Tech Lab
- ads.txt Specification Version 1.1 · IAB Tech Lab on GitHub
- sellers.json Specification · IAB Tech Lab on GitHub
- OpenRTB · IAB Tech Lab
- Global Privacy Platform · IAB Tech Lab
- Transparency & Consent Framework · IAB Europe
Related guides
- ads.txt syntax for AdSense, line by line: pub ID, DIRECT, TAG ID, comments and variables
The AdSense ads.txt line field by field: google.com, your pub ID, DIRECT, f08c47fec0942fa0, plus comments, variables and the formatting errors that break parsing.
- Google's sellers.json for AdSense publishers: seller information visibility and what buyers see
What Google's sellers.json says about your AdSense account, how the Seller information visibility setting works, and how to find your own entry in the file.
- OWNERDOMAIN and MANAGERDOMAIN in ads.txt 1.1: syntax, when to add them, and sellers.json consistency
What the OWNERDOMAIN and MANAGERDOMAIN variables in ads.txt 1.1 mean, the exact syntax, when an AdSense publisher should add them, and how they tie to sellers.json.
- IAB TCF v2.3 for publishers: what Google requires, what changed from v2.2, and v2.4
TCF v2.3 is mandatory for TC strings created since March 1, 2026. What changed from v2.2, Google's dates, the purposes AdSense needs, and the v2.4 update.
- US state privacy laws and AdSense: opt-outs, restricted data processing and the GPP
What US state privacy laws like the CCPA mean for AdSense: opt-out of sale or sharing, restricted data processing, Google's US states message, GPP and GPC.