Identity graph
Email, phone, hashed ID, device, and CRM ID reconciled deterministically.
SINGLEVIEW
One customer, across every touchpoint.
SingleView stitches web, app, CRM, and offline events into a consent-aware customer profile that your paid media, CRM, and analytics teams can all use.
Identity, stitched deterministically.
Journey stitching
Web plus app plus offline touchpoints in one timeline.
Consent layer
Every profile carries the consent flags collected at source.
Open outputs
Push to your warehouse, CRM, and every ad destination via Signals.
HOW IT FITS
Optional, and exactly where it belongs.
SingleView is optional. Signals customers can add SingleView when they need a unified profile view for audiences, measurement, or retention work.
It feeds directly into Segments and back through Signals, so identity work done once serves every downstream use.
Identity questions, answered.
Do I need to move data into Datahash to use SingleView?
Events already flowing through Signals are reusable directly. Warehouse-resident data can be referenced in place or synced on a schedule.
How do you handle consent revocation?
Profiles carry per-purpose consent flags. A revocation at source propagates to the profile and stops downstream activation for that purpose.
Is SingleView a CDP?
It solves the identity slice of what a CDP does, purpose-built for activation. It does not try to be your event warehouse or campaign tool.
What identifiers do you support?
Email, phone, hashed IDs, device IDs, and CRM IDs, reconciled deterministically. No probabilistic guessing.
NEXT STEP