
Prepared by GSDSI Regulatory Content Team
Last updated
CTV measurement is strongest when it is designed as a test before the campaign launches, not reconstructed after a dashboard disappoints. Automatic content recognition (ACR) can identify exposure at the smart-TV or household level; identity graphs can connect that household to eligible outcome signals; foot traffic and transaction data can indicate offline response. None of that proves incrementality unless the test has clean eligibility rules, control design, lookback windows, and suppression logic. This guide is for advertisers and agencies using CTV/Smart TV ACR, MAID identity, global mobility, and cross-channel measurement. Pair it with seed match testing and clean-room joins when multiple parties touch the same keys.
A CTV test should start by choosing one primary question: Did exposed households visit stores? Did exposed households purchase? Did a campaign shift category share? Did incremental reach improve compared with linear or social? Each question needs a different outcome source and test design. The Media Rating Council and IAB Tech Lab both provide useful measurement vocabulary, but buyers still need to translate standards into campaign-specific acceptance criteria: minimum cell sizes, reporting cadence, and what constitutes a successful read for finance versus media.
For retail and QSR brands, foot traffic may be the fastest outcome. For CPG and financial services, transaction or panel-based conversion may be more relevant. For awareness campaigns, reach and frequency may matter more than immediate offline response. Write the primary KPI in the test charter before any vendor sample arrives; otherwise every graph vendor will optimize for the metric they sell best.
Document holdout availability in the media plan before signing data vendors. If the buy cannot support a randomized holdout, say so upfront and choose geo or modeled controls explicitly. Post-campaign debates about incrementality are cheaper when the control strategy was pre-registered with finance and legal.
The operational stack has five layers buyers should name in the RFP: ACR exposure events from opted-in smart-TV panels; a household graph linking CTV device or IP household to hashed email, MAID, address, or other approved join keys; an outcome signal (store visits, transaction panels, web actions, app events, or CRM conversions); a control design; and a governance layer covering permitted use, suppression, aggregation floors, deletion, and campaign retention limits. The stack should be tested with a seed file before the campaign when possible: match rate without stability and permitted use is a vanity metric.
When the advertiser, publisher, and data provider cannot share raw keys, route joins through a clean room and pre-register the join specification. The FTC business guidance on privacy and security is a useful backdrop: downstream measurement should match the notices and expectations attached to collection, even when identifiers are pseudonymous.
Attribution counts observed outcomes after exposure. Incrementality estimates what changed because of exposure. Buyers should require one of four control approaches: randomized holdout, publisher or platform holdout, geography split, or a modeled baseline with pre-period validation. A geo split is easier to explain but may confound with local events. A modeled baseline scales but can hide bias. A randomized holdout is strong but not always available in CTV buys. Report both attributed outcomes and lift confidence; executives need the plain-English version of what changed, how confident the team is, and what should change in the media plan.
Pre-register analysis windows in the test plan. Shifting lookback after results arrive is how teams accidentally manufacture lift. Document whether the read is household-level, device-level, or aggregate-only: the privacy posture and the statistical story change together.
Offline outcomes depend on POI polygon quality and mobility panel math. A household graph can be excellent while visit attribution bleeds into adjacent tenants because the geofence was a radius, not a footprint. For retail use cases, connect the test to retail site selection analytics and CTV attribution.
Score the vendor stack with the RFP matrix before production. Contracts should specify retention for exposure logs, outcome joins, and derived segments; deletion when a source revokes consent; and whether benchmark tables may survive termination. Measurement vendors often want long retention for model tuning; advertisers often want short retention for privacy: negotiate the minimum viable retention for the stated use case.
GSDSI supports CTV exposure, identity linkage, mobility, and outcome-oriented measurement through CTV/Smart TV ACR, MAID Feed, and cross-channel measurement. Run a scoped pilot through the pilot process with pre-registered KPIs before full-market rollout.
Media and analytics leads should align on a single reporting calendar: exposure date, outcome date, and analysis freeze date. Late-added impressions after the freeze create attribution inflation that looks like performance. Document whether deduplication runs at household or device grain and whether cross-device graphs are in scope for the test. Those choices change both match rates and privacy review.
Publish a one-page methods appendix with every results read: exposure definition, outcome lag, control type, match-rate tiers, and suppression rules. Methods appendices reduce rework when finance or legal asks why two vendors disagreed: the disagreement is usually definitional, not mathematical.