For a step by step guide to setting up the Web SDK with tags and sending data to the solutions please see our Implement Adobe Experience Cloud with Web SDK tutorial.
This product is constantly evolving and growing to support more and more use cases. To keep up with the latest and see what we currently support, see the supported use cases page.
Adobe Experience Platform Web SDK is part of the collection that makes up the Adobe Experience Edge. Experience Edge consists of the following technologies:
The Adobe Experience Edge is a new framework for low-latency data collection, pluggable computing and rapid data activation across all addressable channels.
adobedc.net) and receives a single payload back for data and experience delivery.
On the server-side, a unified edge gateway and a common platform services framework makes it easy to plug-in and deploy new capabilities into this real-time computing environment. This architecture:
A single consolidated edge system allows customers to manage their advertising, marketing or personalization campaigns across all channels as an integrated experience. It allows Adobe to deliver services with lower total cost of ownership for customers. It also helps increase the speed of product innovation by making the real-time edge pluggable and allowing Adobe and its customers to more rapidly add new capabilities and customer-defined logic to that real time system.
The following video gives an overview of the Adobe Experience Platform Web SDK and Adobe Experience Platform Edge Network.
The Web SDK is not just a wrapper around existing libraries. It is a completely new library, written from the ground up to incorporate functionalities of existing libraries. Its purpose is to end challenges with tags having to fire in the right order, inconsistency with library versioning challenges, and better dependency management. It is a new way to implement the Experience Cloud and it is open source.
The Web SDK replaces the following SDKs:
In addition to a new library, there is a new endpoint that streamlines the HTTP requests to Adobe solutions. Before, Visitor.js sent a blocking call to the visitor ID service, then AT.js sent a call to Adobe Target, DIL.js sent a call to Adobe Audience Manager, and finally AppMeasurement.js sent a call to Adobe Analytics. This new library and endpoint can retrieve an ID, fetch a Target experience, send data to Audience Manager, and pass the data to Adobe Experience Platform in a single call.
The following video demonstrates Adobe Experience Platform Web SDK and Adobe Experience Platform Edge Network in action. The video example uses a single call to Adobe which sends data to Experience Platform, Analytics, Audience Manager, and Target.
To simplify your migration from any of the existing libraries to Web SDK, Adobe offers a streamlined upgrade path, allowing you to migrate each individual page of your website to Web SDK, without the need of migrating your entire website at once.
This means you can use Web SDK on a page and leave the existing libraries on the other pages, until you can migrate them as well.
Before migrating pages that use at.js to Web SDK, make sure to enable the following Web SDK configuration options. This ensures the visitor profile is kept while navigating from pages with at.js to pages using Web SDK.
The following Target features are not supported when migrating from at.js to Web SDK:
After migrating from at.js to Web SDK, you should remove the
targetMigrationEnabled option from your configuration.