Scope
This guide covers daily operation for Journey Experiments & Frequency. Availability depends on your tenant package, role and configured providers.
Purpose
Test paths while controlling message pressure and timing.
Monitor experiment paths and customer pressure.
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.
- Monitor experiment paths and customer pressure.
- Inspect the current status and supporting context before changing anything.
- Account for system behaviour: Assign eligible entrants and enforce send-time rules.
- Resolve failures, missing data or approval requirements before continuing.
- Close the loop: Review significance, path outcomes and pressure indicators.
Verify the result
Review significance, path outcomes and pressure indicators. 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
Protect holdouts, consent and minimum evidence thresholds. Predictive, attribution and recommendation outputs support operator judgement; provider and data limitations remain relevant.