When the OpenRTB 2.6-202501 snapshot landed on 27 January 2025, AdCOM gained Content Taxonomy 3.1 (cattax: 9) and the content.gtax / content.genres pair for CTV genre metadata. Product teams read that as “finish the 3.x upgrade.” Operations teams read the IAB Content Taxonomy mappings page as “run the CSV from 1.0 to 2.0 to 2.2.” Both are real. Only one of them versions the integers on the live bid.
OpenRTB does not ship a mapping file. It ships cat arrays and a per-object cattax selector. If your migration stops at the spreadsheet, every downstream hop still assumes Content Category Taxonomy 1.0 wherever cattax is missing. That is the comparison practitioners confuse: offline mapping tables versus the on-wire selector that names which table applies.
Content Taxonomy 1.0: the default your bid still inherits
Taxonomy 1.0 is the flat IAB content list AdCOM still labels cattax: 1. OpenRTB 2.6 text is explicit: when an object omits cattax, receivers assume 1.0 for the cat, pagecat, sectioncat, or blocklist arrays on that same object.
1.0 is deprecated for new labeling, but it is not dead on the wire. It is the silent default. A CMS export that still prints IAB1-6 style strings, or an integration that never set cattax after 2017, validates as JSON and still lands in the 1.0 table at the buyer.
The mapping CSV Content 1.0 → Content 2.0 (November 2023 on the IAB mappings table) is how you translate historical codes into the numeric 2.x ids. It does not set cattax on site, app, or content. Without that integer beside each cat array, the mapped number is read as a 1.0 row, not as the 2.0 row you picked in Excel.
Content Taxonomy 2.2: tiered ids that mapping files normalize
Content Taxonomy 2.2 (cattax: 6) is the last 2.x release most block lists and publisher tools still cite. Tiered paths like IAB8-5 became structured numeric ids in the 2.x spreadsheets. The Content 1.0 → Content 2.2 mapping file is the bridge publishers use when they cannot rewrite every legacy tag overnight.
2.2 is where “we ran the mapping” meets “we did not retag OpenRTB.” Prebid ortb2.site.content.cat often holds 2.2 ids copied from a classifier, while site.cattax stays omitted. JSON Schema sees integers in an array. Brand safety sees 1.0 semantics. Loss reason 209 (category blocked) shows up on inventory that your spreadsheet already marked as safe.
2.x is also not backward compatible with 3.0 in the human sense: IAB deleted and reshaped nodes between generations. A mapping row that says “closest match” does not mean the buyer’s 3.1 contextual model agrees. You need a deliberate cattax bump to 7 or 9, not only new ids in cat.
Content Taxonomy 3.0 and 3.1: same ids on paper, new genre plane on the bid
3.0 (cattax: 7) expanded coverage past roughly 400 categories and broke backward compatibility with 2.x in places IAB documented in the June 2022 release notes. 3.1 (cattax: 9) adds rows such as Thriller and is the taxonomy behind default gtax when genre fields are present.
Category ids mostly carry forward from 3.0 to 3.1, but genre does not live in cat. OpenRTB 2.6-202501 puts genres under content.genres with content.gtax defaulting to 9. You can therefore migrate content.cat to 3.1 codes, omit content.cattax, and still have content.genres: [712] read correctly while content.cat: [483] is parsed under 1.0. Validators that check array types but not cross-field defaults miss that split brain.
Example on one Content object:
"content": { "cat": [483], "genres": [712], "gtax": 9 } With no content.cattax, 483 is a 1.0 category. With gtax: 9, 712 is a 3.1 CTV genre. Same object, two tables, one green CI job.
Mapping CSVs vs cattax: two different contracts
| Side | What it versions | What it does not do |
|---|---|---|
| IAB mapping CSV | Source id → target id per taxonomy release | Set OpenRTB cattax on site, app, content, publisher, producer, or bid |
cattax on each object | Which AdCOM taxonomy list applies to that object’s category arrays | Upgrade ids by itself; wrong id + correct cattax is still wrong |
BidRequest.cattax | Only bcat and acat on the request root | Version site.cat or content.cat (no inheritance) |
Teams treat a finished mapping project as “we are on 3.1.” Buyers treat omitted cattax as “you are still on 1.0 unless you prove otherwise.” The category taxonomies enum is the Rosetta stone between spreadsheet work and wire values 1 through 9.
Per-object selectors exist because nested inventory disagrees: property-level app.cat may stay on 2.2 while episode-level content.cat moves to 3.1. Copying cattax: 9 only onto BidRequest does nothing for content.cat. The OpenRTB category blocking guide walks how bcat, acat, and object-level cattax interact when block lists were authored in a different generation than the seller’s classifier.
For genre-specific fields, read content.gtax beside content.cattax. Defaults differ by design: cattax → 1.0, gtax → 3.1. Migration playbooks that only touch cat leave genre and category on different generations.
The content taxonomy glossary ties the IAB releases to the AdCOM integers buyers expect. When Ad Manager or another exchange path starts populating pagecat on one integration but not on header bidding, you get the hop mismatch in GAM pagecat on ADX versus Prebid ortb2: mapped ids without aligned cattax on both paths.
How you catch it
RTBlint checks the OpenRTB object: cattax values against AdCOM, co-occurrence of cat with the selector on the same object, and the 2.6-202501 rules for gtax and genres. An LLM implementing AdCP, ARTF, or AAMP can emit category integers that look upgraded and still omit every cattax. The RPC or tool call can return OK. These packages are the deterministic check on the bid payload. They are independent of IAB Tech Lab and of AgenticAdvertising.org; they are not official harnesses, and the specs do not require them.
Run rtblint validate against the dated snapshot your exchange publishes before you trust a migration CSV in production.
Where to go next
- Reconcile block lists (
bcat/acat) with theBidRequest.cattaxthat scopes them only. - Set
content.cattaxwhenever you setcontent.catafter a 2.2 or 3.x mapping job. - Log
cattaxandgtaxnext tocatandgenreson loss reason 209 tickets so support stops blaming the buyer’s grudge. - Read field-level docs for
content.cattaxwhen you add per-episode labels on CTV.