Industry

IAB Standards Every Publisher Should Know

The IAB Tech Lab maintains dozens of standards. Publishers only need to care about a handful. Here are the ones that directly affect your programmatic revenue and how to stay compliant.

B
BeamFlow Team
BeamFlow Team
February 9, 2026
7 min read
IAB Standards Every Publisher Should Know

Key Takeaways

  • Publishers don't need to master every IAB standard, but they need to implement the ones DSPs enforce. The standards that directly affect bidding behavior are the ones that matter most for revenue.
  • ads.txt and sellers.json are the non-negotiable foundation. Without these, your inventory can't be verified and premium demand can't reach you.
  • OpenRTB defines how your inventory is sold. Understanding the basics of OpenRTB helps you understand what information buyers see when they evaluate your impressions.
  • VAST is critical for publishers with video inventory. Non-compliant video setups cost you demand from programmatic video buyers.
  • Privacy standards (TCF, GPP) affect whether buyers can use targeting data on your inventory. Non-compliant publishers lose access to targeted campaigns, which typically have the highest CPMs.

---

IAB Standards Every Publisher Should Know

The IAB Tech Lab maintains dozens of technical standards, specifications, and guidelines for the digital advertising industry.

For publishers, keeping up with all of them is neither practical nor necessary. What matters is knowing which standards directly affect how DSPs evaluate and price your inventory.

This guide covers the standards that have measurable revenue impact for publishers. If a DSP enforces it, you need to know it. If it only matters for the buy side or for ad tech infrastructure, you can skip it.

Supply Chain Transparency Standards

These are the standards with the most direct and measurable impact on publisher CPMs.

ads.txt / app-ads.txt

What it is: A text file you host on your domain listing every SSP, exchange, and reseller authorized to sell your inventory.

Why it matters: DSPs check ads.txt on virtually every bid request. Unauthorized supply paths are rejected or heavily discounted. This is the single most impactful standard for publishers.

What to do: Keep an accurate ads.txt file at your root domain. Include every SSP you work with. Use the correct account IDs and relationship types (DIRECT/RESELLER). Update it whenever you add or remove SSP partnerships. For app publishers, keep app-ads.txt at the developer website URL registered in your app store listing.

sellers.json

What it is: A JSON file SSPs host listing the identity of every seller on their platform. Each entry maps a seller_id to a business name, domain, and seller type.

Why it matters: DSPs cross-reference your ads.txt entries against sellers.json to verify your identity. Missing or confidential entries mean DSPs can't confirm who you are, which cuts bid confidence and CPMs.

What to do: You can't edit sellers.json (SSPs maintain it), but you can and should monitor it. Verify your entries are present, non-confidential, and accurate across every SSP. Use BeamFlow's scanner to automate this.

SupplyChain Object (schain)

What it is: A structured object embedded in OpenRTB bid requests that documents every entity in the supply path from publisher to buyer.

Why it matters: DSPs use schain to verify the entire path, not just the first hop. Complete chains get higher trust scores. Incomplete chains get discounted.

What to do: You don't directly implement schain (SSPs handle it). But you should choose SSP partners that fully support schain and pass along complete chains. Fewer intermediaries in your supply path means shorter, more verifiable chains.

Transaction Standards

OpenRTB (Open Real-Time Bidding)

What it is: The protocol that defines how programmatic auctions work. It specifies the format of bid requests, bid responses, and the data exchanged between SSPs and DSPs.

Why it matters: OpenRTB determines what information buyers see about your inventory. It defines the fields for site information, content classification, user data, device data, and supply chain objects. The richer and more accurate this data is, the better buyers can evaluate your inventory.

What to do: You don't implement OpenRTB directly (your SSPs handle the protocol). But understanding the basics helps you work more effectively with SSPs. For example, knowing that OpenRTB includes content category fields explains why properly categorizing your content matters for targeting and brand safety.

Recent OpenRTB updates include expanded CTV ad format support, supply chain integrity tools, and enhanced content classification fields.

VAST (Video Ad Serving Template)

What it is: The standard for serving and tracking digital video ads. VAST defines how video ad creatives are delivered, played, and measured.

Why it matters: If you serve video inventory, buyers expect VAST compliance. Non-compliant video implementations cause rendering failures, measurement gaps, and tracking errors. DSPs push down publishers with high video error rates.

What to do: Make sure your video player supports the current VAST version (4.2+). Test video ad delivery regularly. Monitor VAST error rates through your SSP dashboards. Common VAST errors include timeout failures, wrapper chain issues, and unsupported media types.

OMSDK (Open Measurement SDK)

What it is: An SDK that enables standardized viewability and verification measurement across different ad formats and environments.

Why it matters: Buyers use OMSDK to verify that ads are actually viewable. Publishers who integrate OMSDK provide standardized measurement signals that increase buyer confidence. Without OMSDK, viewability measurement relies on less standardized methods.

What to do: Most major SSPs include OMSDK in their SDKs. Verify that your implementation supports OMSDK and that viewability signals are being transmitted correctly. This is particularly important for mobile app publishers.

Content and Classification Standards

IAB Content Taxonomy

What it is: A standardized classification system for web content. The taxonomy defines categories (news, sports, finance, tech, etc.) that buyers use for targeting and brand safety.

Why it matters: DSPs use content taxonomy to match advertiser campaigns to appropriate publisher content. Properly classified content receives more relevant (and often higher-value) demand. Misclassified or unclassified content gets generic campaigns at lower CPMs.

What to do: Make sure your SSPs are categorizing your content correctly using the IAB content taxonomy. Some SSPs auto-classify using page content analysis. Others rely on publisher-provided categories. If your content is consistently miscategorized, work with your SSP to correct it.

IAB Audience Taxonomy

What it is: A standardized classification for audience segments. Publishers can define audiences based on content consumption patterns and make those segments available to buyers.

Why it matters: Curated audience segments command higher CPMs than undifferentiated impressions. The IAB audience taxonomy provides a standardized way to describe these segments so buyers can evaluate and bid on them.

What to do: If you have first-party audience data, work with your SSPs to create audience segments using the standard taxonomy. This is particularly valuable as third-party cookies phase out and first-party data becomes more important for targeting.

Privacy and Consent Standards

TCF (Transparency & Consent Framework)

What it is: A framework for collecting and communicating user consent for data processing in digital advertising. Particularly relevant for GDPR compliance in Europe.

Why it matters: Without proper consent signals, buyers can't use targeting data on your inventory. Targeted campaigns have way higher CPMs than untargeted ones. Non-compliant publishers lose access to the highest-value demand.

What to do: Implement a TCF-compliant Consent Management Platform (CMP) if you serve users in regions with consent requirements. Make sure consent signals are properly passed through to your SSPs and into bid requests.

GPP (Global Privacy Platform)

What it is: A unified framework for communicating privacy signals across different regulatory environments (GDPR, CCPA, and other privacy laws). GPP consolidates multiple privacy signals into a single mechanism.

Why it matters: As privacy regulations multiply globally, GPP provides a standardized way to handle consent and privacy signals. Buyers increasingly expect GPP compliance for inventory in regulated markets.

What to do: Make sure your CMP supports GPP. As of 2025, GPP is in active live testing with expanding adoption. Publishers who implement it early are better positioned as buyer requirements formalize.

Certification and Compliance

TAG Certification

What it is: The Trustworthy Accountability Group (TAG) runs anti-fraud certification programs. TAG-certified entities meet specific standards for inventory quality, brand safety, and transparency.

Why it matters: Many large advertisers and agencies require or prefer TAG-certified supply partners. TAG-IDs in ads.txt entries signal certification status to buyers.

What to do: While TAG certification is primarily for intermediaries (SSPs, exchanges), you benefit by working with TAG-certified partners. Make sure your SSPs' TAG-IDs are included in your ads.txt entries.

Which Standards Matter Most by Publisher Type

| Publisher Type | Critical Standards | Important Standards |

|---------------|-------------------|---------------------|

| Web display | ads.txt, sellers.json | Content taxonomy, TCF/GPP |

| Web video | ads.txt, sellers.json, VAST | OMSDK, content taxonomy |

| Mobile app | app-ads.txt, sellers.json, OMSDK | VAST (if video), TCF/GPP |

| CTV/OTT | app-ads.txt, sellers.json, VAST | OMSDK, content taxonomy |

Frequently Asked Questions

Do I need to implement all these standards?

Not all of them. ads.txt/app-ads.txt and sellers.json monitoring are non-negotiable for every publisher. The other standards depend on your inventory type (video needs VAST), your audience location (EU needs TCF), and your business model (audience segments need the audience taxonomy).

How do I know if I'm compliant?

For ads.txt, run a cross-verification against sellers.json using BeamFlow's scanner. For video standards, check VAST error rates in your SSP dashboards. For privacy, verify through your CMP that consent signals are being properly transmitted.

What happens if I ignore these standards?

DSPs that enforce the standard will cut or eliminate bids on your inventory. The financial impact depends on which standard you're missing and how many DSPs enforce it. ads.txt non-compliance has the broadest and most immediate revenue impact.

Ready to optimize your ads.txt?

Check your domain's supply chain health instantly, free.

Check Your Domain Free