1. Click New Event.
2. Choose an event type to tell Journey Builder which event definition to use. Usually, marketers choose a Contact Data event.Note Event types do not dictate the data source that contacts enter a journey from. Choose thedata source in a subsequent step.
3. Add a name, description, event definition key, and icon. The event definition key is used when calling an event via API. If you do not have one, Journey Builder provides it automatically.
4. Select a sendable data extension (DE), the data source where customer actions and data are recorded, and tell Journey Builder when and how often to check it. When Journey Builder finds new customer records, it automatically tries to enter them into the journey. If they meet the filter criteria set on the next step, Journey Builder admits them.Journeys that include the Send Email activity must use an event source data extension that includes these fields: NameData TypeEmailAddressEmail AddressSubscriberKeyTextIf one or both fields do not exist in the format shown above, Journey Builder creates them and appends them to the event source data extension.Note To prevent errors, ensure thatno other fields in the data extension contain the following:A field named SubscriberKey, with a data type other than TextA field named EmailAddress, with a data type other than Email AddressWhen the event source is modified, added to, or overwritten, this action constitutes an entry event. A single entry event can be used to kick off multiple journeys.
5. A field named SubscriberKey, with a data type other than Text
6. A field named EmailAddress, with a data type other than Email Address
7. If necessary, create a filter using contact attributes so the journey admits only contact records that meet the filter criteria set on this step. An entry event's configuration details appear on the journey canvas. Determine when and how often Journey Builder checks the event source for new records to enter the journey.
8. If contacts enter the journey via API or using Automation Studio, select NotApplicable. Setting an entry schedule here is not necessary.
9. If contacts should enter the journey according to a schedule, select Run using thefollowing schedule.
10. Set the date, time zone, and repetition schedule. The default repeat setting is None, which means the entry event runs only on the scheduled date and time.The schedule dictates when Journey Builder checks the event source for new records. The schedule set here does not admit contacts into the journey unless the journey has been activated. In cases where the schedule set here begins before journey activation, Journey Builder only admits contacts that are added to the event source following activation.