Overview of Adobe Experience Platform integration
summary
Platform claims a single unifying store built on XDM JSON Schema and an identity graph that assembles a real-time customer profile on request. Data lands via batch or stream (streaming writes to profile in <1 minute to profile and micro-batches to the data lake ~15 minutes); batch uses connectors or the batch API. Developers use Adobe IO with JWT, per-tenant sandboxes (~75 today), a single SDK for web and mobile that routes to Adobe or third-party destinations, and profile/entity APIs with governance and privacy hooks.
AI-written summary · about
chapters (12)
- 0:00Introduction and overview
- 3:52Legacy problems in marketing
- 7:04Adobe Experience Platform architecture
- 10:34Developer access and sandboxes
- 14:06XDM system and data modeling
- 16:55Real-time customer profile
- 21:47Data ingress patterns
- 25:35Data egress and use cases
- 29:51Monitoring and events
- 31:55Data collection and SDKs
- 34:00Guardrails and latency
- 35:43Q&A session
related talks
52mKeynote: Headless Today & Tomorrow with Adobe Experience Manager
01h 00mBuilding next gen composable services with Experience Manager
35mWhat is a Digital Experience Platform (DXP)?
39mAdobe Experience Manager as a Headless CMS - Where/When/Why?
18mCh. 2: Innovation
54mAdobe Experience Manager Rock Star: The Headless Challenge
36mCh. 1: Corporate Narrative
21mDedicated Infrastructure in a Multitenant World