Segment qualification events segment-qualification
About segment qualification events about-segment-qualification
This activity allows your journey to listen to the entrances and exits of profiles in ۶Ƶ 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.
-
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 note NOTE 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:
{"name":"Loyalty membership“,”id":"8597c5dc-70e3-4b05-8fb9-7e938f5c07a3"}
-
In the Behaviour field, choose whether you want to listen to segment entrances, exits or both.
note note NOTE Note that Enter and Exit correspond to the Realized and Exited segment participation statuses from ۶Ƶ 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:
- the behavior (entrance, exit)
- the timestamp of qualification
- the segment id
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.
Best practices best-practices-segments
The Segment Qualification activity enables the immediate entrance in journeys of individuals getting qualified or disqualified from an ۶Ƶ 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.
Batch segments batch-speed-segment-qualification
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.
Streamed segments streamed-speed-segment-qualification
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 this page
How to avoid overloads overloads-speed-segment-qualification
Here are a few best practices that will help to avoid overloading systems leveraged in journeys (data sources, custom actions, ۶Ƶ Campaign Standard actions).
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 (refer to this section). 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 section in the ۶Ƶ Experience Platform and look at the graph on the right side.
