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

Migration › Roll out & decommission

Step 13 of 13
100% complete

Roll out & decommission

With parity proven, you don't flip the whole site at once; you advance like a careful tide, one section at a time, always keeping a way back. Mixed implementation is supported across pages (some on Web SDK, some still on AppMeasurement) but never on the same page, so you migrate section by section, watch each, and only then move on. The final act is decommissioning: turning off the legacy extensions and removing the old scripts until AppMeasurement is gone. Keep your previous Launch library versions, that is your rollback, and you want it documented before you need it, not during an incident.
What to do
1
Do Repoint the Production datastream from the validation RSID to the real production RSID. Keep ECID migration on.
2
Do Promote the Tags library Dev → Staging → Production.
3
Do Roll out page-by-page / section-by-section, never two libraries on the same page[32].
4
Do Decommission per validated section: disable the legacy Adobe Analytics and Experience Cloud ID Service extensions; remove residual AppMeasurement.js / VisitorAPI.js.
10% low-riskmonitor50%100%decommissiondotted = rollback (re-publish the previous library)
Advance like a tide, a section at a time, monitoring each, always one re-publish away from rolling back.
⚠ Common mistake

A big-bang cutover of the entire site at once. When something's off, and something always is, the blast radius is everything, and rollback becomes a frantic scramble instead of a calm re-publish.

Rollback & monitor

Rollback = re-publish the previous Tags library for that section. Watch weeks 1–4: unique visitors (cliff), key conversions, parity versus the retiring legacy data.

✓ Migration complete when

A full reporting cycle (≈ a month) reconciles within threshold, AppMeasurement is fully removed, and downstream consumers confirm their reports are intact.