Customer data review
Understand the records before you use the profile.
Compare source keys, conflicting facts and permission evidence in a fictional example. Keep unanswered questions visible before planning the next step.
Fictional records · local review only
R01 · SHOP-017
Fictional records · local review only
- Source system
- shop-export
- Source record
- SHOP-017
- Customer key
- customer-017
- Key namespace
- fictional-store-01/customer
R02 · CRM-204
Fictional records · local review only
- Source system
- crm-export
- Source record
- CRM-204
- Customer key
- customer-017
- Key namespace
- fictional-store-01/customer
R01 + R02
Identity evidence: The two supplied keys match within the same namespace. This does not verify a person or merge a profile.
Permission evidence: R02 supplies an email/newsletter subscription record. R01 supplies no consent evidence. Permission for a combined use remains unresolved.
One review. Two different questions.
Select a record pair, then inspect identity evidence or permission evidence. The underlying records stay unchanged.
Questions for the reviewer
Which source owns the key, and what evidence would resolve this identity question?
C01 · R01 + R02
Matching supplied key
Identity evidence
The two supplied keys match within the same namespace. This does not verify a person or merge a profile.
Permission evidence
R02 supplies an email/newsletter subscription record. R01 supplies no consent evidence. Permission for a combined use remains unresolved.
No profile merged. No permission granted. No customer action sent.
Keep every fact beside its source.
Source record, namespace and observation time remain attached to each value. Missing fields are shown as not supplied, with no invented source or timestamp.
R01 · SHOP-017
Fictional records · local review only
- Identity evidenceSource system
- shop-export
- Fictional source reference: EX-CDP-R01#sourceSystemauthored-fixture-record
- Source record
- SHOP-017
- Fictional source reference: EX-CDP-R01#sourceRecordIdauthored-fixture-record
- Observed at
- 2026-05-14T10:00:00Z
- Fictional source reference: EX-CDP-R01#observedAtauthored-fixture-record
- Customer key
- customer-017
- Fictional source reference: EX-CDP-R01#customerKeyauthored-fixture-record
- Key namespace
- fictional-store-01/customer
- Fictional source reference: EX-CDP-R01#keyNamespaceauthored-fixture-record
- Postal code
- 10115
- Fictional source reference: EX-CDP-R01#postalCodeauthored-fixture-record
- Permission evidenceSubscription status
- Not supplied
- Fictional source reference: Not suppliedexpected-not-supplied
- Channel
- Not supplied
- Fictional source reference: Not suppliedexpected-not-supplied
- Purpose
- Not supplied
- Fictional source reference: Not suppliedexpected-not-supplied
- Recorded at
- Not supplied
- Fictional source reference: Not suppliedexpected-not-supplied
- Evidence reference
- Not supplied
- Fictional source reference: Not suppliedexpected-not-supplied
R02 · CRM-204
Fictional records · local review only
- Identity evidenceSource system
- crm-export
- Fictional source reference: EX-CDP-R02#sourceSystemauthored-fixture-record
- Source record
- CRM-204
- Fictional source reference: EX-CDP-R02#sourceRecordIdauthored-fixture-record
- Observed at
- 2026-05-14T10:05:00Z
- Fictional source reference: EX-CDP-R02#observedAtauthored-fixture-record
- Customer key
- customer-017
- Fictional source reference: EX-CDP-R02#customerKeyauthored-fixture-record
- Key namespace
- fictional-store-01/customer
- Fictional source reference: EX-CDP-R02#keyNamespaceauthored-fixture-record
- Postal code
- 10115
- Fictional source reference: EX-CDP-R02#postalCodeauthored-fixture-record
- Permission evidenceSubscription status
- subscribed
- Fictional source reference: EX-CDP-R02#consentStatusauthored-fixture-record
- Channel
- Fictional source reference: EX-CDP-R02#consentChannelauthored-fixture-record
- Purpose
- newsletter
- Fictional source reference: EX-CDP-R02#consentPurposeauthored-fixture-record
- Recorded at
- 2026-05-01T09:00:00Z
- Fictional source reference: EX-CDP-R02#consentRecordedAtauthored-fixture-record
- Evidence reference
- FICTIONAL-CONSENT-02
- Fictional source reference: EX-CDP-R02#consentEvidenceRefauthored-fixture-record
A matching field is not a verified identity.
Compare supplied keys within their declared namespace. Shared email addresses or postal codes do not settle conflicting identities. This example creates no unified profile.
The two supplied keys match within the same namespace. This does not verify a person or merge a profile.
- 01
Namespace
- 02
Supplied key
- 03
Conflicting facts
Identity evidence does not grant permission.
Review the supplied channel, purpose, status, time and evidence separately. Missing or conflicting entries remain unresolved, even when keys match.
R02 supplies an email/newsletter subscription record. R01 supplies no consent evidence. Permission for a combined use remains unresolved.
- Channel
- Purpose
- Subscription status
- Recorded at
- Evidence reference
Turn the review into questions for your team.
Plan the source scope, inspect the supplied records, document identity and permission gaps, then agree a separate validation with the responsible teams. Connection health, identity quality, consent propagation and activation are not verified here.
- 01
Plan the source scope
- 02
Inspect the supplied records
- 03
Record the open questions
- 04
Agree a separate validation
- Request scope review from the data owner
- Request evidence review from the identity reviewer
- Request purpose and channel review from the permission owner
- Connection health unverified
- Coverage and completeness unknown
- Identity quality unverified
- Consent propagation and deletion unverified
- Activation unverified
Bring a clear source question to the next conversation.
Start with connection scope or explore an adjacent customer-care example. This page sends no data and takes no action on a customer.