Scope
This guide covers daily operation for Digital Twin. Availability depends on your tenant package, role and configured providers.
Purpose
Model measured funnel transitions and explore what-if scenarios.
Inspect baseline flow and adjust scenario assumptions.
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 baseline flow and adjust scenario assumptions.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Refresh the model from eligible observed outcomes.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Compare simulated changes with later actual movement.
Verify the result
Compare simulated changes with later actual movement. 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
Label assumptions and avoid presenting simulation as certainty. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.