Migration › Install & configure the Web SDK extension
Step 06 of 13
46% complete
Install & configure the Web SDK extension
This is where the new library enters your site. In the old world you loaded several scripts, AppMeasurement, the Visitor API, sometimes at.js, each its own download and its own point of failure. The Web SDK collapses all of that into one library,
alloy.js, delivered through your Launch property. Installing the extension and pointing it at your datastream is what connects everything you built server-side back to the browser. From here on, one library speaks for Analytics, identity, and, later, personalization.What to do
1
Where Tags › [property] › Extensions › Catalog › Adobe Experience Platform Web SDK › Install
2
Do In Datastreams, bind each Datastream ID to its matching Tags environment (Dev / Staging / Production).
3
Do Set Edge Domain to your first-party CNAME (e.g.
data.example.com) once provisioned.⚠ Common mistake
Leaving the old Experience Cloud ID Service extension installed alongside the Web SDK. They both try to own identity and collide. You'll retire it at decommission, just never let both run on the same page.
✓ You should see
The Web SDK under Installed Extensions, with datastream IDs bound per environment.