One person, many records
Anonymous and known identities never meet, so history is split.
Platform Foundation Customer Profiles
The same person shows up as a booking, a loyalty number, an app login and a support call. Resolve them into one trusted profile, carefully: with evidence for every link, and the ability to undo any merge.
Match evidence
Why change
Identity is where personalisation quietly goes wrong. Too cautious and you see three strangers. Too eager and you send one person another person's booking.
Anonymous and known identities never meet, so history is split.
A family phone, a shared inbox or one booking for four passengers is not one person.
Nobody can say why two records were joined, or separate them again.
Permissions from one system are not carried to the unified profile.
What it does
A match score is evidence, not permission to merge. Policy decides what links automatically, what goes to a person and what must never be joined.
01 Hybrid identity resolution
Verified identifiers link deterministically. Messy historical records are scored probabilistically, with optional machine learning for the hard cases. Then a policy layer applies the rules a score cannot know: households, shared bookings, verified conflicts.
| Attribute | Record A | Record B | Evidence |
|---|---|---|---|
| Name | Priya S. Menon | Priya Menon | Strong |
| Date of birth | 14 Feb 1991 | 14 Feb 1991 | Strong |
| priya.m@… | menon.family@… | Different | |
| Phone | +91 98… 412 | +91 98… 412 | Shared? |
| Same booking | PNR K7Q2LM | PNR K7Q2LM | Caution |
Fictional records. A high score alone never triggers an automatic merge.
02 The unified profile
One profile with a timeline of events, computed traits and the identifiers behind it. Marketers see the story; systems read it through an API in milliseconds; both see the same thing.
03 Consent and governance
Each attribute carries its source, its purposes and its retention period. Every read is checked against them. When a customer withdraws consent or asks to be forgotten, the change reaches every downstream system.
Agents at work
Identity agents normalise, find candidates, score them and prepare the evidence. High-confidence, policy-eligible pairs link automatically. Everything ambiguous goes to a steward, and their decisions teach the system.
Deterministic links on verified identifiers, trait computation and consent propagation.
Probabilistic matches below the auto-link bar, unmerges, and changes to matching rules or thresholds.
Merging across verified conflicts, linking on weak signals alone and using data beyond its consented purpose.
What's inside
Shared by every other capability, and available to the rest of your stack through a stable interface.
Deterministic identifiers with merge safeguards.
Statistical linkage for incomplete and inconsistent records.
Names, emails, phones and addresses standardised, originals preserved.
Confidence thresholds, merge and unmerge rules.
Events, attributes and identifiers in one view.
Lifecycle, propensity and value, updated as events arrive.
People, accounts, bookers and devices kept distinct.
Record-level evidence and a full merge audit.
Review queues, golden-record governance and corrections.
Enforced on every read, withdrawal propagated downstream.
Right-to-erasure and correction with evidence.
One contract, whether the profile lives in our store or your CDP.
How it runs
Each step is a named, logged stage. Nothing autonomous is switched on until its data, permissions, monitoring and rollback have been checked.
How you'll measure it
We agree the numerator, denominator, cohort and success gate with you before anything goes live, and compare against a baseline or a holdout, never against a hunch.
Questions
Both. Verified identifiers such as a loyalty number link deterministically. Probabilistic and machine-learned scoring handles incomplete historical records. A policy layer then decides what may link automatically.
It can be undone. Source records are never overwritten, every link stores its evidence, and an unmerge restores the original profiles and corrects downstream audiences.
The Data Platform connects sources, builds the context graph and activates audiences. Customer Profiles is the identity and consent foundation underneath: deciding who is who, and what may be done with what you know.
Yes. An adapter exposes your current profiles through the same interface, so other capabilities work without a migration. You can add our identity resolution only where yours has gaps.
Composable by design
Profiles are a foundation. Every capability above them gets better as identity gets cleaner.
Sources, context graph, audiences and activation built on resolved identity.
ExploreReal-time decisions that know the whole customer, not one session.
ExplorePurchases and loyalty state attached to the right person.
ExploreWorks with your booking, commerce, CRM, loyalty and contact-centre systems. Bring your own Customer 360, or use ours.
Small language models trained on marketing data are deployed inside your cloud or data centre, so customer data and the models reasoning over it stay under your control.
Getting started
Pick the two systems that disagree most about who your customers are. Agree identity and consent policy, measure precision on a labelled set, then switch on linking.