Manage contacts, identity, and consent
Keep customer profiles useful for personalization while respecting channel-specific permission and suppression states.
What you’ll achieve
- Reliable customer profiles whose identity, history, and channel permissions support compliant segmentation and personalization.
Folgen Sie dem Arbeitsablauf
-
1
Open Data → Own Data → Contacts
Select the correct connector and use search, filters, and columns to inspect known contacts and anonymous visitors without confusing records from different workspaces.
-
2
Open a contact profile
Review identity channels, email and SMS marketing state, push subscription, customer attributes, custom fields, events, orders, product affinity, notes, and message history.
-
3
Treat consent by channel
Email, SMS, and web push permissions are separate. Subscribed, not subscribed, unsubscribed, unknown, and suppressed states must not be treated as interchangeable.
-
4
Edit only with a valid source
Correct identity or marketing state only when you have a traceable lawful basis. Record useful context and avoid overwriting a connector’s authoritative field without understanding synchronization.
-
5
Resolve duplicates carefully
Use verified identifiers and history before merging or deciding that two records represent the same person. Preserve consent, suppressions, orders, and event provenance.
-
6
Test downstream eligibility
Preview an audience and verify that subscribed contacts are included, unsubscribed or suppressed contacts are excluded, and anonymous visitors are used only where the action supports them.
Verify your work
- Channel-specific consent matches the source record
- Message history and suppression state explain current eligibility
- Audience previews exclude unsubscribed and suppressed contacts
If something doesn’t look right
A known customer appears anonymous
Check connector identifiers, email or phone capture, and pixel identity linkage.
Consent changes revert
Verify which connector is authoritative and whether a later sync overwrites the local value.
Duplicate profiles remain
Compare normalized identifiers and source IDs before using the merge process.
Limitations and safeguards
Leado displays and applies available consent signals; your organization remains responsible for lawful basis, retention, notices, and regional requirements.