ComposableStack.AI CDP
Back to agent
Constraintconstraint.aep-second-gen-export-1500kb

AEP Second-Generation Data Export — 1500 KB / profile / year

AEP allows export of up to 1500 KB of Second-Generation Data per profile per year — but only via pre-built or Destination-SDK destinations, forcing reliance on AEP's ecosystem rather than agnostic reverse-ETL.

confidence 90%v2reviewed May 11, 2026aep, governance, activation-tax, ecosystem-lock, vendor-constraint

AEP Second-Generation Data Export — 1500 KB / profile / year

The rule. "Customer may export an average of up to 1,500 kilobytes of Second-generation Data per Profile per year to pre-built destinations available within Adobe Experience Platform or to custom destinations via custom destination connectors that Customer may build using Adobe's Destination SDK" (source.packaged-vs-composable-md).

Implication. While the limit is 3× higher than first-generation, the constraint is structural: organizations must use AEP's specific Destination framework, not their preferred reverse-ETL or data integration pipelines. This is ecosystem lock-in by quota rather than by API.

Commercial reality. These limits are designed to prevent AEP from being used as a pass-through data lake. Adobe is protecting compute and storage costs. From a customer perspective, this can feel like paying a toll to access their own customer data — particularly for organizations that have already paid the platform license (source.packaged-vs-composable-md).

Composable counterpart. Reverse-ETL tools (Hightouch, Census) and direct CDW-to-destination integrations face no quota beyond raw cost (tradeoff.integration-philosophy).

Sources

Related

This node →

← Referenced by

  • requirespattern.aep-as-edge-node— Pattern exists because of this constraint
  • governed-bycapability.reverse-etl— AEP's Destination framework is the packaged-CDP equivalent of reverse-ETL; it is bounded by the 1500 KB/profile/year second-gen export limit.
  • contrasts-withconstraint.aep-second-gen-data-access-api-200kb— The 200 KB Data Access API limit and the 1500 KB Destination SDK limit both apply to Second-generation AEP data — they are complementary constraints on the same data class via different export paths. Surfacing both clarifies that the 1500 KB figure is not a general second-gen limit but an ecosystem-bound one.