- Type
- not stated
- Format
- Tabular identity-resolution output: record-linkage/match tables keyed to a persistent person and household ID, delivered as an enrichment layer over the retailer's own transaction feed (CRM/loyalty-compatible file or API join), not as raw transaction files
- Volume
- Order of 100M+ household-linked records across deployed retail bases: the case study reports 70%+ of a national chain's in-store transactions resolved to real individuals and households, which on a single national grocer's volume implies tens of billions of resolved transaction-to-person linkages over multi-year history
- Users
- N/A as a consumer count — B2B identity platform. Client footprint instead: national grocery and mass-merchant chains, each contributing very large transaction streams (a single national chain covers tens of millions of households). Deep Sync itself is an 83-person company (~$68.5M revenue range), i.e. enterprise-scale deployments rather than a long tail of small accounts. Request further research on the exact number of retailer deployments.
- History
- 7 years
- Update frequency
- not stated
- Growth
- Active — current marketing use-case content, 83 employees and a ~$68.5M revenue range on the company record, and identity/transaction-matching is the company's flagship positioning
- Launched
- ~2022-2024 for the Transaction Matching product line as currently branded (company record vintage 2022 under the Deep Sync identity); the underlying data business predates the rebrand through its predecessor identity/marketing-data assets
- Delivery
- not stated
- Entity mapping
- not stated
- Sample
- not stated
- Point-in-time
- not stated
- Licence
- not stated