Entry Trigger Node
Overview
The entry trigger node allows you to specify how users should enter the journey. Click Add a trigger and select a trigger type:
Past condition
You can use existing segments to be the past conditions, or manually define the conditions using events and attributes. After the journey becomes active, the system will import users who meet the conditions into the journey. After the initial import, the system will check for qualified users every 6 hours and add them to the journey.
- Use segments: Select segments you want to include or exclude. You need to include at least one segment.
- Define conditions: Select the events and attributes you want to include or exclude.
- The Users to include section allows you to include users who have the specified user attributes or have performed the specified user events. The Users to exclude section allows you to exclude users who have the specified user attributes or events.
- You can add one or multiple conditions. If you select All, users need to match all conditions to be considered a match. If you select Any, users who match any of the conditions will be considered a match.
- Enter a number for Only consider events in the last x days. Only events that occurred within that time period will be used to calculate qualified users. This setting does not apply to user attributes that are set as conditions.
Limitation
New offline users uploaded within one day may not be processed in time to be considered in the past conditions.
Real-time event
You can select one event to be the trigger. Users will only enter the journey if the event happened after the journey becomes active. If the event is an offline event, the event timestamp must be later than the journey activation time, and the users will enter the journey after the offline events are uploaded.
To set an audience filter, select Only include users in the selected segment and select up to 5 segments. The system will check for qualified users in segments every 6 hours.
Date-based
You can let users enter the journey based on a date that is associated with that user. Here are some common ways to use a date-based trigger.
- Birthday: Send a coupon to users during the month of their birthday
- Membership expiration date: Send a renewal reminder to users 5 days before their membership expires
Note
See Tracking date format data for requirements to use user attributes as date-based triggers. Currently, event parameters cannot be used as date-based trigger.
Select the user attribute you want to use as the trigger, and set up the timing of the trigger. If you want to use a date in the past, such as the user's birthday, select Ignore the year in the date.
In the screenshot below, users will enter the journey on the first day of the month of their birthday. For example, a user with a birthday on 1980-04-10 will enter the journey on April 1 every year during the journey schedule. If Ignore the year in the date is not selected, the journey will not be triggered because the user's birthday is in 1980 when the year is considered.
Updated 2 months ago