Scope
This guide covers setup & configuration for Analytics & Attribution. Availability depends on your tenant package, role and configured providers.
Purpose
Read cross-channel performance through multiple contribution lenses.
Confirm events, conversions, channels and reporting windows.
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.
- Confirm events, conversions, channels and reporting windows.
- Connect or select the required source records and owners.
- Create a safe test configuration before using live customer or campaign data.
- Compare platform, multi-touch and Markov perspectives.
- State coverage gaps and model assumptions alongside results.
Verify the result
Compare platform, multi-touch and Markov perspectives. 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
State coverage gaps and model assumptions alongside results. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.