IAB Europe's Supply Chain Transparency Map: What 383 Questions Mean for Publishers

Key Points

• IAB Europe released an interactive supply chain transparency guide with 383 questions across 11 stakeholder nodes and 39 relational edges, replacing a static document first published in 2018.
• The guide covers categories including cost, data, GDPR, identity, inventory, fraud, SPO, and sustainability, organized by counterparty relationship, not role.
• Publishers can use this framework to pressure-test their partners on the questions that matter most: masked URLs, wrapper fees, data modelling disclosures, and identity solution architecture.
• A partner who can't answer these questions has a harder time claiming transparency as a selling point.
• Sustainability is now a formal accountability category, not a brand statement.

What Happened

IAB Europe's Programmatic Working Group released an updated version of its supply chain transparency guidance on April 9, 2026. PPC Land's coverage of the announcement details the full scope: 383 questions distributed across 11 node types and 39 directional edges, now navigable through an interactive graph rather than a downloadable PDF.

The node types covered are: Seller, SSP, DSP, Buyer, Data Provider, DMP, Identity Provider, Measurement Provider, Ad Network, Header Bidding Provider, and Curator. Each edge in the graph defines a specific counterparty relationship, and the questions tagged to that edge apply only to that pair. A DSP talking to an SSP sees a different question set than a buyer evaluating a data provider. That's not a trivial distinction.

The upgrade from static document to navigable graph reflects something the industry has known for years: the supply chain isn't a list. It's a network, and accountability questions only make sense in relational context.

See It In Action:

• Adcash: Ad network profile illustrating how ad network counterparties fit into the IAB Europe node structure
• 33Across: SSP and attention measurement platform, directly relevant to the SSP-to-Measurement Provider edge questions on attention methodology
• Yahoo Advertising: Demand-side and supply-side platform profile covering SPO and identity considerations in the framework

Why This Matters for Publishers

Most transparency conversations in programmatic have focused on what's visible in the bid stream: ads.txt, sellers.json, SupplyChain objects. Those signals are real and important. They don't capture everything.

Carbon reporting methodology, wrapper fee structures, data modelling disclosures, SPO logic, identity solution architecture, none of that surfaces in a bid request. The IAB Europe framework creates a documented expectation that counterparties should be able to answer questions in all of these areas, in commercial conversations, before the deal is signed.

That's a meaningful shift. The old document delivered 383 questions to everyone at once. The new graph routes you to the questions relevant to your specific relationships. If you're a publisher evaluating an SSP, you're looking at the Seller-to-SSP and SSP-to-Seller edges, which is a much more manageable accountability checklist than a 383-item master list.

The guide also formalizes attention measurement methodology as a supply chain question. The SSP-to-Measurement Provider edge asks how attention time is calculated, specifically whether the calculation includes eye-tracking proxies, scroll speed, or hardware signals. That level of specificity is appropriate. "We measure attention" isn't a useful answer in 2026.

Essential Background Reading:

• Google AdX: How Google's exchange fits into the programmatic supply chain and what publishers should know about it
• The Trade Desk: Profile of one of the major DSP counterparties publishers encounter in supply chain transparency conversations
• Fraudlogix: How third-party fraud detection integrates into the supply chain and what it checks for
• Display Video 360: Google's DSP and its role as a buyer-side counterparty in the programmatic ecosystem

Where to Focus Your Attention

The full framework is detailed, but a few areas carry particular weight for publishers evaluating or renegotiating partner relationships.

Inventory transparency questions in the SSP-to-Seller edge address the mechanisms that enable or obstruct fraud detection:

• Top-level domain or complete page URL: whether it's passed and whether it's masked or transparent
• Owned and operated vs. exclusive inventory: how the inventory is classified and disclosed
• App ID or bundle ID: whether it's passed for app inventory validation
• Third-party verification access: whether verification vendors can track URLs

Masked URLs block verification vendors from assessing page content. Missing bundle IDs make app inventory impossible to validate against app-ads.txt. These aren't edge cases. They're the core mechanisms by which bad inventory hides.

Header bidding wrapper questions cover an area where opacity has historically benefited intermediaries at publisher expense. The framework asks whether wrapper fees or integration maintenance fees are charged to SSPs, and what the process is for resolving discrepancies between wrapper-recorded wins and SSP-recorded impressions. Discrepancy resolution is unglamorous work, but formalizing the expectation that partners have a defined process for it is a meaningful step.

Identity questions require monthly active addressable user counts specifically for Safari, Firefox, and Edge, the browsers that have restricted or eliminated third-party cookies and that represent a substantial share of European traffic. Scale claims for identity solutions live or die on publisher adoption, and the guide asks for verifiable inventory, not aggregate descriptions.

Here's a summary of the key edge categories and what they surface:

What Publishers Should Do With This

The framework won't enforce itself. It's a structured set of expectations, and whether partners meet them depends on whether publishers ask. A few practical steps:

• Run the graph against your current partner stack: identify which edges apply to your relationships and pull the relevant question sets.
• Prioritize inventory and GDPR edges first: these carry the highest risk exposure if partners aren't meeting baseline expectations.
• Use wrapper fee and discrepancy questions in renewal conversations: vague answers here are a red flag, not a starting point for negotiation.
• Treat sustainability questions as real due diligence: carbon reporting methodology is now part of what measurement partners are expected to provide, per the framework.
• Document partner responses: the value of a structured question set is only realized if you track answers over time and use gaps as decision criteria.

IAB Europe notes that European publishers showed 73% adoption of supply chain transparency standards as of August 2025, based on research examining 2,054 European online news publishers. The question framework published in April 2026 extends that accountability upstream, into commercial conversations, not just technical signals.

Next Steps:

• Adform: Full-stack ad tech platform profile, relevant for publishers auditing DSP and DMP counterparty relationships
• Nexxen: Unified programmatic platform covering SSP, DSP, and data, a multi-edge counterparty worth evaluating against the framework
• MonetizeMore: Publisher monetization platform and how it compares as a managed partner against transparency benchmarks
• PulsePoint: Contextual and programmatic platform profile for publishers evaluating data and inventory counterparties

How We Think About This

We've built our platform around the QPT framework: Quality, Performance, Transparency. That last word isn't a badge. It means publishers working with us should be able to see what's happening with their inventory, understand what's driving their revenue, and ask hard questions about every layer of the stack.

The IAB Europe framework formalizes expectations that should already apply across the industry. When a publisher asks us about wrapper fees, discrepancy resolution, or SPO methodology, we have clear answers. If a partner can't answer the questions in this guide, that's not a gap in the framework. That's information.

Our RAMP platform is built to give publishers the transparency and control this guide is asking for. If you want to see what that looks like in practice, let's talk.