When a journey's entry source is configured in Journey Builder, the data source from which contacts are admitted is usually a data extension.
When an event fires, Journey Builder admits the contacts stored in the entry source data extension that meet entry criteria. Specifically, Journey Builder evaluates the data extension from its first row and continues until all existing rows are evaluated.
The next time the event fires, the entry source begins evaluating rows from the point where it stopped. This factor prevents contacts that are already in the journey from entering the same journey again if their contact record is unchanged.
Single Event Source for Multiple Events
Multiple entry sources can use the same data extension.
Three methods exist for admitting contacts into a journey.
- API
- Automation Studio’s Fire Event activity
- The Schedule feature found within Journey Builder’s event setup process
Ensure that the desired contacts enter each journey as intended. Use one of these three methods to admit contacts from an event source data extension.
Journey Builder now evaluates the event source data extension separately for each individual event.
Events and Shared Data Extensions
A shared data extension can be used as the entry source data extension in more than one business unit. Journey Builder separates the processing of the data extension for each business unit. Events that run against a data extension in Business Unit A evaluate records starting at the last row that was evaluated previously. But when an entry source uses this data extension in Business Unit B for the first time, it begins at the first row.