Scope
This guide covers daily operation for Offline Attribution. Availability depends on your tenant package, role and configured providers.
Purpose
Bring events, print and hoarding activity into analysis.
Enter or import offline touchpoints and reconcile context.
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.
- Enter or import offline touchpoints and reconcile context.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Process validated imports into reporting relationships.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Compare offline activity with leads, outcomes and margin context.
Verify the result
Compare offline activity with leads, outcomes and margin context. 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
Distinguish manually supplied data and document gaps. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.