Home AppMeasurement Web SDK · Migration Guide Created by Amit G Dusane

Migration › Understand what's changing

Step 01 of 13
8% complete

Understand what's changing

The whole migration rests on one shift: where the work happens. For years AppMeasurement lived in the visitor's browser; it gathered your eVars and events, assembled the hit, and fired it off, all on the user's device, every page load. The Web SDK moves that work off the browser and onto Adobe's Edge Network. The browser now sends one clean, structured message; the Edge does the assembling and routes it to Analytics, and later to CJA, Target, and beyond.[1][5] Nothing else in this guide makes sense until that picture is fixed in your mind: you are not swapping one script for another, you are moving the kitchen out of the house.
What's changing
At a glance, what this migration does
RemoveAppMeasurement.js · the Visitor API (ECID) extension · s.t()/s.tl() beacons · doPlugins
Addan XDM schema · a datastream · the Web SDK (alloy) extension · one sendEvent rule
Keepyour report suite, classifications, marketing channels, processing rules, segments, all report-suite-side
Browser alloy.js sends one message /ee/ your domain EDGE NETWORK 1 Assemble the hit 2 Enrich (geo, UA) 3 Identify (ECID) the kitchen, off the browser Adobe Analytics today Target later CJA / AEP later
One structured message leaves the browser; the Edge assembles, enriches and identifies it, then fans it out, Analytics today, the rest when you light them up. The cooking moved off the device.
✓ Ready when

You can explain, in one sentence, that data is now assembled at the Edge rather than in the browser. Open a "Why?" above for the full picture, then move on.