Journey Optimizer: outdated audience count due to manual segment evaluation
This article offers strategies to address the ÃÛ¶¹ÊÓƵ Journey Optimizer issue where a journey doesn’t reflect the most recent qualified data. This issue arises when segments are manually evaluated but don’t update the profile snapshot dataset, leading to outdated audience counts.
Description description
Environment
Product: ÃÛ¶¹ÊÓƵ Experience Platform
Component: Journey Optimizer
Issue/Symptoms
Segments evaluated manually on the same day doesn’t update in the journey, leading to journeys reflecting outdated audience counts.
Cause
The issue arises because manual segment evaluations do not trigger export jobs, resulting in profile snapshot datasets not being updated. Consequently, discrepancies between scheduled and manual segment jobs lead to incorrect audience counts being used in journeys.
Resolution resolution
To address this issue, follow these troubleshooting strategies:
- Schedule manual segment jobs after daily batch segmentation jobs to ensure changes from manual evaluations are included in subsequent exports.
- Align your segmentation strategy with scheduled export jobs, as manual segment evaluations don’t automatically trigger export jobs.
If manual evaluation is necessary, follow it with an export job to update the profile snapshot datasets that journeys read. - For real-time updates within a day, consider using streaming ingestion methods instead of batch processing. This is because batch segments can’t be updated and reflected in journeys on the same day without an export job.
- Regularly monitor and adjust segmentation job schedules based on data ingestion times to ensure timely updates in profiles used by journeys.