Journeys Best Practices and FAQ
Enforce exclusivity in multi-branch splits
When you create a multi-branch split, do not create overlapping conditions that might lead a user to qualify for more than one step at a time.
- In the case where a multi-branch split is based on the conditions
registration form submittedand
webinar attended, a user may satisfy both conditions, and therefore is eligible for both paths.
- To set a priority, branch 2 should then be
who performed registration form submitted and did not perform webinar attendedto ensure mutual exclusivity
Add time windows whenever possible
Add time windows when defining conditions to enforce funnel constraints in a Journey, rather than using an unbounded event condition which operates on the entire history of the user profile. For example, to check if a user has completed an order since receiving an email triggered 7 days ago, use the condition “Order Completed at least 1 time within 7 days.”
Suppress targeting with journey lists
Unlike lists associated with Personas Audiences, users who are added to a journey list cannot be subsequently removed. Lists are typically associated with advertising campaigns, and you must take additional steps if you wish to ensure that users do not continue to be targeted with ads after they achieve some goal. A typical implementation pattern is:
- Use a send to destination step to add users to the initial targeting list.
- Create additional journey steps to model the conditions where a user should be removed from targeting. Create a second send to destination step for the removal list.
- When configuring targeting conditions in the destination interface, use boolean logic to include only those users who are in the initial list AND NOT in the removal list.
Review your Journey in drafts first
Save your Journey in a draft state so that you can review before you publish it. Once you publish a Journey, you cannot edit select portions of a Journey and Journeys sends data to destinations.
Make a copy to edit published Journeys
Once you publish a Journey, you cannot add, delete, or edit the steps within the Journey. You can edit the Journey name, description, and destinations.
To edit the steps within a published Journey, make a copy of the Journey you wish to edit, make adjustments, delete the original Journey, and then publish the revised Journey.
When you do this, the key used for syncing to destinations will be different from the copied Journey. Make sure you change the reference key used in the downstream destinations accordingly.
Use Traits for conditions based on historical data
Aside from the entry condition, all Journey step conditions are triggered by future events and existing trait memberships. This means that event-based conditions evaluate events that have occurred after the Journey is published.
As a result, if you want to include historical events that may have occurred before the Journey was published, create conditions based on traits, instead of events.
For example, to evaluate if a user has ever used a discount code mid-Journey, create and configure a Computed Trait to select for
discount_used = true to use in your Journey.
Use dev spaces and data warehouse destinations to test journeys
Follow these best practices to test your journeys:
- While in the process of configuring a journey, use dev Personas spaces to model that journey without affecting production data.
- Connect a data warehouse to each step of the journey to test for success or failure of that step.
- For early version journeys, scaffold Send to Destination steps without connecting to your production advertising or messaging destinations.
- Verify individual users’ progress through the Journey in the Personas Explorer view.
Frequently asked questions
How often do Journeys run?
Journeys run in real-time, like real-time Audiences in Personas. This means that users will progress through Journeys as Segment receives new events.
How many times can a user enter one Journey?
Users can enter a given journey a maximum of one time.
What destinations does Journeys support?
Journeys supports all Personas destinations, including Destination Functions. Read more in Send data to destinations.
What are the reporting capabilities of Journeys?
When building a Journey, if you check Use historical data, you can see the estimated number of users in the initial cohort.
Once published, Journeys displays the number of users are in each step of the Journey at any given time.
How are users sent to downstream destinations?
The data type you send to a destination depends on whether the destination is an Event Destination or a List Destination.
Which roles can access Journeys?
For Personas Advanced customers, users with either the Personas User or Personas Admin roles can create, edit, and delete journeys. Users with the Personas Read-only role are restricted to view-only access.
Why am I seeing duplicate entry or exit events?
Journeys triggers audience or trait-related events for each email
external_id on a profile. If a profile has two email addresses, you’ll see two Audience Entered and two Audience Exited events for each Journey step. Journeys sends both email addresses to downstream destinations.
This page was last modified: 28 Sep 2021
Questions? Problems? Need more info? Contact us, and we can help!