Since 2018
Privacy-safe enterprise data
VOSB & SDVOSB
U.S. Veteran-Owned, Service-Disabled
SCC Transfers
EU/UK/CH per privacy policy
GDPR · CCPA · CPRA
Consent-first data sourcing
At a glance
Short, extractable evaluation notes for buyers (what you get, how it’s sourced, and how procurement typically runs).
What you get
- ACR-derived exposure events with identifiers for measurement and planning.
- Coverage cuts by OEM/platform and geography during evaluation.
- Governance-ready fields for dedupe + windowing.
How it’s sourced
- Documented provenance and permitted uses for measurement workflows.
- Exclusions and privacy controls aligned to buyer policy.
- Stable schema + refresh expectations in a delivery manifest.
How you buy it
- Matched sample to measure join yield and reach in your markets.
- Confirm delivery path (S3/SFTP/Snowflake) and formats (Parquet/CSV).
- License terms aligned to activation + measurement windows.
Want the buying guide?
If you’re evaluating vendors or writing an RFP, this guide lays out what to ask for (coverage, refresh, governance) and links to the best references.
Need an API key + JSON sample?
For technical evaluation, we can provide a sample payload, schema notes, and delivery options (S3/SFTP/Snowflake) aligned to your workflow.
Sample fields
A representative slice of the CTV / Smart TV (ACR) Feed schema. The data dictionary shared during evaluation lists every field with its type, nullability, join keys, and refresh cadence.
| Field | What it contains |
|---|---|
| ctv_id | Pseudonymous connected-TV device identifier. |
| event_timestamp | UTC timestamp for the tuning, content, or ad-exposure event. |
| content_id | Matched program, episode, creative, or other recognized content identifier. |
| channel | Linear network, streaming service, or channel associated with the event. |
| exposure_type | Classification of the event as programming, streaming content, or advertising. |
Proof & buyer diligence for ACR / CTV measurement
- Clarify the unit of measurement (household vs person) and how householding is constructed for cross-device joins.
- Require coverage by OEM/platform and a clear view of how ad detection events are derived.
- Plan governance up front: attribution windows, dedupe logic, and what qualifies as an exposure event.
Vendor comparisons
Use these buyer guides to compare this feed category with adjacent vendor offerings.
Related pages
How buyers diligence CTV / ACR data
CTV buyers usually start with a measurement pilot: confirm householding logic, OEM/platform coverage, exposure-event definitions, and whether ACR events can be joined to identity, mobility, or outcome files without overcounting reach.
- Clarify household vs. device-level measurement and dedupe rules before attribution.
- Request coverage by OEM/platform, geography, date range, and content or ad-detection method.
- Define attribution windows, exposure thresholds, and cross-screen join keys in the pilot brief.
- Confirm delivery cadence and whether files support clean-room or warehouse-based measurement.
