Scope
This guide covers setup & configuration for Customer 360 & Identity. Availability depends on your tenant package, role and configured providers.
Purpose
Connect profile, activity and source evidence into one timeline.
Configure identity keys, sources and merge policy.
Before you start
Correct tenant and project selected
Required source or provider is available
An accountable owner is identified
Test data can be separated from live activity
Procedure
- Open the correct tenant and confirm the project or workspace that owns this capability.
- Configure identity keys, sources and merge policy.
- Connect or select the required source records and owners.
- Create a safe test configuration before using live customer or campaign data.
- Measure completeness, activity and lifecycle change.
- Keep merge history, provenance and uncertain matches visible.
Verify the result
Measure completeness, activity and lifecycle change. Confirm that the intended record, state, run or report is visible to another authorised operator and that its next owner is clear.
Completion checkpoint
The capability is in the intended state, evidence is current, exceptions are owned and the next action can be understood without a separate status message.
Controls and limitations
Keep merge history, provenance and uncertain matches visible. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.