RT-CDP Audiences - Enable aggregation on "Edge" and "Streaming" segments

[#1]

Description - as soon as an Audience is created that is using aggregation e.g., to evaluate a certain number of page views with a given property like a content category, the only working evaluation is "Batch" which is obviously not suitable if you want to do next page personalization based upon a user's content affinity. 

Why is this feature important to you - It seems to be a standard feature in nowadays' CDPs to be able to define some kind of real-time "Badges" based upon user behaviour which can include aggregated values.

This would be exactly that. Audiences on the Edge should support this as well since Batch evaluation is just too slow for next-page personalization.

How would you like the feature to work - Allow aggregation on Edge or Streaming Audiences to be closer to real-time

Current Behaviour - Upon save, an error is shown and none of the available segmentation methods works except for "Batch"

[#2]

Hi, 

The reason your aggregation-based audience can only be evaluated in Batch is due to how Adobe Edge and Streaming Audiences handle real-time processing. Aggregations—like counting page views by content category—require summarizing multiple events over time, which inherently takes longer to compute.

Edge Segmentation is designed for low-latency, next-page or same-session personalization, and it can only evaluate queries that can be resolved very quickly (typically under ~24 hours). Because aggregations are more complex, they can’t be processed in true real-time at the Edge, which is why only Batch evaluation works.

Streaming Segmentation evaluates data continuously and can get closer to real-time, but it still has limits and may not meet the strict instant-decision needs for next-page personalization.

You can refer to Adobe’s documentation here for more details: Edge Segmentation.

In short, this isn’t a bug — it’s a design limitation to balance performance and computation complexity.