Adobe

Are You Ready For AT.js?

Adobe Target

Adobe Target

I recently attended an excellent webinar “Ask the Experts – Adobe Target New Features” presented by Adobe’s @kimenwarner. During the webinar, Kimen mentioned a very exciting new feature coming to Adobe Target in February 2016: AT.js.
AT.js is the new client library for Adobe Target, replacing the legacy mbox.js. This new client library is currently in beta testing and promises to be more flexible, faster and safer than the current library. Specifically, AT.js offers:

  • Flexibility: Supports standard websites and single page apps
  • FlexibilityCustomize error handling and timeouts
  • Modern Coding: Uses XMLHttpRequest method for all AJAX loading
  • Speed: Doesn’t require blocking calls — can be loaded asynchronously
  • Speed: Avoids document.write() calls
  • Safety: Doesn’t immediately execute JavaScript on errors and timeouts
  • Safety: No longer reloads on timeouts

These new features are especially exciting for those developing single page applications, as it allows marketers to no longer rely on developers to implement personalization and optimization strategies when supporting single page applications, such as those built in AngularJS or ember.js. Single page applications are becoming the new standard for complex, user-friendly application development and are becoming more and more common as companies modernize their legacy applications and migrate desktop apps to web applications.
Additionally, the speed and safety improvements will make Adobe Target more enticing for anyone looking to do personalization; users increasingly expect near-instant page loads, while also expecting a personalized experience.
Of course, all of these new features require some deprecation of some legacy integrations and support. With AT.js, the following will be deprecated:

  • IE7 or older support
  • Legacy SiteCatalyst -> Test&Target Integration
  • Legacy Test&Target -> SiteCatalyst Integration
  • Legacy Adobe Audience Manager -> Test&Target Integration
  • Direct access to internal mbox.js functions

If you are using these integrations, you will need to upgrade to the latest product versions to leverage the new integrations and when migrating you will need to ensure that you are not invoking internal methods. The migration process is a great time to evaluate your current personalization and optimization implementation as well, especially given the speed and platform improvements in AT.js.
Are you ready for AT.JS? I know I am!

Thoughts on “Are You Ready For AT.js?”

  1. Bhemarasetty Satyavani

    Hi,

    If i am upgarding to at.js , how does the server calls look like, to filter is it on ?mbox or ?at

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Dan Klco, Adobe Digital Marketing Technical Director

Dan is a certified Adobe Digital Marketing Technologist, Architect, and Advisor, having led multiple successful digital marketing programs on the Adobe Experience Cloud. He's passionate about solving complex problems and building innovative digital marketing solutions. Dan is a PMC Member of the Apache Sling project, frequent Adobe Beta participant and committer to ACS AEM Commons, allowing a unique insight into the cutting edge of the Adobe Experience Cloud platform.

More from this Author

Follow Us
TwitterLinkedinFacebookYoutubeInstagram