Batch evaluation re-processes the entire profile store on a fixed schedule, allowing look-back logic such as “purchased in the last 30 days AND no promotional-email engagement.” This historical, cross-channel requirement exceeds Edge’s in-session scope and streaming’s event-triggered scope, so batch segmentation is the appropriate approach.

A. Edge segments are limited to current session or very recent events; they can’t evaluate 30-day histories or “no-event” conditions.

C. Streaming evaluates only when a new event arrives; cannot guarantee detection of the absence of an email event across 30 days.

D. Manual export ignores Real-Time CDP’s built-in segmentation and removes automation and governance benefits.

1. Adobe Experience Platform Segmentation Service – “Segmentation evaluation methods: Batch segmentation is ideal for historical data such as purchases over the last 30 days.” (Docs › Segmentation › Home, 2024-03-14)

2. Segmentation Best Practices – “Use batch segments for larger look-back windows and complex criteria involving absence of events.” (Experience League, Best-Practices section, para. 3)

3. Edge Segmentation Overview – “Edge segments are optimized for in-session evaluation of recent events only.” (Docs › Segmentation › Edge › Overview, Limitations list)