Pilot Process: Matched Sample → License Workflow

A practical buyer workflow: scope success metrics, run a matched sample, confirm delivery specs and refresh cadence, then lock governance and go live.

Matched sample → license workflow

GSDSI pilots are designed as procurement measurement, not demos. Buyers scope a success metric (match rate, coverage, lift, model performance), run a matched sample against first-party seeds, confirm delivery specs and refresh cadence, then finalize governance terms and move to production activation.

Buyer workflow

Scope the endpoint: activation, measurement, risk, or research.
Run a matched sample (hashed seed match) to measure usable resolution.
Confirm delivery: SFTP/S3/Snowflake/API; Parquet/CSV/JSON; refresh cadence.
Lock governance: exclusions, retention, deletion SLA, downstream sharing rules.

Indicative economics

Matched samples are typically scoped at no charge or a nominal prep fee. Single-feed US production licenses often start in the mid five figures annually; multi-feed bundles scale with volume, refresh SLA, and activation rights. Final terms appear only in a signed order.

For provenance artifacts and exclusions, see the sourcing methodology. For identity resolution evaluation, start with the identity-graph diligence guide in resources.

Enterprise Data Products: Identity, POI, CTV/ACR Browse enterprise datasets: identity graph (MAID→HEM), CTV/ACR, POI polygons, mobility, clickstream, CPG, B2B contacts, property, and leads. Request pricing.
Identity Graph: MAID-to-HEM & Device Resolution MAID-to-HEM identity resolution for onboarding and measurement. Evaluate match rates, refresh cadence, and compliance. Request a matched sample.
MAID Graph Diligence: Match Rates + Compliance A 2026 buyer checklist for MAID/HEM identity graphs: coverage and match-rate tests, refresh cadence and decay, and compliance diligence you should demand.