You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/personas/journeys/faq-best-practices.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ Aside from the entry condition, all Journey step conditions are triggered by fut
43
43
44
44
When you [include historical data](/docs/personas/journeys/build-journey/#using-historical-data-for-the-entry-step) in a Journey's entry condition, Personas backfills entry with users who previously satisfied the entry condition. For example, to evaluate if a user has ever used a discount code mid-Journey, create and configure a [Computed Trait](/docs/personas/computed-traits/#conditions) to select for `discount_used = true` to use in your Journey.
45
45
46
-
This historical backfill has no impact on any additional Journey steps, however. To include historical data in post-entry conditions, then, first use the following table to identify which conditions will automatically backfill historical data:
46
+
This historical backfill has no impact on any additional Journey steps, however. To include historical data in post-entry conditions, use the following table to identify which conditions will automatically backfill historical data:
47
47
48
48
| Condition Type | Automatic Historical Data Backfill |
0 commit comments