Most Adobe Analytics tutorials hand you a glossary. This one hands you a sandbox. Write code, fire hits, inspect the wire format, and build the muscle memory of a working implementation engineer.
You will not pass a certification by reading. You will pass it — and become useful on the job — by shipping code. So every module here is built around the same loop.
Each lesson ends with a live editor connected to a faithful mock of Adobe's
s object. You write the implementation, fire the call, and the simulator decodes
the request the same way a network panel or Adobe's debugger would. There is no faking with
placeholder data — what you build is what you'd see on a real site.
Sequenced from first principles to production-grade. Take them in order, or jump straight to the gap in your knowledge.
The Adobe Experience Cloud landscape — what a report suite is, how data collection works end to end, and the words you need to read any documentation.
→ 02Designing a JavaScript data layer that survives developer turnover. CEDDL, Adobe Client Data Layer, custom patterns, and the politics of getting it shipped.
→ 03The library that does the actual work. The s object anatomy, s.t() vs s.tl(), plugins, and the network format you'll be inspecting for the rest of your career.
The deployment surface. Properties, environments, extensions, data elements, and rules — the architecture that makes implementation maintainable.
→ 05The vocabulary of conversion. Allocation, expiration, serialization, merchandising eVars, list variables — and how to choose between them without regret.
→ 06Custom links, download links, exit links. When to whitelist with linkTrackVars, how the three link types are reported, and why void(0) is your friend.
Single-page applications break the page-load assumption. Virtual page views, route listeners, the React/Vue/Angular patterns — and the duplication bugs they create.
→ 08Alloy and the Edge Network. XDM schemas, the new sendEvent shape, and how to migrate from AppMeasurement without losing your historical data.
→ 09Charles, the Network panel, the Experience League debugger, console plugins. The repeatable QA checklist you'll run before every release.
→ 10Processing rules, marketing channels, classifications, VISTA. How the interface lets you reshape data after it's collected — and why you sometimes shouldn't.
→ 11A bridge for the web engineer. AEP Mobile SDK architecture, lifecycle events, and how the same XDM concepts translate to iOS and Android.
→ 12Server-side forwarding, A4T, Customer Journey Analytics, the consent layer, and the disciplined approach to governance that separates seniors from juniors.
→Reading is half the work. The other half lives in the labs — interactive simulators that let you run the same code you would on a real site.
A live s object — write code, call s.t(), watch hits stream into a fake network panel with every parameter decoded.
Design a page-type-aware data layer in a structured form, watch it generate as JSON, then bind variables to it the way Launch would.
Build an event → conditions → actions rule in a graphical editor and fire test pages through it to see which rules execute.
Paste a real Adobe Analytics request URL and have it decoded into a human-readable parameter table — the same way you'll do it in the field.
When you've finished here, these are the documents and books that practising implementation engineers actually keep open in a tab.