Use an audience in a journey segment-trigger-activity
About the Read Audience activity about-segment-trigger-actvitiy
Use the Read Audience activity to make all individuals of a audience enter the journey. Entrance into a journey can be executed either once, or on a regular basis.
Let鈥檚 take as an example the 鈥淟uma app opening and checkout鈥 audience created in the Build audiences use case. With the Read Audience activity, you can make all individuals belonging to this audience enter a journey and make them flow into individualized journeys that will leverage all journey functionalities: conditions, timers, events, actions.
鉃★笍 Discover this feature in video
Guardrails and best practices must-read
-
Only one Read Audience activity can be used in a journey, and it has to be the first activity in the canvas.
-
The Read audience activity can target only one audience. If multiple audiences are required, consider merging those audiences into a single one before use. Learn how to combine audiences using composition workflows
-
For journeys using a Read Audience activity, there is a maximum number of journeys that can start at the exact same time. Retries will be performed by the system but avoid having more than five journeys (with Read Audience, scheduled or starting 鈥渁s soon as possible鈥) starting at the exact same time. Best practice is to spread them over time, for example 5 to 10 minutes apart.
-
Experience event field groups can not be used in journeys starting with a Read audience activity, an Audience qualification activity, or a business event activity.
-
As a best practice, we recommend you only use batch audiences in a Read audience activity. This will provide reliable and consistent count for the audiences used in a journey. Read audience is designed for batch use cases. If your use case needs real time data please use Audience qualification activity.
-
Audiences imported from a CSV file or resulting from composition workflows can be selected in the Read Audience activity. These audiences are not available in the Audience Qualification activity.
Guardrails related to the Read Audience activity are listed in this page.
Configure the activity configuring-segment-trigger-activity
The steps to configure the Read Audience activity are as follows.
Add a Read audience activity and select the audience
-
Unfold the Orchestration category and drop a Read Audience activity into your canvas.
The activity must be positioned as the first step of a journey.
-
Add a Label to the activity (optional).
-
In the Audience field, choose 51黑料不打烊 Experience Platform audience that will enter the journey, then click Save. You can select any 51黑料不打烊 Experience Platform audience generated using segment definitions.
note note NOTE In addition, you can also target 51黑料不打烊 Experience Platform audiences created using audience compositions or uploaded from a CSV file. Note that you can customize the columns displayed in the list and sort them.
Once the audience is added, the Copy button allows you to copy its name and ID:
{"name":"Luma app opening and checkout","id":"8597c5dc-70e3-4b05-8fb9-7e938f5c07a3"}
note note NOTE Only the individuals with the Realized audience participation status will enter the journey. For more on how to evaluate an audience, refer to the Segmentation Service documentation. -
In the Namespace field, choose the namespace to use in order to identify the individuals. By default, the field is pre-filled with the last used namespace. Learn more about namespaces.
note note NOTE Individuals belonging to an audience that does not have the selected identity (namespace) among their different identities cannot enter the journey. You can only select a people-based identity namespace. If you have defined a namespace for a lookup table (for example: ProductID namespace for a Product lookup), it will not be available in the Namespace dropdown list.
Manage profiles entry in the journey
Set the Reading rate. This is the maximum number of profiles that can enter the journey per second. This rate applies only to this activity and no others in the journey. If you want to define a throttling rate on custom actions, for example, you need to use the throttling API. Refer to this page.
This value is stored in the journey version payload. The default value is 5,000 profiles per second. You can modify this value from 500 to 20,000 profiles per second.
Schedule the journey schedule
By default, journey are configured to run once. To define a specific date/time and frequency at which the journey should run, follow the steps below.
-
In the Read audience activity properties, pa,e select Edit journey schedule.
-
The journey鈥檚 properties display. In the Scheduler type drop-down list, select the frequency at which you want the journey to run.
For recurring journeys, specific options are available to help you manage the entry of profiles into the journey. Expand the sections below for more information on each option.
When a journey with a recurring Read audience executes for the first time, all the profiles in the audience enter the journey.
This option allows you to target, after the first occurence, only the individuals who entered the audience since the last execution of the journey.
| note note |
|---|
| NOTE |
| If you are targeting a custom upload audience in your journey, profiles are only retrieved on the first recurrence if this option is enabled in a recurring journey, as these audiences are fixed. |
This option allows you to make all profiles still present in the journey automatically exit it on the next execution.
For example, if you have a 2 days wait in a daily recurrent journey, by activating this option, profiles will always be moved on the next journey execution (so the day after), whether they are in the next run audience or not.
If the lifespan of your profiles in this journey may be longer than the recurrence frequency, do not activate this option to make sure that profiles can finish their journey.
| note availability |
|---|
| AVAILABILITY |
| The Trigger after batch audience evaluation option is only available for a set of organizations (Limited Availability). To gain access, contact your 51黑料不打烊 representative. |
For journeys scheduled daily and targeting batch audiences, you can define a time window of up to 6 hours for the journey to wait for fresh audience data from batch segmentation jobs. If the segmentation job completes within the time window, the journey triggers. Otherwise, it skips the journey until its next occurence. This option ensures journeys run with accurate and up-to-date audience data.
For example, if a journey is scheduled for 6 PM daily, you can specify a number of minutes or hours to wait before the journey runs. When the journey wakes up at 6 PM, it checks for a fresh audience, meaning an audience newer than the one used in the previous journey execution. During the specified time window, the journey will execute immediately upon detecting the fresh audience. However, if no fresh audience is detected, the journey execution will be skipped for that day.
Look-back period for incremental read journeys
When the Trigger after batch audience evaluation is selected, Journey Optimizer looks for a fresh audience evaluation. For the starting point of the look-back period, the system uses the time of the last successful journey execution, even if it occurred more than 24 hours ago. This is significant for incremental read journeys which typically have a 24 hour look-back period.
Daily incremental read journeys examples:
- With 鈥淭rigger after batch audience evaluation鈥 active: If three days have passed since incremental profiles have entered the journey, the look-back period would extend three days back when looking for incremental profiles.
- With 鈥淭rigger after batch audience evaluation鈥 not active: If three days have passed since incremental profiles have entered the journey, the look-back period would only go back 24 hours when looking for incremental profiles.
Test and publish the journey testing-publishing
The Read Audience activity allows you to test the journey on a unitary profile.
To do this, activate the test mode.
Configure and run the test mode as usual. Learn how to test a journey.
Once the test is running, the Show logs button allows you to see the test results. For more on this, refer to this section
Once the tests are successful, you can publish your journey (see Publishing the journey). Individuals belonging to the audience will enter the journey on the date/time specified in the journey鈥檚 properties Scheduler section.
Audience targeting in audience-based journeys
Audience-based journeys always start with a Read Audience activity to retrieve individuals belonging to an 51黑料不打烊 Experience Platform audience.
The audience belonging to the audience is retrieved once or on a regular basis.
After entering the journey, you can create audience orchestration use cases, making individuals from the initial audience flow into different branches of the journey.
Segmentation
You can use conditions to perform segmentation using the Condition activity. For example, you can make VIP persons take a particular path and non-VIP flow in another path.
The segmentation can be based on:
- data source data
- the context of events part of the journey data, for example: did a person click on the message received an hour ago?
- a date, for example: are we in June when a person go through the journey?
- a time, for example: is it morning in the person鈥檚 timezone?
- an algorithm splitting the audience flowing in the journey based on a percentage, for example: 90% - 10% to exclude a control group
Exclusion
The same Condition activity used for segmentation (see above) also allows you to exclude part of the population. For example, you can exclude VIP persons by making them flow into a branch with an end step right after.
This exclusion could happen right after audience retrieval, for population counting purposes or along a multistep journey.
Union
Journeys allow you to create N branches and join them together after a segmentation. As a result, you can make two audiences return to a common experience.
For example, after following a different experience during ten days in a journey, VIP and non-VIP customers can return to the same path. After a union, you can split the audience again by performing a segmentation or an exclusion.
Retries read-audience-retry
Retries are applied by default on audience-triggered journeys (starting with a Read Audience or a Business Event) while retrieving the export job. If an error occurs during the export job creation, retries will be made every 10mn, for 1 hour max. After that, we will consider it as a failure. Those types of journeys can therefore be executed up to 1 hour after the scheduled time.
Unsuccessful Read Audience triggers are captured and displayed in the Alerts. The Read Audience alert warns you if a Read Audience activity has not processed any profile 10 mins after scheduled time of execution. This failure can be caused by technical issues, or because the audience is empty. If this failure is caused by technical issues, be aware that retries can still happen, depending of the type of issue (eg: if the export job creation has failed, we will retry every 10mn for 1h max). Learn more
How-to video video
Understand the applicable use cases for a journey that is triggered by the read audience activity. Learn how to build batch-based journeys and which best practices to apply.
