Adobe Implementation Playbook

Implementation learning portfolio · Madhavi T

Adobe Experience Cloud, implemented from kickoff to closure

Follow a real project in order: plan it, build nine tools in dependency order across six industries, then test, launch and hand over. Every step has what to do, what to check, what you must know, interview questions and a slot for your own screenshot.

Build steps
102
Domains per step
6
Interview questions
347
Linked key terms
109

New: What changed (2024–26) lists Adobe's renames, such as AJO surfaces → channel configurations and Segment Builder → Audience Builder.

The project, start to close

1Initiation2Discovery3SOW & plan4Design5Build & configure6QA / UAT7Go-live8Hypercare9Closure

Phase 5 · Build order

The tools in the order a real implementation builds them, from your board's master configuration sequence. Durations are planning estimates from your playbook.

  1. 1Adobe Experience Platform16–26 weeks
  2. 2Adobe Analytics9–15 weeks
  3. 3Adobe Launch (Tags) + Web SDK7–14 weeks
  4. 4Marketo Engage14–21 weeks
  5. 5Real-Time CDP8–13 weeks
  6. 6Adobe Experience Manager (Sites & Assets)18–30 weeks
  7. 7Adobe Target8–14 weeks
  8. 8Adobe Journey Optimizer11–18 weeks
  9. 9Customer Journey Analytics8–15 weeks

How to use this site

  1. Go in order. Read a step, do it in a sandbox (or on paper if you don't have Adobe access), then tick it off. Ticks are saved in this browser.
  2. Read across the domains. Each build page has a tab per industry. Do Travel (SkyLumen Airways) and Retail (Cartwell) first.
  3. Add your screenshots. Every step shows a file name such as screenshots/aep/step-03.png. Save your screenshot with that name in the screenshots folder, upload the site again, and it appears in place of the placeholder.
  4. Prepare for interviews. Answer each step's questions out loud before revealing the model answer, or use the Interview prep page.

How the tools fit together

Customer touchpoints

  • Websitepages served by AEM
  • Mobile appMobile SDK
  • Inbox & devicesemail, SMS, push, in-app
  • Stores & call centrePOS and contact-centre systems
  • Sales teamCRM (Salesforce / Dynamics)

Collection & content

  • AEM Sites & Assetspages, fragments, assets; Tags via Cloud Services
  • Tags + Web / Mobile SDKdata layer → XDM events, consent
  • Edge Network & datastreamsroutes events to AEP, Analytics, Target
  • Source connectorsbatch and streaming from CRM, POS, warehouse
  • Marketo EngageB2B leads, Munchkin, CRM sync

Experience Platform foundation

  • Data lake: schemas & datasetsXDM schemas, datasets, Data Prep
  • Identity Servicenamespaces, identity graph
  • Real-Time Customer Profilemerged profiles, merge policies
  • Query ServiceSQL validation, derived datasets
  • Data governancelabels, policies, consent

Applications

  • Adobe Analyticsfed by the datastream Analytics service
  • Customer Journey Analyticsconnections and data views on AEP datasets
  • Real-Time CDPaudiences and destinations
  • Journey Optimizerjourneys, channels, decisioning
  • Targettests and personalization at the edge

Activation & insight

  • Dashboards & BIWorkspace, Tableau
  • CRM & sales alertscustom actions, Marketo, RTCDP
  • Ad platforms & partnersRTCDP destinations
  • Email · SMS · Push · In-appAJO channel delivery
  • Web & app personalizationTarget and AJO web/code-based

Skills you'll use along the way

Your board's suggested learning order

JSON → AEP → SQL → Tags + JavaScript → Analytics → RTCDP → AJO → CJA → Tableau → Target → AEM → Marketo

The build order above follows how a project is delivered; this learning order is a study path. Both cover the same pages.