Adobe Experience Platform Data Collection
summary
Adobe Experience Platform Collection claims one unified pipeline: a single web/mobile SDK collapses multiple Adobe libraries into AP Web SDK (library 121 KB → 20.8 KB in the demo) and sends one beacon to a globally distributed edge that handles thousands of events per second with low latency. Event forwarding / Launch Server Side lets developers run ES6 code or install extensions on Adobe infrastructure to transform and fan out events to GA, Facebook, webhooks, etc. Developer tools include a scaffolding npm tool, local sandbox and a public hello‑world repo (no license required to start).
AI-written summary · about
chapters (13)
- 0:00Introduction and agenda
- 1:47Four industry trends impacting data collection
- 3:56Old school architecture vulnerabilities
- 5:22New school architecture principles
- 7:51Demo overview and user experience
- 9:37Performance comparison old vs new
- 11:05Launch server side rules and actions
- 12:49Real-time data propagation demo
- 14:35Developer experience introduction
- 15:40Scaffolding tool for extensions
- 17:25Extension sandbox testing
- 22:41Summary and resources
- 24:30Q&A session
related talks
01h 00mBuilding next gen composable services with Experience Manager
54mAdobe Experience Manager Rock Star: The Headless Challenge
52mKeynote: Headless Today & Tomorrow with Adobe Experience Manager
39mAdobe Experience Manager as a Headless CMS - Where/When/Why?
40mBuilding Event Collection SDKs and Data Models
54mFireside Chat with Experience Manager Product Leaders
28mA C
38mSeamless Integration of Experience Manager Assets with Applications