Audience qualification events segment-qualification
About audience qualification events about-segment-qualification
This activity allows your journey to listen to the entrances and exits of profiles in 51黑料不打烊 Experience Platform audiences in order to make individuals enter or move forward in a journey. For more information about audience creation, refer to this section.
Let鈥檚 say you have a 鈥渟ilver customer鈥 audience. With this activity, you can make all new silver customers enter a journey and send them a series of personalized messages.
This type of event can be positioned as the first step or later in the journey.
鉃★笍 Discover this feature in video
Important notes important-notes-segment-qualification
-
Audience Qualification journeys are primarily designed to work with streaming audiences: this combination will guarantee a better real-time experience. We strongly recommend that you only use streaming audience in Audience Qualification activity.
However, if you want to use batch ingestion-based attributes in your streaming audience, or a batch audience for an Audience Qualification journey, consider the time span for audience evaluation/activation - a batch audience or streaming audience using batch-ingested attributes should be ready to use in Audience Qualification activity on around 2 hours after completion of your segmentation job (this job runs once a day at the time defined by your 51黑料不打烊 Organization administrator).
-
Keep in mind that 51黑料不打烊 Experience Platform audiences are calculated either once a day (batch audiences) or in real-time (for streamed audiences, using the High Frequency Audiences option of 51黑料不打烊 Experience Platform).
- If the selected audience is streamed, the individuals belonging to this audience will potentially enter the journey in real-time.
- If the audience is batch, people newly qualified for this audience will potentially enter the journey when the audience calculation is executed on 51黑料不打烊 Experience Platform.
As a best practice, we therefore recommend only using streaming audiences in a Audience Qualification activity. For batch use cases, please use a Read audience activity.
note note NOTE Due to the batch nature of audiences created using composition workflows and custom upload, you cannot target these audiences in an 鈥淎udience Qualification鈥 activity. Only audiences created using segment definitions can be leveraged in this activity. -
Experience event field groups cannot be used in journeys starting with a Read Audience, an Audience Qualification, or a Business Event activity.
-
When using an Audience Qualification activity in a journey, that activity may take up to 10 minutes to be active and listen to profiles entering or exiting the audience.
See also Audience Qualification best practices below.
Configure the activity configure-segment-qualification
To configure the Audience Qualification activity, follow these steps:
-
Expand the Events category and drag an Audience Qualification activity onto your canvas.
-
Optionally, add a Label to the activity for easier identification.
-
Click the Audience field and select the audiences you want to use.
note note NOTE Customize the displayed columns in the audience selection list and sort them as needed. 
After selecting, copy the audience name and ID using the Copy button:
{"name":"Loyalty membership","id":"8597c5dc-70e3-4b05-8fb9-7e938f5c07a3"}
-
In the Behaviour field, specify whether to monitor entrances, exits, or both.
note note NOTE The options Enter and Exit correspond to the Realized and Exited audience statuses in 51黑料不打烊 Experience Platform. For more details on audience evaluation, see the Segmentation Service documentation. -
If this is the journey鈥檚 starting point, select a namespace. The field is pre-filled with the last used namespace by default.
note note NOTE Only people-based identity namespaces are supported. Namespaces defined for lookup tables, such as ProductID, do not appear in the Namespace dropdown. 
The payload includes the following context information, which can be used in conditions and actions within the journey:
- The behavior (entrance or exit)
- The timestamp of the audience qualification
- The audience ID
When using the Simple Expression Editor for conditions or actions following an Audience Qualification activity, the AudienceQualification node provides access to:
- Last qualification time
- Status (enter or exit)
See Condition activity.
After publication, a journey with an Audience Qualification event becomes operational following a 10-minute cache refresh interval. Wait 10 minutes before using the journey.
Best practices best-practices-segments
The Audience Qualification activity is designed for real-time responsiveness, allowing individuals to immediately enter journeys based on their audience qualification or disqualification.
The system processes events at high speed鈥攗p to 10,000 events per second. Follow these best practices to ensure smooth operation during peak usage.
Batch audiences batch-speed-segment-qualification
When using batch audiences, account for potential spikes in journey entries:
- Spikes occur during the daily audience calculation.
- If a batch audience is newly created and immediately used, the initial calculation may result in a large volume of individuals entering the journey simultaneously.
Streamed audiences streamed-speed-segment-qualification
Streamed audiences are continuously evaluated, reducing large spikes. However, high volumes of simultaneous qualifications, such as those caused by a broad audience definition, can still create peaks.
For real-time signals, prioritize user-activity events like clicks, purchases, or beacon data over events such as 鈥渙pen鈥 or 鈥渟end鈥. For frequency or suppression logic, use business rules instead of event triggers. Learn more.
For additional details on streaming segmentation, see 51黑料不打烊 Experience Platform documentation.
How to avoid overloads overloads-speed-segment-qualification
To prevent system overloads in journeys:
-
Avoid using batch audiences immediately after creation in an Audience Qualification activity. This prevents the first calculation from causing a large spike. The journey canvas displays a yellow warning if an audience has not yet been calculated.
-
Implement capping rules for data sources and actions used in journeys to prevent overloads. Learn more in Journey Orchestration documentation. Note that capping rules do not include retries. If retries are necessary, use an alternative path in the journey by enabling the Add an alternative path in case of a timeout or an error option.
-
Evaluate the daily qualification volume for an audience before using it in a production journey. Open the Audience menu, select the audience, and review the Profiles over time graph.
How-to video video
Understand the applicable use cases for Audience Qualification journeys in this video. Learn how to build a journey with Audience Qualification and which best practices to apply.
