ComposableStack.AI CDP
Back to agent
Conceptconcept.activation-tax

Activation Tax

The vendor-imposed structural cost of moving data out of a packaged CDP to external systems — expressed as byte export quotas, concurrent activation limits, audience slot ceilings, and ecosystem-lock incentives. Distinct from infrastructure egress costs (which scale predictably with volume), the activation tax is an architectural constraint enforced by commercial product decisions. High activation tax correlates with low data liquidity in the external direction; the `pattern.aep-as-edge-node` and composable CDP architectures are the primary structural mitigations.

confidence 75%v1reviewed May 11, 2026data-liquidity, packaged-cdp, export-quotas, activation, vendor-constraint, composable-cdp, architectural-decision

Activation Tax

The activation tax is the structural penalty a packaged CDP imposes on data that needs to leave its ecosystem — through profiles exported to an external CDW, audiences pushed to third-party destinations, or profile attributes read by non-CDP activation tools. Unlike infrastructure egress costs (which are distance-based, volume-linear, and predictable), the activation tax is vendor-enforced through the product architecture and cannot be reduced by engineering optimization.

Three manifestations in the current KG:

  1. Byte quotas on export paths: AEP limits first-gen profile data to 500 KB/profile/year via the Data Access API (constraint.aep-first-gen-export-500kb). Second-generation data via the same path is capped at 200 KB/profile/year — more restrictive, not less (constraint.aep-second-gen-data-access-api-200kb). A richly enriched AEP second-gen profile (behavioral sequences, AI-derived scores, cross-channel history) can exhaust this budget before a meaningful CDW export is complete.

  2. Audience slot ceilings: AEP limits external audience activations to 20 per destination instance (constraint.aep-activation-external-audience-limit-20). Organizations with more than 20 simultaneous CDW-computed segments pushing to a single downstream channel face a hard ceiling that forces prioritization or additional destination instance procurement.

  3. Ecosystem-lock incentives: The same second-gen data subject to a 200 KB agnostic-export limit earns a 1500 KB quota (7.5× higher) when routed through AEP's Destination SDK framework (constraint.aep-second-gen-export-1500kb). This differential pricing creates a strong economic incentive to remain within the AEP activation ecosystem — a structural mechanism for vendor lock-in enforced through the entitlement structure, not through technical inability to export.

Relationship to concept.data-liquidity: Data liquidity is the broader principle — the freedom for data to move where needed across a stack. The activation tax is the specific mechanism by which packaged CDPs constrain that liquidity at the egress boundary. A high activation tax is the leading vendor-imposed cause of low data liquidity for organizations that have chosen a packaged CDP as their primary profile store.

Architectural significance: The activation tax is a primary input to the packaged-vs.-composable evaluation. Organizations that have invested in AEP second-gen profile enrichment and also need CDW-native analytics or composable activation will encounter the activation tax at scale. The pattern.aep-as-edge-node is the canonical architectural mitigation: use the CDW as the canonical profile store; position the packaged CDP as a downstream activation-only edge node rather than the profile source of truth.

Note on scope: "Activation tax" is this KG's analytical label for a cluster of documented vendor constraints — it is not a term used in Gartner or Forrester analyst reports. It is grounded in specific, independently sourced product constraints, not in analyst literature.

Sources

Related

This node →

  • refined-byconcept.data-liquidity— Activation tax is the vendor-imposed mechanism through which packaged CDPs constrain data liquidity at the egress boundary. Activation-tax refines data-liquidity by naming the specific commercial enforcement mechanism.

← Referenced by

  • evidence-forconstraint.aep-first-gen-export-500kb— 500 KB/profile/year Data Access API limit for first-gen AEP data is a direct quantitative manifestation of the activation tax.
  • evidence-forconstraint.aep-second-gen-data-access-api-200kb— 200 KB/profile/year limit for second-gen data via agnostic export path — more restrictive than first-gen — is the sharpest instance of the activation tax: investment in richer second-gen profiles paradoxically tightens the export ceiling.
  • evidence-forconstraint.aep-activation-external-audience-limit-20— 20 external-audience slot ceiling per destination instance is the activation-tax applied to segment depth rather than data volume.
  • addressespattern.aep-as-edge-node— The AEP-as-edge-node pattern — positioning CDW as canonical profile store with AEP as downstream activation-only edge node — is the structural mitigation for the activation tax: data-intensive work remains in the unconstrained CDW, and only pre-computed activation signals transit the AEP quota boundary.