Three Questions That Reveal Your Packaged CDP's Activation Tax
For: executives-evaluating-cdp
Angle
The activation tax — the vendor-imposed structural ceiling on how much data can exit a packaged CDP — is a named framework in the KG this week for the first time. Unlike infrastructure egress costs (which scale linearly and are predictable), the activation tax is enforced through commercial product architecture: byte export quotas, audience slot ceilings, and ecosystem-lock incentives that make compliant external routing more expensive than staying inside the vendor ecosystem. Most organizations discover this constraint after commitment rather than before. The article's contribution is a three-question self-diagnostic: (1) What percentage of your segment count exceeds the 20 external-audience slot ceiling? (2) How much of your AEP second-gen profile data would survive the 200 KB/profile/year agnostic-export limit? (3) Are your critical activation destinations Destination SDK partners, or are they agnostic? Readers who answer these questions have the data they need to evaluate whether the activation tax is a material constraint for their use case.
Key decision this helps with
How do you measure the activation tax your packaged CDP imposes before it becomes a production incident, and what architectural postures are available when you find it?
Tradeoffs the article will map
- Packaged CDP proprietary activation paths (high quota, ecosystem-locked) vs. agnostic export paths (lower quota, unrestricted destination choice) — the quota differential creates a structural lock-in incentive that compounds over time
- Accepting the activation tax as a cost of packaged CDP operational simplicity vs. mitigating it by adopting pattern.aep-as-edge-node (CDW as canonical profile store, AEP as downstream activation-only edge node)
- Investing in richer second-gen AEP profiles (better ML, more attributes, higher AI score quality) vs. the counterintuitive consequence: richer profiles hit the 200 KB agnostic-export ceiling faster than leaner first-gen profiles hit the 500 KB limit
Open questions / uncertainties
- AEP's activation entitlements and quota tiers are contractually defined and vary by customer agreement — the 500 KB / 200 KB / 1500 KB thresholds documented in KG source nodes are from publicly stated product entitlements, not private contracts; the article should acknowledge that enterprise agreements may differ
- The activation-tax concept is this KG's analytical label — it does not appear in Gartner or Forrester analyst reports; the article should be clear about the conceptual origin while citing the specific product constraints that ground it
Knowledge-graph nodes this draws from
Your feedback
Signed-in feedback feeds the next morning's Marketing Drafter routine. It re-weights the backlog priority and records you as an interested reviewer if you opt in.