AEP architecture: an enterprise reference model

Reference architecture layers

1. Collection — Web SDK, Mobile SDK, server APIs and source connectors.
2. Foundation — XDM schemas, datasets, Identity Service, Real-Time Customer Profile.
3. Intelligence — segmentation, Query Service and analytics in CJA.
4. Activation — Real-Time CDP destinations, Journey Optimizer, Target and partner tools.
5. Governance — sandboxes, roles, labels, policies, consent and monitoring.

Architecture best practices

• Use development and production sandboxes with a promotion process.
• Agree the identity strategy before building schemas.
• Apply least-privilege access and audit changes.
• Design for consent from the start rather than retrofitting it.
• Plan capacity: profile counts, event volumes and audience limits.
• Keep secrets for APIs in a secure vault; never in code or tag managers.

Enterprise integration patterns

Common patterns include CRM-to-AEP batch syncs, event streaming from Kafka or cloud pub/sub into the streaming API, warehouse integration with Snowflake, BigQuery or Databricks, and server-to-server event forwarding. See data engineering for pipeline design.

Who this guide is for

This guide is written for beginners, students and career switchers who want a clear mental model, and for developers, data engineers, implementation specialists, consultants, architects, marketers, agencies and enterprise teams who need practical, step-by-step detail they can apply on real projects.