This activity allows your journey to listen to the entrances and exits of profiles in Adobe Experience Platform segments in order to make individuals enter or move forward in a journey. For more information on segment creation, refer to this section.
Let’s say you have a “silver customer” segment. 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.
Keep in mind that Adobe Experience Platform segments are calculated either once a day (batch segments) or in real-time (streamed segments, using the High Frequency Audiences option of Adobe Experience Platform).
If the selected segment is streamed, the individuals belonging to this segment will potentially enter the journey in real-time. If the segment is batch, people newly qualified for this segment will potentially enter the journey when the segment calculation is executed on Adobe Experience Platform.
Unfold the Events category and drop a Segment Qualification activity into your canvas.
Add a Label to the activity. This step is optional.
Click in the Segment field and select the segments you want to leverage.
Note that you can customize the columns displayed in the list and sort them.
Once the segment is added, the Copy button allows you to copy its name and ID:
In the Behaviour field, choose whether you want to listen to segment entrances, exits or both.
Note that Enter and Exit correspond to the Realized and Exited segment participation statuses from Adobe Experience Platform. For more on how to evaluate a segment, refer to the Segmentation Service documentation.
Select a namespace. This is only needed if the event is positioned as the first step of the journey.
The payload contains the following context information, which you can use in conditions and actions:
When using the expression editor in a condition or action that follows a Segment Qualification activity, you have access to the SegmentQualification node. You can choose between the Last qualification time and the status (enter or exit).
See Condition activity.
A new journey that includes a segment qualification event is operational ten minutes after you have published it. This time interval corresponds to the cache refresh interval of the dedicated service. Therefore, you must wait ten minutes before using this journey.
The Segment Qualification activity enables the immediate entrance in journeys of individuals getting qualified or disqualified from an Adobe Experience Platform segment.
The reception speed of this information is high. Measurements made show a speed of 10 000 events received per seconds. As a result, you should make sure you understand how peaks of entrance might happen, how to avoid them and how to make your journey ready for them.
When using segment qualification for a batch segment, note that a peak of entrance will happen at the time of the daily calculation. The size of the peak will depend on the number of individuals entering (or exiting) the segment daily.
Moreover, if the batch segment is newly created and immediately used in a journey, the first batch of calculation might make a very large number of individuals enter the journey.
When using segment qualification for streamed segments, there is less risk of getting large peaks of entrances/exits due to the continuous evaluation of the segment. Still, if the segment definition leads to making a large volume of customers qualify at the same time, there might be a peak too.
For more information on streaming segmentation, refer to Adobe Experience Platform documentation
Here are a few best practices that will help to avoid overloading systems leveraged in journeys (data sources, custom actions, Message activities).
Do not use, in a Segment Qualification activity, a batch segment immediately after its creation. It will avoid the first calculation peak. Note that there will be a yellow warning in the journey canvas if you’re about to use a segment that has never been calculated.
Put in place a capping rule for data sources and actions used in journeys to avoid overloading them. Learn more in Journey Orchestration documentation. Note that the capping rule has no retry. If you need to retry, you must use an alternative path in the journey by checking the box Add an alternative path in case of a timeout or an error in conditions or actions.
Before using the segment in a production journey, always evaluate first the volume of individuals qualifying for this segment every day. To do so, you can check the Segments menu, open the segment then look at the Profiles over time graph.