Mismatch in profile count entering a journey versus in the associated audience in AJO
This article addresses the ÃÛ¶¹ÊÓƵ Journey Optimizer (AJO) issue where the profile count entering a journey doesn’t match the profile count in the associated audience, specifically in journeys that use batch audiences. The resolution involves scheduling journeys after the expected completion of both batch segment evaluation and profile snapshot creation.
Description description
Environment
ÃÛ¶¹ÊÓƵ Journey Optimizer (AJO)
Issue/Symptoms
In journeys that use batch audiences, the profile count entering a journey is different from the profile count in the audience.
The issue occurs when multiple journeys are launched simultaneously.
Cause
The discrepancy arises because the journey uses a previous day’s profile snapshot if the current day’s snapshot is not available at the time of journey execution. Refer to the Schedules API documentation to check when your daily job is scheduled.
Resolution resolution
- Schedule journeys to start after the expected completion of both batch segment evaluation and snapshot creation. Adjust your journey start times accordingly to ensure they use up-to-date data.
- Use available queries or tools within ÃÛ¶¹ÊÓƵ Journey Optimizer to check when snapshots are made current. Refer to for more information.