Overview
Adobe Analytics implementations succeed when the XDM schema, report suites, and tag governance are planned upfront. Decide whether to use the Web SDK + Experience Platform Edge Network or the older appMeasurement.js, then align launch approvals accordingly.
Implementation Phases
Discovery & Access
- Confirm report suites, virtual report suites, and publishing rights in Adobe Experience Platform Launch or Tags.
- Document XDM or context data schema decisions and which components (eVars, props, events) are reserved for this rollout.
- Capture privacy constraints (IP obfuscation, data retention) that may affect server forwarding or identifiers.
Instrumentation Build
- Select the deployment model: Web SDK with Edge Network or legacy appMeasurement; avoid mixing unless migration is planned.
- Configure the data layer mapping to XDM or context data and bind it to Launch data elements.
- Define rules for page views, link tracking, and custom events; ensure eVar/prop allocation matches reporting needs (visit vs hit).
- Implement identity strategy (ECID vs hashed login IDs) and align opt-out handling with Privacy Service if used.
QA & Launch
- Validate hits in Adobe Experience Platform Debugger or Assurance; confirm report suite IDs and tracking servers are correct.
- Check eVar expirations and merchandising bindings on ecommerce events.
- Plan rollback steps in Launch via library republish or rule disablement.
Deployment Artifacts
- Solution design reference showing eVar/prop/event assignments and XDM mappings.
- Launch/Tags library URLs and publishing flow (dev > stage > prod) with approvers listed.
- Identity strategy doc covering ECID configuration, first-party CNAME usage, and opt-out behaviors.
Linked Runbooks
- Install or Embed the Tag or SDK
- Event Tracking
- Data Layer Setup
- Cross-Domain Tracking
- Server-Side vs Client-Side
Change Log & Owners
- Track who owns the solution design and who publishes Launch libraries for each environment.
- Maintain TODOs for retiring legacy appMeasurement beacons after Web SDK migration.