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
| Remove | AppMeasurement.js · the Visitor API (ECID) extension · s.t()/s.tl() beacons · doPlugins |
| Add | an XDM schema · a datastream · the Web SDK (alloy) extension · one sendEvent rule |
| Keep | your report suite, classifications, marketing channels, processing rules, segments, all report-suite-side |
✓ 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.