Merge pull request #6655 from segmentio/samkcrespo-patch-22

Add FAQ on handling historical data in Journey entry conditions

Author: pwseg

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

@@ -99,3 +99,9 @@ Journeys triggers audience or trait-related events for each email `external_id`
 #### How quickly do user profiles move through Journeys?
 
 It may take up to five minutes for a user profile to enter each step of a Journey, including the entry condition. For Journey steps that reference a batch audience or SQL trait, Journeys processes user profiles at the same rate as the audience or trait computation. Visit the Engage docs to [learn more about compute times](/docs/engage/audiences/#understanding-compute-times).
+
+#### How can I ensure consistent user evaluation in Journey entry conditions that use historical data?
+
+When you publish a journey, the entry step begins evaluating users in real time while the historical data backfill runs separately. If a user's events or traits span both real-time and historical data, they might qualify for the journey immediately, even if their full historical data would have disqualified them.
+
+To prevent inconsistencies, you can manually create an audience that includes the same conditions as the journey's entry step. This ensures that it evaluates both real-time and historical data. You can then use this pre-built audience as the journey's entry condition. This approach guarantees that Segment evaluates users consistently across both data sources.