AEP Audience Evaluation: Handling Batch Limitations with Frequent Audience Evaluation(FAE)

Problem Statement :

How can we support near real-time or frequent audience evaluation in AEP, when the platform only allows one scheduled batch segmentation run per day and does not support sub-daily automation?

Solution:

In Adobe Experience Platform (AEP), batch segmentation is designed for daily execution (one run per day per sandbox). This becomes a challenge when business requires more frequent audience refresh (hourly or near real-time use cases).

To handle this, AEP provides a combination of on-demand execution, optimization strategies, and alternative approaches.

1. Understand the Core Limitation

• Only 1 automated batch run per day per sandbox
• No hourly or multiple recurring schedules supported
• Schedule timing (default 5:00 AM UTC) can be modified only via API, not UI

👉 This means native batch segmentation cannot meet high-frequency use cases

2. Use Flexible Audience Evaluation (FAE) – On-Demand Runs

To overcome this limitation, AEP provides Flexible Audience Evaluation (FAE).

✅ What FAE does:

• Triggers immediate batch evaluation
• Bypasses waiting for the daily scheduled run

✅ But comes with strict limits:

3. Optimize FAE Usage (Important Strategy)

Since FAE is limited, we must use it efficiently:

• Bundle up to 20 audiences in one FAE job
• Avoid running segments individually
• Reserve FAE for:
  • Critical campaigns
  • Urgent business needs
  • Ad-hoc activations

👉 Not suitable for continuous/hourly automation

4. Best Practice: Move to Streaming Segmentation (Recommended)

For near real-time use cases, the correct approach is:

✅ Use Streaming Segmentation

• Evaluates users as data arrives
• Supports near real-time audience qualification
• No dependency on batch schedules

✅ When to use:

• Frequent updates (hourly / multiple times daily)
• Real-time personalization use cases
• Event-driven targeting

5. Important Considerations

• Streaming audiences must be enabled properly
• If audience is required in downstream systems (like CJA),
  ensure batch evaluation is also enabled (if needed)

Final Recommendation

• Use Batch Segmentation → For daily use cases
• Use FAE → For limited on-demand runs (critical only)
• Use Streaming Segmentation → For real-time or frequent updates