Migrate Target from at.js 2.x to Platform Web SDK

This guide is for experienced Adobe Target implementers to learn how to migrate an at.js implementation to Adobe Experience Platform Web SDK.

Adobe Experience Platform Web SDK is a client-side JavaScript library that allows Adobe Experience Cloud customers to interact with Experience Cloud services through the Adobe Experience Platform Edge Network. This new library combines the capabilities of the separate Adobe application libraries into a single lightweight package that can take full advantage of new Adobe Experience Platform features.

Key benefits

Some of the benefits of the Platform Web SDK compared to the standalone at.js library include:

  • Faster sharing of audiences from Real-Time Customer Data Platform
  • Integrating Target with Journey Optimizer to support Offer Decisioning delivery
  • Ability to use first-party ids to generate the ECID for longer duration visitor identification
  • Consolidation of network calls across Adobe applications
  • A smaller footprint for improved page speed metrics
  • A tighter integration with Adobe Analytics which does not rely on stitching information from separate network calls
  • Additional implementation flexibility for developers

Arguably, the largest benefit to Target customers of migrating is for integration with Real-Time Customer Data Platform. Real-Time CDP offers tremendous audience-building capabilities based on the full range of data ingested into Experience Platform and its Real-time Customer Profile capability. A built-in data governance framework, automates responsible use of that data. Customer AI allows you to easily use machine learning models to construct propensity and churn models whose output can be shared back to Adobe Target. And finally, customers of the optional Healthcare and Privacy & Security Shield addons can use the consent enforcement feature to easily enforce individual customers’ consent preferences. Platform Web SDK is a requirement to use these RTCDP features in your web channel.

Learning objectives

At the end of this tutorial, you will be able to:

  • Understand the Target implementation differences between at.js and Platform Web SDK
  • Set up the initial configuration for Target functionality
  • Upgrade the at.js library to Platform Web SDK
  • Render form-based and visual experience composer activities
  • Pass parameters to Target
  • Track conversion events
  • Enable cross-domain support
  • Update audiences and profile scripts
  • Validate the implementation
  • Debug Target experience delivery


To complete this tutorial, you should first:

Once you are ready, the first step to a successful migration is to learn about the migration process and how at.js and Platform Web SDK differ.

We are committed to helping you be successful with your Target migration from at.js to Web SDK. If you run into obstacles with your migration or feel like there is critical information missing in this guide, please let us know by posting in this Community discussion.