CTV Bidstream Signals: What Buyers Check Before They Bid, and What Publishers Lose Without Them

By TGM Team · Wed Nov 18 2026 · 8 min read

CIMM found 62% of CTV buyers move spend when bidstream signals are missing. Which signals matter, where they get lost and what publishers should fix first.

Introduction

CTV buyers have been saying for years that they need better data from the bidstream. A new study shows what they do when they don't get it. On 12 November 2026, the Coalition for Innovative Media Measurement (CIMM) published Behind the Bidstream, a survey of 50 programmatic CTV buyers co-sponsored by FreeWheel and OpenX. Its headline: 62% of buyers move spend to a different supply path when the signals they require are missing.

For CTV publishers, that is a revenue finding, not a measurement one. The study also suggests where to start fixing it, and it is not where most publishers look first.

What did the CIMM study say?

The survey asked buyers how they respond when their signal requirements are not met. Respondents could choose more than one answer:


The second finding points at the buy side. Only 8% of buyers said their DSP always acts on the signals they require once a campaign is live; 58% said it does so often. A signal can leave the publisher intact and still never influence a bid.

The study has limits worth stating. Fifty buyers is a small sample, and the two sponsors both sell into the supply path the paper examines. CIMM pairs the survey with interviews with 28 executives and bid-log analyses from FreeWheel and OpenX, and says those analyses show associations, not causes.

The supply path comes before the data

The most useful result for publishers is how buyers weigh data against trust. Buyers rated how likely they were to bid in four scenarios, on a scale of one to seven. The share scoring five or higher:


A verified path meant a direct route with a documented supply chain. An unverified one meant several intermediaries, an incomplete chain and an unverified reseller. Rich content data did not make up for a path buyers could not check. Asked to rank eight factors, 48% of buyers put supply-path transparency in their top three, slightly ahead of scale and reach at 46%.

The order of work follows from that. Selling authority comes first; content enrichment second. We set out the authorization basics, including app-ads.txt and inventory partner declarations, in our guide to CTV monetization for publishers.

Which signals do CTV buyers look for?

Without cookies, a CTV bid request is most of what a buyer knows about an impression. CIMM's proposed baseline covers two areas, inventory identity and selling authority. In practice, buyers evaluate five groups of signals:







Content fields are where the market is thinnest. Peer39 estimated in March 2026 that only 40% of CTV bid requests carry usable program-level signals, and 91% of programmatic traders in Gracenote research said missing show-level data limits their CTV campaigns.

Placement signals now cover more than the ad break. IAB Tech Lab finalized how six newer CTV formats are signaled in bid requests in July 2026. For publishers testing pause and other non-break formats, a format that is not signaled correctly cannot be bought programmatically.

How a signal gets into a bid request

Each group of signals starts in a different system, which is why each fails differently. Inventory identity comes from the app itself, its bundle and store URL, while selling authority comes from app-ads.txt on the developer’s domain and the sellers.json files each seller in the chain maintains. Content fields come from the schedule and the EPG. Device and delivery fields come from the player, or from the ad insertion server acting on its behalf.

Placement fields come from ad decisioning, which knows the pod structure.

From there the request travels through an integration to the SSP, the exchange and the DSP, and each receiver reads it by its own rules. OpenRTB defines where a value belongs; it does not check that the value is right. So a field can be present and correctly formatted and still be useless to a buyer, for example when the app bundle does not match the store listing or a livestream flag is missing.

Where signals get lost?

A field can be missing at any of four points, and each needs a different fix.

At the source. Metadata never reaches the ad request because scheduling, EPG and ad decisioning live in separate systems. This is common on FAST channels assembled from many content partners.

In ad insertion. Server-side ad insertion must forward device, IP and user-agent details accurately. When it doesn't, buyers cannot validate the impression, and spoofed SSAI traffic has made them less forgiving: HUMAN's NewsJunkie case in July 2026 involved fake device and app data at close to two billion bid requests a day per seller.

In resale. Each extra hop can normalize, truncate or drop fields, and inventory sold through shared or reseller arrangements is where chains most often break. Our breakdown of how FAST channels make money covers how those distribution deals work.

In the DSP. The field arrives but is not used. That is the 8% problem, and it is the one publishers can least control, which is why CIMM wants platforms to report what they receive and use.

Fragmented markets lose more at every point. In India, Storyboard18 reported this month that platforms, TV makers and FAST services each run their own IDs, ad servers and reporting, and that much premium CTV inventory has moved into programmatic guaranteed and private marketplace deals. Signals that cannot be compared across sellers push buyers toward the few paths they already trust.

Why integration quality sets the ceiling on signal quality

The integration that builds the request sets the ceiling on signal quality. A client-side SDK and a server-side insertion workflow can serve the same app, but each assembles the request its own way, and both need to pass the same app identifiers, device details and content metadata in the same form. If the two paths report different identifiers for one app, a buyer can read one inventory as two.

Metadata is the other half. A schedule or EPG may hold clean program information, but it only helps a buyer once it is mapped to the matching fields in the ad request and kept in step when the schedule changes. On FAST channels assembled from many content partners, that mapping is where gaps tend to appear.

OpenRTB compatibility is therefore the minimum, not the finish line. A practical test is to sample live bid requests from each integration path and compare them field by field: the same app, channel and content should produce the same values.

What publishers should do now?







At TGM, our CTV work sits at two of these points: server-side and client SDK ad integrations, and the Swift playout workflow, where schedules, EPG data and ad slots are managed together. Our CTV monetization page covers both.

FAST is where this matters most, because a single channel can combine content from several partners and distribution paths. Keeping the schedule, the EPG data and the ad slots in one workflow gives the ad request one source of truth for what is playing and where the break falls, instead of three systems that have to be reconciled afterward.

FAQ

Q1. What are bidstream signals in CTV?

They are the data fields sent with each ad opportunity in a programmatic bid request: which app or channel it is, who is selling it, what content is playing, which device is involved and where the ad sits in the break.

Q2. Which signals matter most to CTV buyers?

Selling authority comes first. In CIMM's survey, detailed signals on an unverified supply path drew far less bidding interest than limited signals on a verified one. After that, buyers look for content, device and placement data.

Q3. Why do CTV buyers move spend when signals are missing?

If a buyer cannot confirm what an impression is or who is selling it, the safest response is to buy the same audience through a path they can verify. In CIMM's survey, 62% said they do this.

Q4. What is CIMM's minimum trading baseline?

A proposed voluntary set of information covering inventory identity and selling authority. Each element would have a defined purpose and accepted alternatives, so legitimate inventory is not rejected over a single field.

Q5. Does sending more data raise CTV CPMs?

Not on its own. CIMM's bid-log analyses show associations between signals and pricing rather than proven causes, and its survey suggests reliability and supply-path trust matter more than volume.

Q6. How can publishers check whether their signals reach the DSP?

Sample live bid requests at your SSP, ask DSP partners which fields they receive and act on, and compare rejected and unfilled requests across deals. CIMM proposes formal reconciliation reports for this, which are not yet standard.

Q7. Where do bidstream signals come from?

They come from several systems. The app and seller authorization files supply inventory identity and selling authority, the schedule and EPG supply content details, the player or ad insertion server supplies device data, and ad decisioning supplies placement. An integration packages them into the bid request.