Scope
This guide covers daily operation for Customer 360 & Identity. Availability depends on your tenant package, role and configured providers.
Purpose
Connect profile, activity and source evidence into one timeline.
Inspect profile, events, messages, campaigns and relationships.
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
- State the operating objective and the record, audience, campaign or project in scope.
- Inspect profile, events, messages, campaigns and relationships.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Stitch eligible identities as new evidence arrives.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Measure completeness, activity and lifecycle change.
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.