Skip to content

Commit e6df38a

Browse files
pwsegforstisabella
andauthored
Update src/personas/journeys/faq-best-practices.md
Co-authored-by: forstisabella <[email protected]>
1 parent 0d42352 commit e6df38a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/personas/journeys/faq-best-practices.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Aside from the entry condition, all Journey step conditions are triggered by fut
4343

4444
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.
4545

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:
4747

4848
| Condition Type | Automatic Historical Data Backfill |
4949
| ------------------ | ---------------------------------- |

0 commit comments

Comments
 (0)