ADWEAVE INSIGHTS / PUBLISHER MONETIZATION
Know Who Sells Your Inventory: A Publisher Transparency Checklist
Connect seller authorization, seller identity and the path to market before expanding demand.
By Adweave4 min read
THE ADWEAVE FIELD GUIDE 04
Adding a demand partner creates another relationship to understand. Before expanding monetization, publishers and buyers should be able to explain who is authorized to sell the inventory and how the declared selling relationships fit together.
Separate the three transparency questions
IAB Tech Lab’s standards address related questions. Ads.txt and app-ads.txt let publishers declare authorized sellers. Sellers.json provides information about seller entities and intermediaries. The OpenRTB SupplyChain object describes parties involved in selling or reselling a bid request.
Authorization, identity and selling path are different checks. Treating one file as a complete picture can leave important relationships unexplained.
Start with the partner’s account details
Ask each partner for the advertising-system domain, seller account identifier and explanation of its role. Establish which property and agreement the account relates to.
Compare those details with the relevant publisher declaration. For app inventory, confirm the applicable app-ads.txt setup with the responsible implementation team.
Do not guess account identifiers or add a proposed seller simply because it appears in a template. Confirm the commercial relationship and have the responsible team review the declaration before any production change.
Reconcile seller identity and the selling path
Ask your partner to explain how the account is represented in its sellers.json and how the selling relationships appear in the SupplyChain object where applicable. Record discrepancies and the person responsible for resolving them.
These mechanisms help buyers understand the parties involved. They do not guarantee campaign performance, remove every quality risk or replace a broader assessment of the inventory.
Keep an operational record of each relationship
A working partner register can include the property, commercial owner, technical contact, supplied account details, review date and unresolved questions.
For an illustrative app publisher adding a partner, the checklist might record who approved the relationship, who checks the declaration and who confirms that the reported inventory matches the intended property.
Keep proposed, approved and active relationships distinguishable. Review records when partners, account arrangements or integrations change. An outdated entry deserves investigation rather than an automatic assumption about its cause.
Review business quality alongside transparency
Continue to assess placements, ad behaviour, reporting and the effect on the app experience. Establish who will investigate discrepancies, what reporting is available and which operational limits matter to the publisher.
Ask partners to explain fees, reporting definitions and payment arrangements under the actual agreement. Transparency standards alone cannot answer those commercial questions.
Before expanding, assemble a brief that covers the intended inventory, partner roles, implementation responsibilities and the evidence available for review. Resolve open questions with the relevant partner and technical team.
Sources and further reading
Original Adweave planning guidance. Technical context is informed by the following primary sources, reviewed November 7, 2026. Illustrative examples are not client case studies.