Channel ad inventory: earning buyers’ trust

Can a buyer trace your channel ad inventory from the programme you promised to the seller they paid and the delivery you reported? That question gets harder when a channel appears inside several streaming apps, each with its own advertising arrangements.

Commercial teams can make the buying decision easier by preparing a small evidence pack before a campaign starts. It should explain what is being sold, who can sell it and how delivery will be counted. An impressive audience presentation leaves plenty of room for awkward invoice conversations when those details are missing.

Describe the channel ad inventory precisely

Give buyers a schedule, channel description and list of distribution destinations. Include territory, language, programme categories, content classifications, dayparts, advertising formats and any contractual exclusions. Explain how you handle sensitive programming and whether a buyer can exclude particular contexts.

Separate the streaming app from the channel inside it. An app identifier may describe a platform carrying hundreds of channels. A buyer evaluating a documentary channel needs a way to recognise that particular service in delivery records.

OpenRTB 2.6 provides distinct app, content, network and channel objects. Ask your partners which fields they actually populate and which survive into buyer reporting. A field’s presence in the specification does not establish support throughout a commercial integration.

Keep rights evidence alongside this description. Record the territories and distribution arrangements approved for each feed, with an owner responsible for changes. Our FAST distribution deal guide covers the wider commercial terms; this evidence helps a buyer understand the inventory within them.

Make the selling path inspectable

Match authorization, identity and transaction records

IAB Tech Lab’s ads.txt and app-ads.txt framework lets publishers declare authorized selling accounts. For inventory inside a connected-TV app, establish the relevant app owner, developer website and distributor arrangements. Publishing a file on the broadcaster’s corporate website alone may leave that relationship unresolved.

The account declaration, seller identity and transaction path should agree. Sellers.json and the SupplyChain object support those cross-checks: sellers.json describes seller accounts, while SupplyChain represents participants in the direct payment flow. Confidential seller entries and incomplete chains need an explanation.

Publisher authorizationads.txt / app-ads.txt: selling system and authorized account

Seller identitysellers.json: the entity represented by that seller account

Transaction pathSupplyChain: declared participants in the payment flow

Illustrative verification sequence, not the video delivery path. Cross-check system domains and account identifiers. Matching declarations still need corroboration.

These records establish specific selling relationships. They do not certify programme quality, human attention or a buyer’s suitability requirements. DIRECT describes control of a selling account; it should never be presented as a blanket promise that the transaction has no intermediaries or fees.

Agree the measurement contract

Define the billable event before agreeing a volume. An ad request, a qualified impression, a completed ad and a person reached describe different things. Put the counting method, exclusions, reporting timezone and completion-rate denominator into the campaign agreement.

Server-side ad insertion (SSAI) needs particular care. A server can insert an advertisement and generate tracking without proving that someone watched it. MRC’s OTT/CTV and SSAI guidance addresses playback requirements and measurement limitations. Validated server-to-server signals can contribute to compliant measurement; ask how the actual player and device integrations meet the requirements.

Ask what the reporting cannot establish, too. MRC’s 2024 invalid-traffic update distinguishes unknown traffic where signals are insufficient. A low reported invalid-traffic rate needs context about measurement coverage and decision rates. Respect privacy restrictions when collecting evidence.

Reconcile a pilot before promising scale

Consider a hypothetical pilot with the following agreed reporting definitions. All counts refer to the same campaign period and correlated event cohort. The numbers are illustrative, with no claim about typical performance or Evrideo customer results.

1. 01
   900,000 measured starts

   The starting report, before the agreed traffic filtering.

2. 02
   30,000 starts excluded

   The measurement partner identifies invalid traffic in this example.

3. 03
   870,000 valid starts

   The agreed denominator after filtering. Any unknown traffic would need separate disclosure.

4. 04
   780,000 valid completions

   Completions from those retained starts: 780,000 / 870,000 = 89.7%.

This example assumes event correlation and filtering are resolved. A completion rate alone establishes neither unique audience reach nor continuous human attention. Billable impressions still require the agreed counting criteria.

Now compare the publisher, ad-server and buyer reports. Investigate differences in filtering, duplicate handling, late events and reporting windows. Give each unresolved discrepancy an owner and a resolution date. Avoid silently changing the denominator until the reports agree.

Broad-audience spot sales and addressable campaigns can coexist, including premium scheduled inventory alongside programmatic opportunities. Combined reach claims need compatible populations, exposure definitions and deduplication. MRC’s cross-media video standard distinguishes reach, impressions and ratings. Adding a programme rating to digital impression counts produces no meaningful audience total.

Give the buyer something they can verify

Prepare a dated inventory description, reconciled selling-path sample and measurement schedule. Add a redacted pilot report with exclusions, unknowns and discrepancies visible. Include playback checks and an incident contact so the buyer knows who handles wrong content, missing ads or interrupted delivery.

Update this pack when a distributor, monetization partner or measurement integration changes. Check any accreditation claim against the specific service, metric and environment it covers. A familiar company logo cannot answer that question.

Trust in channel ad inventory grows when commercial promises can be checked against operational records. Start with one destination and one pilot campaign, resolve the gaps, then extend the same discipline across your distribution agreements. Explore Evrideo Broadcast for the scheduling and playout side of that operation.