Objective

This article provides information on how to include historical information in V1 Journey steps, beyond journey entry. 

When you include historical data in a journey’s entry condition, Unify identifies users who previously satisfied the entry condition and adds them. Including historical data doesn’t impact any additional journey steps, however. All journey step conditions are triggered by future events and existing trait memberships. Event-based conditions only evaluate events that occur after the journey is published.

Product

Twilio Segment

Environment

Segment Console

Procedure 

To include historical data in post-entry conditions, use the following table to identify which conditions will automatically include historical data:

To include historical data based on custom traits or events that predate the journey, first build an Audience that includes the targeted data by following these steps:

1. Create a standard Engage Audience outside of the Journeys builder.
2. Add conditions that include the historical event or custom trait you want to include in the journey step.
3. After you’ve created the Audience, return to Journeys and create a Part of an Audience condition that references the audience you created in Step 2.

For example, to include custom trait = ABC in a journey, create an Audience called ABC that includes that custom trait, then add the journey condition Part of Audience ABC.

Using the Part of Audience condition, Journeys then populates the custom trait as if it were using historical data.

Additional Information 

For more information, refer to the following documents:

• Build a Journey
• Understanding Journeys Logic
• Journeys Best Practices and FAQs