CTV DSP Buying Guide: How to Configure, Target, and Measure Programmatic TV Campaigns

A demand-side platform in CTV requires VAST 4.2 compliance, household-level frequency capping, deal ID handling, and CTV-specific OpenRTB field configuration. The complete guide to DSP setup and optimization for programmatic connected TV buying.

MS
Manmohan Singh

Head of CTV Product, LtvAdx

Published 14 Jun 2026·Updated 15 Jul 2026·14 min read
CTV DSP Buying Guide: How to Configure, Target, and Measure Programmatic TV Campaigns

A demand-side platform (DSP) is the software layer that executes programmatic CTV advertising on behalf of a buyer. When a brand or agency wants to run campaigns across connected TV inventory — FAST channels, AVOD platforms, streaming apps on Roku, Fire TV, and smart TVs — the DSP is the system that translates campaign objectives into real-time bids, manages audience targeting and frequency controls, traffics creative, and reports on delivery and outcomes. Understanding how DSPs work in the CTV context, how they connect to supply, and what configuration decisions determine campaign performance is essential knowledge for every media buyer and ad operations professional working in advanced TV. This guide covers the full picture — from DSP architecture through deal configuration, audience targeting, and measurement setup — with the LtvAdx advertiser platform as the operational reference for programmatic CTV buyers.

What a DSP does in CTV programmatic

A DSP receives bid requests from supply-side platforms (SSPs) and exchanges via OpenRTB, evaluates each request against active campaign targeting criteria, calculates a bid price, and responds within the configured timeout window — typically 100–150ms for CTV. The DSP simultaneously manages budget pacing (spending at the right rate across the flight), frequency capping (limiting how often specific households see a creative), audience matching (applying segment targeting to each bid request), and creative selection (choosing which ad variant to serve given the audience and frequency context).

In CTV, the DSP operates against a more complex bid request than in standard display. A CTV bid request carries content metadata — app bundle, content genre, content rating, series title — alongside device signals (platform advertising ID, device type, IP address) and pod structure information (slot position, pod duration, slot duration). The DSP uses all of these signals simultaneously to decide whether to bid, at what price, and with which creative. A DSP not configured to read and act on CTV-specific OpenRTB fields is operating at a significant disadvantage relative to buyers who have mapped their targeting logic to the full signal set.

The connection between the DSP and CTV supply runs through SSPs and exchanges. LtvAdx operates as the SSP layer: it aggregates publisher inventory, runs the supply-side auction, and routes winning bids to the SSAI stitcher for manifest delivery. DSPs connect to LtvAdx via OpenRTB endpoint registration and deal ID activation for private marketplace and programmatic guaranteed inventory access.

CTV DSP architecture: what to look for

Not all DSPs handle CTV with equal depth. Several capabilities distinguish purpose-built CTV DSPs from display DSPs that have added CTV as a channel extension. Household-level frequency capping is the most critical differentiator: a DSP that caps at the device level rather than the household level will overexpose households with multiple streaming devices, generating the ad fatigue complaints that damage brand perception in CTV. The CTV frequency capping guide explains why device-level caps fail and what household identity resolution requires.

VAST 4.2 compliance is the second critical capability. A DSP that generates VAST 2.0 or 3.0 creative responses cannot utilize the verification node support, improved tracking definitions, or mezzanine file references that VAST 4.2 provides. Publishers on the LtvAdx exchange increasingly require VAST 4.2 for premium inventory, particularly for live sports and direct-sold integrations. Confirm your DSP can generate VAST 4.2 responses before running CTV campaigns on premium supply.

Deal ID handling distinguishes programmatic sophistication. A CTV DSP must correctly receive PMP and programmatic guaranteed deal IDs from publishers, apply them in bid responses with the correct OpenRTB deal object structure, and maintain deal-specific frequency and pacing separate from open auction campaigns. DSPs that conflate deal inventory with open auction or that misformat deal objects produce delivery failures that manifest as mysteriously low fill rates on PMP campaigns — a symptom that is difficult to diagnose without bid-level logging.

Campaign setup: line item structure for CTV

CTV campaign line items require more configuration than standard display because the targeting, creative, and measurement variables specific to television are not populated by default in most DSP UIs. The line item setup checklist for a CTV campaign covers: supply type (CTV only, not OTT which includes mobile), device type filter (connected TV, excluding phone and tablet), environment (app, not web), video format (in-stream, not out-stream or in-article), ad duration (matching your creative length to available slot durations on target inventory), and content category targeting (genre restrictions or allowlists by IAB category).

Audience targeting in CTV line items should specify both the target segment and the fallback behavior when a device does not match the segment. A line item targeting in-market auto shoppers that stops bidding entirely when no segment match is found will chronically underpace because segment match rates on CTV inventory typically run 40–65% — below the 80%+ rates DSPs see on authenticated web environments. Configure a contextual or demographic fallback targeting tier so the line item continues pacing against contextually relevant inventory when behavioral segments are absent. The household identity guide covers match rate expectations by identity method and why match rates vary.

Creative trafficking in CTV DSPs requires the VAST tag or media file URL for each creative, the declared duration (must match the actual creative length exactly — mismatches cause slot rejection), and tracking pixel URLs that are HTTPS and reachable from server environments without JavaScript execution requirements. Review the CTV creative best practices guide for the full technical specification before trafficking to avoid rejection-driven delivery failures.

Deal types: open auction, PMP, and programmatic guaranteed

CTV programmatic buying operates across three deal structures, and the DSP configuration for each is distinct. Open auction buying — the default programmatic mode — requires no pre-negotiation. The DSP submits bids against all available inventory matching campaign targeting at whatever CPM the algorithm determines. Open auction CPMs for CTV typically range $15–$35 depending on audience, daypart, and content genre. Open auction provides scale and efficiency but no delivery guarantees and no priority access to premium inventory.

Private marketplace deals give the DSP priority access to specific publisher inventory at negotiated floor CPMs. The publisher generates a deal ID in the LtvAdx system, shares it with the buyer, and the buyer activates it in their DSP line item targeting. When a bid request from eligible inventory arrives, the DSP identifies the deal ID, bids at or above the floor, and the supply side prioritizes the deal-linked bid over open auction competition. PMP deals improve delivery predictability without committing to guaranteed volume. They are the preferred mechanism for accessing premium FAST channel inventory or genre-specific buys where open auction competition is intense.

Programmatic guaranteed deals commit to fixed CPM and volume. The DSP activates the deal ID, the publisher reserves inventory, and delivery executes automatically against the agreed parameters. PG deals require pre-campaign creative approval and pacing alignment between buyer and seller systems. The DSP must track delivery against the PG commitment and alert on underdelivery before the flight ends — not after. Configure PG monitoring alerts in your DSP at 80% of scheduled delivery by mid-flight, not at campaign end.

Audience segments and targeting precision

CTV audience targeting in DSPs draws from multiple data sources with different quality tiers. First-party advertiser CRM data — hashed email or phone matched against the identity graph — is the highest quality signal: deterministic, owned by the advertiser, and actionable for both targeting and suppression. Upload CRM data as audience segments in your DSP and match against the LtvAdx HouseholdID graph to create CTV-targetable household lists from existing customer data.

Second-party data from publisher-authenticated audiences — streaming services that have users registered with verified emails — carries near-first-party accuracy. Access this through PMP deals with identity-enriched publishers rather than through open auction, where the identity signal is often stripped from the bid request for privacy reasons. Third-party audience segments from data providers (income, purchase intent, demographic overlays) are the most widely available but least accurate targeting layer in CTV due to probabilistic household resolution and segment freshness lag. Use third-party segments as a reach extension mechanism, not as a precision targeting foundation.

ACR-based audience targeting — segments derived from smart TV viewing history — provides a unique CTV-native signal: households that have recently seen specific competitors' advertising on linear TV, or households with verified sports viewership patterns, or audiences who watched specific programming genres. ACR segments are available through data partnerships in major DSPs and are particularly valuable for competitive conquesting and reach extension against linear TV audiences who are measurably available on streaming.

Bid strategy and floor pricing dynamics

CTV bid strategy in DSPs operates in a second-price auction environment: the winning bidder pays the second-highest bid plus a clearing increment, not their full bid price. This means bidding above the true value of the impression does not increase cost significantly in most cases, but bidding below it consistently loses to competitors who have more accurately priced the inventory. Dynamic CPM bidding — where the DSP adjusts bid price based on predicted win probability, audience match quality, and historical clearing price — outperforms static CPM bids over the course of a flight.

Publisher floor prices on LtvAdx vary by deal tier, content genre, daypart, and audience enrichment level. A FAST channel prime-time slot with HouseholdID-enriched audience data may clear at a $25 floor; the same channel's overnight inventory without identity enrichment may clear at $8. DSPs that cannot read or act on floor price signals in bid requests — using a single static CPM across all inventory — will consistently lose premium slots to floor-aware bidders while overpaying for lower-tier inventory. Configure floor-responsive bid logic in your DSP campaign settings and review clearing price distribution in delivery logs weekly.

Measurement and attribution in the DSP layer

DSP delivery reports for CTV campaigns should surface at minimum: impressions by device type, video completion rate by creative, household reach and frequency if the DSP supports household-level identity, deal-level delivery breakdown, and clearing CPM distribution. Reports that aggregate all video inventory without device type segmentation mix CTV impressions with mobile and desktop — rendering any CTV-specific optimization impossible because the KPI benchmarks for each environment are completely different.

For outcome attribution beyond delivery metrics, the DSP must either provide impression-level logs for export to the advertiser's measurement environment or integrate with a third-party attribution vendor. The CTV attribution and measurement guide covers the site lift, search lift, and incrementality methodologies that connect CTV delivery to downstream business outcomes. Most DSPs support impression log export via API; configure this export to flow into your data warehouse rather than relying on in-platform reporting for outcome analysis.

Brand lift measurement in the DSP layer requires a survey vendor integration and sufficient household-level exposure volume — typically 500,000+ impressions against a defined segment — to generate statistically significant results. For campaigns below this scale, correlation analysis between household CTV exposure and post-exposure web behavior via IP matching is a more practical measurement approach than formal brand lift methodology.

Connecting your DSP to LtvAdx supply

DSPs access LtvAdx CTV supply through an OpenRTB endpoint connection. The technical integration requires: endpoint registration, bid request parameter configuration (confirming which CTV-specific fields the DSP reads and acts on), creative format validation (VAST 4.2 compliance check), and deal ID activation for any PMP or PG arrangements. For DSPs running their first LtvAdx integration, the LtvAdx developer documentation provides the OpenRTB implementation guide with field mapping for CTV-specific parameters including pod structure, content metadata, and household identity extensions.

Agencies managing multiple DSP seats against LtvAdx supply should review the agency portal for multi-seat deal management and cross-DSP delivery reporting. The reporting API provides impression-level logs that can be ingested by any DSP analytics system for unified attribution analysis across supply sources. To discuss DSP integration requirements or deal structures, contact the demand partnerships team or request a platform walkthrough.

Stay ahead of CTV and addressable TV

Get articles on streaming monetization, identity, and programmatic TV.

Subscribe + request demo →
MS
Manmohan Singh

Head of CTV Product, LtvAdx

2026-06-14·14 min read

Related articles

Start trading TV

Ready to monetise CTV inventory?

See how LtvAdx fits your streaming and addressable TV setup — start free or book a walkthrough.

No minimum spend48-hour account reviewVAST 4.2 + SSAI docs includedIAB-compliant stack
IAB-compliant

<10ms

VAST decision latency

p99 under 15ms — product specification

IAB-compliant

7-tier

HouseholdID graph tiers

UID2 · PPID · ADID · DeviceID · ACR · IP/24 · fingerprint

Illustrative platform metrics · System status

VAST 4.2VMAP 1.0.1OpenRTB 2.6schainTCF 2.2CCPASCTE-35HouseholdID