How to Buy CTV Inventory Through PMP Deals

What a PMP actually is

In programmatic terms, a PMP is a curated auction: the seller assembles an inventory package, invites a defined list of buyers, and sets a price floor. You still bid, but only against the invited group, and the inventory is narrower and usually higher quality than the open exchange.

Two variants sit alongside it and are often confused with it. A preferred deal gives a buyer fixed pricing and priority for a set window without a volume commitment. A programmatic guaranteed deal pairs fixed pricing with a guaranteed volume commitment on both sides. All three are activated the same way — through a deal ID in your DSP — which is why the mechanics below apply to each of them.

What to have ready before you start

Sellers match campaigns against their supply relationships, so the more precise this list is, the faster you get to a relevant opportunity. Vague briefs tend to produce broad, unhelpful inventory proposals.

• Target audience and the geography you need, including any regions to exclude
• Device and platform preferences, such as living-room streaming devices versus smart-TV apps
• Content categories you want and categories you will not run against
• Budget range and flight dates, including how flexible the flight is
• Your DSP account identifier, so a seller can grant your account access to a deal
• Creative specifications and turnaround time, including ad duration and VAST requirements
• Measurement requirements, such as which verification vendors must be in the tag

How deal IDs work

A deal ID is the handshake between seller and buyer. The seller creates the deal inside an ad exchange or supply platform, attaches the inventory package, pricing rule, and priority to it, and adds the buyer's DSP or account ID to the deal's allowed list. The buyer then enters that deal ID in the campaign.

Once the deal ID is attached, impressions can only come from the inventory the seller put into the deal. That is the core value: you are not hoping the algorithm finds good supply, you are buying a package someone assembled and is accountable for.

Activation, step by step

1. 1.Confirm deal access

   Ask the seller to add your DSP account identifier to the deal and verify the deal is visible in your platform before you build anything.

2. 2.Build the campaign

   Set the inventory type to Connected TV, set flight dates, and attach the deal ID at campaign or line-item level depending on your platform.

3. 3.Apply targeting inside the deal's scope

   Narrowing is fine — geography, device, daypart, audience. Just remember you cannot widen beyond what the deal contains.

4. 4.Upload creative that matches specs

   Provide VAST-hosted creative at the required duration, plus any tracking pixels the seller requires. Confirm acceptance before scheduling launch.

5. 5.Verify and preview

   Confirm the verification tags are attached and preview the creative on a test device or preview link before scaling spend.

6. 6.Launch and monitor pacing

   Watch delivery against the flight in the first 24-48 hours. If a deal underdelivers, you need time to adjust targeting or add a second deal.

What to confirm before you commit

• Which apps, channels, or content categories are actually inside the deal
• Whether pricing is a floor in an auction or a fixed rate, and what the expected clearing price looks like
• Whether the deal carries priority over open demand, and how much
• Any category exclusivity, and whether it cuts both ways
• Cancellation terms, substitution policy, and makegood handling if the deal underdelivers
• Reporting cadence and the metrics you will receive

Where buyers get stuck

The most frequent failure is a deal described only as 'premium inventory'. If nobody can tell you what the package contains, you cannot plan against it.

The second is creative turnaround: a deal that takes ten days to approve creative can miss a flight entirely. The third is targeting that is narrower than the deal's own scope, which starves delivery and looks like a bad deal when it is a configuration problem.