ComposableStack.AI CDP
Back to agent
Constraintconstraint.aep-batch-audiences-per-hour-100

AEP Batch Export Throughput — 100 Audiences Per Hour (Performance Guardrail)

Adobe Experience Platform performance guardrail recommending a maximum of 100 audiences per batch export hour across all batch (file-based) destinations. Not system-enforced — AEP does not hard-block above 100 — but throughput degradation is expected when more than 100 audiences are scheduled to export within any single hour. This hourly-rate guardrail governs export throughput density: it limits how many audiences can be simultaneously scheduled to export within any given hour, not the total number of audiences configured across all destinations. Organizations with more than 100 active batch audiences should stagger export schedules to avoid clustering exports in the same hour.

confidence 85%v1reviewed May 28, 2026aep, batch, destinations, file-export, audiences-per-hour, performance-guardrail, throughput, scheduling, rate-limit

AEP Batch Export Throughput — 100 Audiences Per Hour (Performance Guardrail)

What it is. Adobe Experience Platform documents a performance guardrail of 100 audiences per hour across all batch export operations. This is not system-enforced: scheduling more than 100 batch audience exports in the same hour will not hard-block, but export throughput degradation is expected — slower file generation, delayed delivery to cloud-storage destinations.

Scope. Applies globally to the AEP sandbox across all batch (file-based) destinations and all audiences scheduled to export within the same one-hour window.

Architectural implication. For most organizations with 10–50 batch-activated audiences, this limit is not binding even with all exports on the same hourly schedule. For enterprise organizations with 100–300 batch audiences across many file-based destinations (healthcare data extracts, loyalty program exports, large ad-platform file uploads), the hourly rate guardrail requires deliberate export schedule staggering: distributing audience exports across multiple hours (e.g., hour 0, hour 1, hour 2) rather than clustering all exports at 00:00 or the top of every hour.

Relationship to constraint.aep-destinations-per-sandbox-100. The destinations-per-sandbox constraint caps the total number of destination instances at 100 per sandbox (system-enforced). This guardrail caps the export throughput rate at 100 audiences per hour (performance guardrail). Both are relevant to large-scale AEP batch activation planning, but they govern different dimensions: topology (how many destination connections) vs. throughput (how many audiences export per hour).

Where the agent should surface this. When a user describes configuring scheduled batch exports for a large AEP deployment (e.g., "we have 200 audiences exporting to S3 every day"), ask about their export schedule clustering and recommend a spread-hourly approach to stay below the 100-audiences-per-hour throughput guardrail.

Sources

Related

← Referenced by

  • governed-byarchetype.aep-heavy-enterprise-evaluating-composable— OC-079. Enterprise organizations with large batch activation catalogs — potentially 100-300 audiences across file-based destinations — are most likely to hit the 100-audiences-per-hour throughput guardrail when all exports are clustered at the top of the hour. The hourly throughput constraint requires deliberate export schedule staggering at enterprise scale. Discovering this constraint during operational scaling is a common trigger for the composable-augmentation evaluation (Hightouch activation avoids AEP's hourly throughput ceiling by operating at the CDW layer).