Use an audience in a journey segment-trigger-activity
Add a Read Audience activity about-segment-trigger-activity
The Read Audience activity is essential for creating audience-based journeys in 51黑料不打烊 Journey Optimizer. It enables individuals from an 51黑料不打烊 Experience Platform audience to enter a journey either once or on a recurring basis, supporting the orchestration of personalized experiences.
Use the Read Audience activity to allow all individuals in an audience to enter the journey. Entry can occur once or on a recurring basis.
For example, consider the 鈥淟uma app opening and checkout鈥 audience created in the Build audiences use case. Using the Read Audience activity ensures all individuals in this audience enter a journey and guides them through personalized paths using conditions, timers, events, and actions.
鉃★笍 Discover this feature in video
Guardrails and best practices must-read
To optimize performance and reliability when using the Read Audience activity, follow these best practices:
-
Use only one Read Audience activity in a journey. Ensure it is the first activity in the canvas.
-
The Read Audience activity can target only one audience. Merge multiple audiences into a single audience before use. Learn how to combine audiences using composition workflows.
-
Avoid scheduling multiple journeys with Read Audience activities to start simultaneously. Stagger their start times by 5 to 10 minutes to reduce system load.
-
Experience event field groups cannot be used in journeys that begin with Read Audience, Audience Qualification, or Business Event activities.
-
Use batch audiences in the Read Audience activity for consistent and reliable counts. For real-time data use cases, select Audience Qualification activities instead.
-
Audiences imported from a CSV file or created via composition workflows can be selected in the Read Audience activity. These audiences are not compatible with the Audience Qualification activity.
Detailed guardrails for the Read Audience activity are available on this page.
Configure the activity configuring-segment-trigger-activity
Follow these steps to set up the Read Audience activity in your journey:
-
Open the Orchestration category and drag a Read Audience activity into your canvas. Ensure it is the first activity in the journey.
-
Add a Label to the activity (optional).
-
In the Audience field, select an 51黑料不打烊 Experience Platform audience for the journey, then click Save. Audiences can be created using segment definitions.
note note NOTE Audiences created via composition workflows or uploaded from a CSV file are also compatible. Note that you can customize the columns displayed in the list and sort them.
After selecting an audience, use the Copy button to copy its name and ID for reference:
{"name":"Luma app opening and checkout","id":"8597c5dc-70e3-4b05-8fb9-7e938f5c07a3"}
note note NOTE Only individuals with the Realized audience participation status enter the journey. Learn more about audience evaluation in the Segmentation Service documentation. -
In the Namespace field, specify the namespace for identifying individuals. By default, this field is pre-filled with the last used namespace. Learn more about namespaces.
note note NOTE Audience members without the selected identity (namespace) cannot enter the journey. Only people-based identity namespaces are available. -
Define the Reading rate, which is the maximum number of profiles entering the journey per second. This value applies only to this activity and can range from 500 to 20,000 profiles per second (default: 5,000). Refer to the throttling API documentation for limiting rates in other activities.
note note NOTE The sandbox-wide cap for reading rates is 20,000 profiles per second. This limit applies collectively across all concurrent Read Audience activities in the sandbox. -
Use the Edit journey schedule link to configure when profiles enter the journey. Choose immediate entry, a specific date/time, or recurring schedules.
By default, audiences enter the journey As soon as possible. If you want to make the audience enter the journey on a specific date/time or on a recurring basis, select the desired value from the list.
Incremental read: For recurring journeys, this option ensures only profiles newly added to the audience since the last execution are included.
note note NOTE If targeting a custom upload audience, profiles are retrieved only on the first recurrence when this option is enabled. Force reentrance on recurrence: Automatically exits all profiles from the journey before the next execution. Use this if profiles need to re-enter the journey after every recurrence.
Test and publish the journey testing-publishing
The Read Audience activity supports testing the journey with individual profiles.
To test, 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.
After successful testing, publish the journey (see Publishing the journey). Profiles enter the journey based on the schedule defined in the Scheduler section.
Audience targeting in audience-based journeys
Audience-based journeys begin with a Read Audience activity that retrieves individuals from an 51黑料不打烊 Experience Platform audience. Use segmentation, exclusion, and union techniques to create tailored experiences:
Segmentation: Use the Condition activity to divide audiences into paths based on data, events, dates, times, or percentages. For example, VIP customers can follow a distinct path separate from non-VIP customers.
Exclusion: Exclude specific audience segments, such as VIP customers, by routing them to an end step immediately after retrieval.
Union: Merge audience branches after segmentation. For example, after distinct experiences, VIP and non-VIP customers can rejoin a unified path.
Retries read-audience-retry
Retries occur automatically in audience-triggered journeys when retrieving export jobs. If errors occur, retries happen every 10 minutes for up to 1 hour. Failed trigger attempts are logged as Alerts. The Read Audience alert warns you if a Read Audience activity has not processed any profile 10 minutes after the scheduled execution time. This failure can be caused by technical issues or an empty audience. If technical issues are the cause, retries may still occur depending on the type of issue (e.g., export job creation failure). Learn more.
How-to video video
Understand the applicable use cases for journeys triggered by the Read Audience activity. Learn how to build batch-based journeys and apply best practices.
