Segmentation eligibility criteria update

Starting on May 20, 2025, three updates will be made that affect segmentation eligibility.

Ruleset ruleset

Any new or edited segment definitions that match the following rulesets will no longer be evaluated using streaming or edge segmentation. Instead, they will be evaluated using batch segmentation.

Time window time-window

In order to evaluate an audience with streaming segmentation, it must be constrained within a 24 hour time window.

Including batch data in streaming audiences include-batch-data

Prior to this update, you could create a streaming audience definition that combined both batch and streaming data sources. However, with the latest update, creating an audience with both batch and streaming data sources will be evaluated using batch segmentation.

If you need to evaluate a segment definition using streaming or edge segmentation that matches the updated ruleset, you need to explicitly create a batch and streaming ruleset and combine them using segment of segments. This batch ruleset must be based on a profile schema.

For example, let’s say you have two audiences, with one audience housing profile schema data and the other housing experience event schema data:

If you want to use the batch component in your streaming audience, you’ll need to make a reference to the batch audience using segment of segments.

So, an example ruleset that would combine the two audiences together would look as follows:

inSegment("e3be6d7f-1727-401f-a41e-c296b45f607a") and
CHAIN(xEvent, timestamp, [C0: WHAT(eventType.equals("commerce.checkouts", false))
WHEN(<= 24 hours before now)])

The resulting audience will be evaluated using streaming segmentation, since it leverages the batch audience’s membership by referring to the batch audience component.

However, if you want to combine two audiences with event data, you cannot just combine the two events. You’ll need to create both audiences, then create another audience that uses inSegment to refer to both of these audiences.

For example, let’s say you have two audiences, with both audiences housing experience event schema data:

In this situation, you’d need to create a third audience as follows:

inSegment("7deb246a-49b4-4687-95f9-6316df049948") and inSegment("9e1646bb-57ff-4309-ba59-17d6c5bab6a1")

Merge policy merge-policy

Any new or edited segment definitions that qualify for streaming or edge segmentation must be on the “Active on Edge” merge policy.

If there is no active merge policy set, you’ll need to configure your merge policy and set it to be active on edge.