This page answers common questions for marketers building and managing batch journeys. It covers journey configuration, stage and profile behavior, segment evaluation, permissions, and workflow troubleshooting.
Individuals can launch a journey only if they have edit access to folders with journeys and journeys set up as jump destinations in the current journey's Exit criteria, Goal, and Jump events.
If you reference profiles within a batch journey (or batch journey stage) with versions, all launched versions' profiles are combined. For example, if Journey A has three versions with 100 profiles in each version, 300 profiles will be referenced in the drag-on rule.
Batch journeys rely on the daily running of parent segments. Real-time journeys can send a triggered activation within minutes. Learn more about Creating a Real-time Triggered Activation.
Real-time journeys require a separate contract from batch journeys.
Yes. You can a maximum of 120 events to a journey. This feature is in Beta.
Each journey can have a maximum of 8 stages.
Each journey can have a maximum of 120 events. Within that journey, each stage can have a maximum of 70 events. This feature is in Beta.
When creating a journey with 120 events, limit your activations to less than 50 for better performance.
Yes. If you create a journey version, you can edit many journey elements.
Only for the first stage. All stages that follow the first stage have entry criteria based on the milestone of the previous stage and/or exit criteria of other stages.
There are two options:
Stale Profile: Enter the number of days it takes for profiles to become stale after staying in a journey stage.
Custom Exit Criteria: Create a rule through the Segment Editor, for example, an opt-out profile.
The profile belongs to the lowest stage in the journey. For example, if the profile qualifies for both Awareness and Interest, the profile belongs in Interest.
If the other stage's goal or milestone is fulfilled, the profile will directly skip and go to the stage that fulfilled the condition.
Even if a profile is currently in a wait step, it can still move to a later stage by completing that later stage's goal or milestone.
No. A milestone or goal segment evaluates against its entire Parent Segment, not just the profiles that reached the previous stage or entered the journey. This is by design — it lets profiles "catch up" and enter a later stage even if they missed an earlier one.
This means a milestone or goal rule that isn't scoped to a stage can match far more profiles than expected, especially if it's broader than the entry criteria used to test the journey. To restrict a milestone, goal, decision point, or exit criteria to profiles that actually reached a specific stage, add a journey stage location condition, for example:
- Profile is currently IN [Journey Name], Stage 1
The Complete Goal metric on the Batch Journey Dashboard is scoped differently: it only counts profiles that were in a journey stage when they met the goal criteria. The Goal segment itself is not scoped this way — reusing it elsewhere, for example as entry criteria for another journey, pulls in the full Parent Segment.
Yes. A profile can return to a journey after it has exited.
No. Profiles can move forward to the next stage; however, they can’t return to a previous stage.
For example, you want to deliver an ad hoc marketing campaign to:
- Profiles who are not in stage X in a journey
OR
- Send an email to profiles who are not associated with a journey
Yes. Treasure Data segments can add an existing journey by including the journey in a segment rule. They can extract already included/excluded profiles in a specific journey using it.
Journeys included in segments must be live.
Full Control Folder Permission: A user can create, modify, or delete any Journeys in selected folders or child folders. Additionally, a user can get a list of profiles as well as customers' endpoints.
View Folder Permission: A user can view Journeys in selected folders or child folders.
Typically, it's due to an activation scheduling issue. Set the activation schedule after the parent segment and journey workflow runs.
Otherwise, the activation runs a different schedule, which results in profiles not being recognized correctly.
When creating a batch journey activation, you can automatically set the activation to run after the parent segment and journey workflow refreshes have been completed.
Let's assume multiple priority groups contain multiple journeys. The capping is 2. On Day 1, regardless of how many profiles qualify for a journey, with a cap of 2, the qualifying profiles only enter the first two prioritized journeys (Journey A and Journey B). On Day 2, Journey B is paused; the qualifying profiles enter Journey A and C because the cap is still 2, but Journey B is no longer available in the priority group.
You need to pay attention to the session times of workflows. The correct sequence for workflows is as follows:
Parent segment workflow > batch journey workflow > batch journey activations workflow.
You can select
Because batch journeys run daily, you need to evaluate the parent segment schedule and adjust the schedules of batch journey and activation workflows accordingly. For more information about workflows, see Journey Workflow Dependencies.
You can recover data using the following Treasure CLI code.
# Rerun the audience workflow (journey workflows are triggered automatically afterward)
# td workflow start cdp_audience_{:audienceId} audience --session daily
# Rerun the activation workflow
$ td workflow start cdp_journey_{:journeyId} syndication_{:activationId} --session daily In the previous example, "session daily" is used. You can change the session time.
Available session times
--session <hourly | daily | now | yyyy-MM-dd | "yyyy-MM-dd HH:mm:ss"> set session_time to this time (required)