Show Menu
TOPICS×

What is Adobe Experience Platform Web SDK

Adobe Experience Platform Web SDK is a client-side JavaScript library that allows customers of the Adobe Experience Cloud to interact with the various services in the Experience Cloud through the Adobe Experience Platform Edge Network. In addition to the JavaScript library, there is a Launch extension to help with your Web SDK configurations.

Experience Edge

Adobe Experience Platform Web SDK is part of the collection that makes up Experience Edge. Experience Edge consists of three technologies:
  • Adobe Experience Platform Web SDK: A JavaScript SDK and Launch extension to dramatically simplify deploying Adobe technologies
  • Adobe Experience Platform Mobile SDK: An extension to the v5 mobile SDK to allow customers to use the new deployment methodology
  • Adobe Experience Platform Edge Network: A global distributed network of servers that enable a new methodology of deploying Adobe products
The Adobe Experience Edge is a new framework for low-latency data collection, pluggable computing and rapid data activation across all addressable channels.
Adobe Experience Edge provides a single consolidated SDK for every channel (JavaScript, Mobile, Server-side), which sends data to a common Adobe domain ( 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:
  • Decreases customer time to value
  • Ends the need for "point" integrations
  • Improves performance compared to the old libraries
  • Decreases costs
  • Increases the speed of innovation
  • Creates sustained competitive advantages for Adobe customers
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.

Video overview

The following video gives an overview of the Adobe Experience Platform Web SDK and Edge Network.

SDKs replaced by Adobe Experience Platform Web SDK

Adobe Experience Platform Web SDK replaces the following SDKs:
  • Visitor.js
  • AppMeasurement.js
  • AT.js
  • DIL.js
This is not just a wrapper around existing libraries. It is a complete rewrite. 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 .
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 the Adobe Experience Platform in a single call.
The following video demonstrates the Adobe Experience Platform Web SDK and Edge Network in action. The video example uses a single call to Adobe which sends data to Experience Platform, Analytics, Audience Manager, and Target.

Getting Started

We highly recommend you check out our getting started guide for a quick tutorial on how to get started using Adobe Launch.
This product is constantly evolving and growing to support more and more use cases. To keep up with the latest, check out our supported use-cases board . We keep this up to date with the use cases we currently support and the ones we are working on to enable you to make the best decisions possible.
  • Use Cases Not Yet Supported: These are use cases that are on our roadmap to be supported in the future.
  • Use Cases In Progress: These are the use cases the team is currently working on completing for release.
  • Supported Use Cases: These are the use cases that are supported and work today.
  • Use Cases We Won't Support: These are the use cases we have made a decision not to support.