What to Look for When Buying Premium CTV Inventory

1. Content environment, defined

If the answer is 'premium streaming apps' with no list, you are buying an abstraction. Ask for the package contents and check them against your brand-safety requirements.

• Which apps, channels, or content categories are in the package — by name
• Whether the environment is live, VOD, or linear FAST, since ad load and attention differ
• Which categories are excluded, and whether exclusivity is reciprocal
• Whether the seller will commit to the environment in writing, not just describe it

2. How the ad is delivered

• Server-side ad insertion or client-side — this changes what you can observe and how the ad behaves
• Pod position: first position, mid-roll, or last, and how much of your buy sits in each
• Ad load: how many ads run in a pod, which drives attention and frequency
• Device and platform coverage, including whether living-room devices dominate
• Maximum ad duration and whether your creative format is supported

3. Verification and brand safety

Verification support is not universal across streaming supply, and it can differ between a publisher's VOD and FAST inventory. Confirm it per package rather than assuming it carries across your account.

• Whether the inventory supports your verification vendors, and at which level (creative or deal)
• How invalid traffic is filtered, and whether filtering is applied pre-bid or post-bid
• Whether viewability or attention measurement is available for this supply
• What happens if a placement is found to be non-compliant mid-flight

4. Audience, reach, and frequency

• How granular targeting can go: geography, device, daypart, content, household segments
• Whether frequency caps can be enforced, and at what level
• How much this package overlaps with your other deals — overlap is where frequency problems hide
• Whether reach is incremental to what you already buy, or duplicative

5. Commercial terms

• Pricing model: auction floor, fixed rate, or guaranteed volume
• Cancellation terms and required notice
• Substitution policy and makegood handling when delivery slips
• Reporting cadence, metrics, and who provides them
• Creative approval turnaround, because a slow approval can cost you a flight

6. Red flags worth walking away from

• Inventory described only with adjectives, never with contents
• No verification support and no explanation of why
• A seller unwilling to name the environments inside a deal
• Pricing that cannot be explained against a comparable package
• Delivery promises that depend on a single unverified event or launch
• Reporting that arrives after the flight with no interim visibility

How to use this checklist

Run it before you commit, not after. Most of these questions are answered in a single requirements call, and the ones that cannot be answered are the ones that would have become problems in-flight. A seller who can answer them precisely is usually a seller worth working with.