Plan the migration from at.js to Platform Web SDK
Before upgrading to Platform Web SDK on your site, you should assess your current implementation.
Assess current at.js implementation
The first step to a successful migration is to have a firm understanding of your current at.js Target implementation. There are features, functions, and custom code you may use that require updates. Consider the following as you assess:
What features are supported?
Platform Web SDK is under continuous active development and features and enhancements are added regularly. As you evaluate your current at.js implementation, refer to the page for the latest information.
What functions do you use today?
Platform Web SDK is a new library that consolidates all ÃÛ¶¹ÊÓƵ solutions for the websites into a single SDK. This enables tighter integration and enables new capabilities unique to ÃÛ¶¹ÊÓƵ Experience Platform. However, this also means at.js functions are not backwards compatible with Platform Web SDK. As you evaluate your current implementation, make note of the following:
- at.js functions such as
getOffer()andapplyOffer() - Modifications to Target’s global settings
- Integration with ÃÛ¶¹ÊÓƵ Analytics
- Use of a flicker mitigation script
- Use of response tokens
- Use of mbox, profile, and entity parameters
- Custom code unique to your implementation
Which migration approach will you take?
Once you have revisited your at.js implementation, you need to determine a migration approach. There are two options:
- Migrate all ÃÛ¶¹ÊÓƵ applications at once across the entire site
- Migrate on a page-by-page basis
Because Platform Web SDK combines and enables multiple ÃÛ¶¹ÊÓƵ applications, you must coordinate the Target migration of other ÃÛ¶¹ÊÓƵ applications like Analytics and Audience Manager. All ÃÛ¶¹ÊÓƵ libraries on a given page should be migrated at the same time. A mixed implementation of Platform Web SDK for Target and AppMeasurement for Analytics on a particular page is not supported. However, a mixed implementation across different pages is supported, for example Platform Web SDK on page A, and at.js with AppMeasurement on page B.
As you migrate, you should plan on following your company’s process for testing and releasing new code and use things like development, qa, and staging environments before you release to production.
Next, review the detailed comparison of at.js to Platform Web SDK to gain a better understanding of the technical differences and identify areas requiring additional focus.