"Customers may batch export an average of up to 200 KB of Second-generation Data per Profile per year through the Data Access API or other means within Adobe Experience Platform Activation" (source.helpx-adobe-com.legal-product-descriptions-aep-activation-2026).
Why this is architecturally significant. The counterintuitive finding: for the agnostic export path (Data Access API, non-AEP-ecosystem), second-generation data is more constrained than first-generation. The 1500 KB second-gen limit (constraint.aep-second-gen-export-1500kb) applies exclusively when routing through AEP's Destination SDK framework — it is an AEP-ecosystem premium, not a general second-gen quota.
The practical implication for composable CDP designs: organizations attempting to use the Data Access API to move second-gen profile attributes to an external CDW (Snowflake, BigQuery, Databricks) for downstream composable activation or analytics are limited to 200 KB per profile per year. A highly engaged customer with a rich second-gen profile — behavioral sequence, AI-derived scores, cross-channel event history — may have hundreds of kilobytes of second-gen attributes. At 200 KB, that budget is consumed quickly.
How it relates to constraint.aep-first-gen-export-500kb. Both constraints use the Data Access API as the export mechanism. First-gen (legacy, generally raw event data) has a 500 KB allocation. Second-gen (current, enriched profile attributes and computed scores) has a 200 KB allocation via the same path. The message from AEP's product architecture is consistent: use Destination SDK for second-gen data, not the Data Access API.
Recommended architectural response. The pattern.aep-as-edge-node pattern (position CDW as the canonical data store, use AEP only for Destination SDK activations) is the direct structural mitigation. Organizations investing heavily in AEP second-gen profile enrichment who also want CDW-native analytics and composable activation should accept the Destination SDK constraint or adopt the edge-node pattern.
Confidence note: Source is a search snippet from the helpx.adobe.com product description page (403-blocked for direct fetch). The source node source.helpx-adobe-com.legal-product-descriptions-aep-activation-2026 was created today from the snippet. Confidence will rise to ≥0.90 when the primary URL becomes accessible. The 200 KB/profile/year claim is internally consistent with the known AEP quota architecture (agnostic export is more restricted than ecosystem export) and was cross-verified against the phrasing of the first-gen and second-gen Destination SDK limits in existing constraint nodes.