The following document states how to use streaming segmentation using the UI. For information on using streaming segmentation using the API, please read the streaming segmentation API guide.
Streaming segmentation on Adobe Experience Platform allows customers to do segmentation in near real-time while focusing on data richness. With streaming segmentation, segment qualification now happens as streaming data lands into Platform, alleviating the need to schedule and run segmentation jobs. With this capability, most segment rules can now be evaluated as the data is passed into Platform, meaning segment membership will be kept up-to-date without running scheduled segmentation jobs.
Streaming segmentation works on all data that was ingested using a streaming source. Data ingested using a batch-based source will be evaluated nightly, even if it qualifies for streaming segmentation.
Additionally, segments evaluated with streaming segmentation may drift between ideal and actual membership if the segment is based off of another segment that is evaluated using batch segmentation. For example, if Segment A is based off of Segment B, and Segment B is evaluated using batch segmentation, since Segment B only updates every 24 hours, Segment A will move further away from the actual data until it re-syncs with the Segment B update.
In order for streaming segmentation to work, you will need to enable scheduled segmentation for the organization. For details on enabling scheduled segmentation, please refer to the streaming segmentation section in the Segmentation user guide.
A query will be automatically evaluated with streaming segmentation if it meets any of the following criteria:
|Single event||Any segment definition that refers to a single incoming event with no time restriction.|
|Single event within a relative time window||Any segment definition that refers to a single incoming event.|
|Single event with a time window||Any segment definition that refers to a single incoming event with a time window.|
|Profile only||Any segment definition that refers to only a profile attribute.|
|Single event with a profile attribute||Any segment definition that refers to a single incoming event, with no time restriction, and one or more profile attributes. Note: The query is immediately evaluated when the event comes. In the case of a profile event, however, it must wait 24 hours to be incorporated.|
|Single event with a profile attribute within a relative time window||Any segment definition that refers to a single incoming event and one or more profile attributes.|
|Segment of segments||Any segment definition that contains one or more batch or streaming segments. Note: If a segment of segments is used, profile disqualification will happen every 24 hours.|
|Multiple events with a profile attribute||Any segment definition that refers to multiple events within the last 24 hours and (optionally) has one or more profile attributes.|
A segment definition will not be enabled for streaming segmentation in the following scenarios:
inSegmentevent is profile only, the segment definition will be enabled for streaming segmentation.
Please note the following guidelines apply when doing streaming segmentation:
|Single event query||There are no limits to the lookback window.|
|Query with event history||
If a segment definition is modified so it no longer meets the criteria for streaming segmentation, the segment definition will automatically switch from “Streaming” to “Batch”.
Additionally, segment unqualification, similarly to segment qualification, happens in real-time. As a result, if an audience no longer qualifies for a segment, it will be immediately unqualified. For example, if the segment definition asks for “All users who bought red shoes in the last three hours”, after three hours, all the profiles that initially qualified for the segment definition will be unqualified.
After creating a streaming-enabled segment, you can view details of that segment.
Specifically, the Total qualified metric is displayed, which shows the total number of qualified audiences, based on batch and streaming evaluations for this segment.
Underneath is a line graph that shows the number of new audiences that were updated in the last 24 hours using the streaming evaluation method. The dropdown can be adjusted to show the last 24 hours, last week, or last 30 days. The New audience updated metric is based on the change in audience size during the selected time range, as evaluated by streaming segmentation. This metric does not include the total qualified audience from the daily segment batch evaluation.
A segment is considered qualified if it goes from having no status to realized or if it goes from exited to realized. A segment is considered unqualified if it goes from realized to exited or from existing to exited.
More information about these statuses can be found in the status table within the segmentation overview.
Additional information about the last segment evaluation can be found by selecting the information bubble next to Total qualified.
For more information about segment definitions, please read the previous section on segment definition details.
This user guide explains how streaming-enabled segment definitions work on Adobe Experience Platform and how to monitor streaming-enabled segments.
To learn more about using the Adobe Experience Platform user interface, please read the Segmentation user guide.
The following section lists frequently asked questions regarding streaming segmentation:
For most instances, streaming segmentation unqualification happens in real-time. However, streaming segments that use segments of segments do not unqualify in real-time, instead unqualifying after 24 hours.
Streaming segmentation works on all data that was ingested using a streaming source. Segments ingested using a batch-based source will be evaluated nightly, even if it qualifies for streaming segmentation. Events streamed into the system with a timestamp older than 24 hours will be processed in the subsequent batch job.
A segment is defined as either batch or streaming segmentation based on a combination of query type and event history duration. A list of which segments will be evaluated as a streaming segment can be found in the streaming segmentation query types section.
Please note that if a segment contains both an
inSegment expression and a direct single-event chain, it cannot qualify for streaming segmentation. If you want to have this segment qualify for streaming segmentation, you should make the direct single-event chain its own segment.
The number of total qualified segments is drawn from the daily segmentation job, which includes audiences that qualify for both batch and streaming segments. This value is shown for both batch and streaming segments.
The number under the “Last X days” only includes audiences that are qualified in streaming segmentation, and only increases if you have streamed data into the system and it counts toward that streaming definition. This value is only shown for streaming segments. As a result, this value may display as 0 for batch segments.
As a result, if you see that the number under “Last X days” is zero, and the line graph is also reporting zero, you have not streamed any profiles into the system that would qualify for that segment.
It takes up to one hour for a segment to be available.