I85PREP
⌘ K
Adobe Analytics Developer Expert study materials
Adobe Analytics Developer Expert study resources

Adobe Analytics Developer Expert: Web SDK and Mobile SDK Implementation

Adobe Analytics Developer Expert · Work through your exam, one topic at a time.

All guide sections

Web SDK and Mobile SDK Implementation

One library, an XDM-shaped payload

Adobe Experience Platform Web SDK replaces the legacy AppMeasurement/Visitor/at.js stack with a single library that sends data to the Edge Network in Experience Data Model (XDM) format. You configure a datastream, map XDM fields to Adobe Analytics variables via the Analytics service in the datastream, and send events with sendEvent. The xdm object carries event data; the data object carries non-XDM payload for other services. Identity is handled by the Experience Cloud ID service built into the SDK. Mobile SDK (Adobe Experience Platform Mobile SDK) follows the same Edge paradigm with extensions for Edge, Analytics, Identity, and Consent, plus lifecycle metrics for app launches and sessions.

Concepts you must know

Understand configure (datastream ID, org ID, edge domain), sendEvent with xdm.eventType and xdm.web.webPageDetails, and the alloy global. Know the Analytics variable mapping in the datastream (context data to eVars/props/events), and that _experience.analytics fields map to Analytics. For mobile, know lifecycle events, the trackState/trackAction equivalents in Edge (sendEvent with eventType), and consent extension behavior. Know that identity sync, consent, and datastream configuration happen before any beacon is sent.

Traps in questions

  • Sending eVars directly in the xdm object instead of mapping context data in the datastream.
  • Forgetting that Web SDK requires a configured datastream; without it, no Analytics data flows.
  • Confusing xdm (schema-bound) with data (free-form) payloads.
  • Assuming legacy s.t() calls coexist cleanly with Web SDK; migration requires deliberate cutover.
  • Missing lifecycle metrics on mobile, so sessions and crashes go unreported.

Rule of thumb

If a value must appear in an Analytics variable, either map it in the datastream or set it in the Analytics context data - never assume the raw XDM path lands in a report.