← All projects Discuss the project
Project ·
AEP architecture for an international education platform
Sector: Digital education
Context: an international education platform with several business lines
- Adobe Experience Platform
- Real-Time CDP
- Adobe Journey Optimizer: Decision Management (legacy)
- Web SDK
- Google Tag Manager
- OneTrust
- Query Service
The problem
Several business lines shared users and content but managed their own data and consent. They needed to recognise the same person and personalise offers without mixing permissions across business lines.
What I did
- I designed the XDM model for profiles, events, content and consent across the business lines.
- I defined schemas, datasets, identities and ingestion, separating personalisation data stored in the profile from context needed with each request.
- I implemented Web SDK with the GTM data layer. I checked event ingestion and identity resolution.
- I designed the OneTrust-to-AEP integration after comparing batch and real-time options.
- I configured and tested personalisation with Decision Management, AJO’s legacy offer decisioning capability. For retargeting, I stored recent views in the browser and sent them with the next offer request.
Result
- First personalisation use case deployed to production with AEP and AJO, with its audience activated. Configuration validated in pre-production and production.
- The consent integration had a defined technical design. Final schema validation remained dependent on the corporate model.
Where to go next
How I can help
First production use case →
For turning a data model into a first personalisation use case you can validate and operate.
Understand the decision
Model Decisioning inputs by consumption →
Read how to separate stored profile data from context that only exists during a request.
Other related patterns
Do you have a similar problem?
Tell me what you need to solve and which platforms you use.