at.js version details

Adobe Opt-in support: Adobe Opt-In is a way to simplify Adobe solutions integrations with consent management platforms. For more information about Adobe Opt-in, see Privacy and General Data Protection Regulation (GDPR).

Industry-standard CSP compliant: at.js no longer uses eval() to execute JavaScript.

Client-side analytics logging: Give customers full control on how they want to send analytics data to Adobe Analytics, whether on the client-side or server-side.

For more information, see Client-side Analytics logging.

Send notifications: Allow developers to send notifications when an experience is rendered by their code instead of using applyOffer() or applyOffers().

For more information, see adobe.target.sendNotifications(options).

at.js size reduced by ~24%: The size of at.js is reduced by ~24%. The smaller file size improves page load performance and reduces the time to download at.js on the page.

The details of the at-request-succeeded event contain the redirect flag. This flag can be used to determine if the page will be redirected to a different URL. If you want to know the URL, subscribe to at-content-rendering-redirect. (TNT-29834)

Fixed an issue that caused window.targetGlobalSettings.enabled to fail with a runtime exception if it was set to false. (TNT-29829)

Fixed an issue that caused the page to fail while loading in the Visual Experience Composer (VEC) if using custom code to a fire global mbox request and using body hiding. (TNT-29795)

Added support for screenOrientation, devicePixelRatio, and webGLRenderer. These new Target request parameters are used for iPhone X and other modern device detection. For more information, see Mobile. (TNT-29781)

Fixed an issue where the Adobe Audience Manager (AAM) location hint wasn’t always sent. (TNT-29695)

For browsers that support it, at.js 1.5.0 switches to MutationObserver for selector polling. Versions prior to at.js 1.0.0 used a MutationObserver polyfill, which proved to be problematic. To avoid the polyfill issues, version1.5.0 uses the following pseudo code to decide which scheduling mechanism to use:

if MutationObserver is supported
  scheduler = MutationObserver
else if document is visible
  scheduler = requestAnimationFrame
else
  scheduler = setTimeout

The following new events are available to help in tracing, debugging, and customizing interaction with at.js:

• LIBRARY_LOADED
• REQUEST_START
• CONTENT_RENDERING_START
• CONTENT_RENDERING_NO_OFFERS
• CONTENT_RENDERING_REDIRECT

For more information, see at.js custom events.

You can augment an at.js request with additional parameters that come from data providers. Data providers should be added to window.targetGlobalSettings under the dataProviders key.

For more information, see Data Providers.

at.js requests now use GET, but it will switch to POST when the URL size exceeds 2048 characters. There is a new property named urlSizeLimit where you can increase the size limit if necessary. This change allows Target to align at.js to AppMeasurement, which uses the same technique.

Target now enforces that the mbox key in the adobe.target.applyOffer(options) function is used. This key has been required in the past, but Target now enforces its use to ensure that Target has proper validation and customers are using the function correctly.

at.js has improved event and click tracking functionality. at.js uses navigator.sendBeacon() to send event tracking data and will fallback to synchronous XHR when navigator.sendBeacon() is not supported. This fallback mostly affects Internet Explorer 10 and 11 and some versions of Safari. Safari will add support for navigator.sendBeacon() in the upcoming iOS 11.3 release.

at.js can now render offers even when a page is opened in background tabs. Some Target Customers encountered an issue when requestAnimationFrame() was disabled because of the browser throttling behavior for background tabs.

This release adds many performance improvements, including shorter callstacks when inspecting a Chrome CPU profile.

at.js 1.3.0 no longer supports content delivery on Microsoft Internet Explorer 9. For a list of supported browsers, see Supported Browsers. Going forward, all requests are executed via XMLHttpRequest with CORS support with no JSONP requests. This change greatly improves security.

Redirect offer support for A4T. After you download and install at.js version 0.9.6, you can use redirect offers in activities that use Adobe Analytics as the Reporting Source for Target (A4T). Besides at.js version 0.9.6, there are other minimum requirements your implementation must meet in order to use redirect offers and A4T. For more information and additional important information you should know, see Redirect Offers - A4T FAQ.

Prior to at.js 0.9.6, when the Visitor API was present on the page and the visitorApiTimeout setting was too aggressive, Target could run into a situation when no MCID data was sent in the Target request. This could lead to issues like unstitched hits in Analytics when using A4T.

This behavior has been changed in at.js 0.9.6, even if the visitorApiTimeout is set to say 1 ms, Target will try to collect SDID, tracking servers, and customer IDs data and send those in the Target request.

Added the selectorsPollingTimeout setting. For more information, see targetGlobalSettings().

The format of the response from getOffer() has been changed. For more information, see adobe.target.getOffer(options).

Console logging has been added for unsupported <!DOCTYPE> declarations.

Fixed an issue where Target Classic plugins weren’t being applied correctly when multiple default offers were delivered to a single mbox. (TGT-22664)

Improved cookie-setting for two letter top-level-domains (TLDs) to ensure that the mbox cookie is set correctly for these domains (for example, test.no, autodrives.ca, and so forth).

The algorithm for extracting the top-level domain that should be used when saving cookies has changed in at.js version 0.9.6. Because of this change, cookies cannot be saved to addresses that use IP. Most of the time, IP addresses are used for testing purposes, but as workarounds you can use DNS entries or adjust the hosts file on a local box.

Fixed move and rearrange actions handling when properties are string values instead of integers.

mbox names can now contain special characters, including ampersands ( & ).

For a list of allowable special characters, see at.js Configuration.

Added secureOnly setting that indicates whether at.js should use HTTPS only or be allowed to switch between HTTP and HTTPS based on the page protocol. This is an advanced setting that defaults to False and can be overridden via targetGlobalSettings.

The Legacy Browser Support option is available in at.js version 0.9.3 and earlier. This option was removed in at.js version 0.9.4.

Fixes a whitescreen issue when using VEC offers. Anyone using at.js should upgrade to this new version.

New registerExtension API.

This new API gives developers access to certain jQuery modules used in at.js to develop extensions (aka plugins) for the library. There are a few implications for this change. This impact only those users who are using these features:

• getSettings() API has been removed, but the same functionality is available using registerExtension().

• getTracking() API has been removed, but the same functionality is available using registerExtension().

• Existing extensions (e.g. AngularJS extensions) must be updated to use the registerExtension() approach.

New at.js notification API.

The goal of this notification system is to provide more insight into what at.js is doing on the page and when there are issues. A common issue seen with the VEC is that an IT release changes the page, a VEC selector breaks, and the test stops delivering content correctly. A goal of this notification system is to make this delivery issue known to the page, so developers can access this information, pass it to a system like Adobe Analytics, and alerts can be sent to the business owners that their test broke.

New targetGlobalSettings() API method.

You can override settings in the at.js library, rather than configuring them in the Target Standard/Premium UI or by using REST APIs.