at.js version 2.11.6 (September 29, 2024)
- Fixed an issue that prevented Target from operating correctly with redirect offers within the Visual Experience Composer (VEC) or Form-Based Experience Composer.
at.js version 2.11.5 (August 14, 2024)
- Implemented caching for cookie read and write operations to reduce the overhead of repeated, costly string parsing and manipulation.
- Implemented the newer URL Search Params API when available, as it is faster than manually parsing and manipulating strings.
at.js version 2.11.4 (January 24, 2024)
- Updated at.js to prevent invalid geo data from being sent to the Delivery API.
at.js version 2.11.3 (November 21, 2023)
- Fixed an issue that prevented response tokens from being sent on
at-content-rendering-failed
events.
at.js version 2.11.2 (October 26, 2023)
- Fixed an issue that caused inconsistencies in response tokens sent on custom events.
at.js version 2.11.1 (October 13, 2023)
- Fixed an issue that caused uncaught errors while a page running at.js is in quirks mode.
at.js version 2.11.0 (October 10, 2023)
- Added support for setting custom Adobe Experience Platform (AEP)
sandboxId
andsandboxName
intargetGlobalSettings
, which is passed to the Delivery API ongetOffer/getOffers
calls. - Shadow DOM fix for chaining
:eq()
in selectors.
at.js version 2.10.3 (September 12, 2023)
- Fixed an issue that incorrectly triggered the
at-content-rendering-succeeded
custom event when no offers are rendered. The correct event,at-content-rendering-no-offers
, is now triggered. - Added
eventToken
andresponseTokens
to error object for theat-content-rendering-failed
custom event.
at.js version 2.10.2 (March 7, 2023)
- Fixed an issue that caused the
trackEvent
function to always return an error.
at.js version 2.10.1 (February 2, 2023)
- Fixed a bug in which activities involving audience rules containing parameters with dots in their names were not returning the expected experience, for on-device decisioning.
- Fixed a bug introduced in at.js 2.6.0 in which at.js was firing a delivery call, even when mboxDisable was enabled.
at.js version 2.10.0 (September 19, 2022)
- Added third-party cookie support.
at.js version 2.9.0 (May 27, 2022)
- Added User Agent Client Hints support.
- Fixed a bug where multiple mbox requests on the same page have different impression IDs.
at.js version 2.8.1 (January 28, 2022)
- Fixed
pageLoad
not being mapped to target-global-mbox in On Device Decisioning (ODD) hybrid execution mode. - Fixed an issue with analytics details for mbox request.
- Upgraded dev dependencies to fix security vulnerabilities.
at.js version 2.8.0 (January 7, 2022)
The Target at.js JavaScript library now collects feature usage and performance telemetry data. Personal data is not collected. Opt-out for this feature is available by setting telemetryEnabled
to false in targetGlobalSettings
. For more information, see telemetryEnabled in targetGlobalSettings.
at.js version 2.7.0 (October 28, 2021)
This release contains the following enhancement:
- Added support for Web Components. This version of at.js is required to create and test personalized experiences and offers on custom elements and on elements inside custom elements. This functionality is included in the Target Standard/Premium 21.10.5 release.
at.js 1.8.3 (September 21, 2021)
This release contains the following changes:
- Removed the
reactor-window
andreactor-document
Adobe Experience Platform Launch modules to ensure that the Platform Launch build functions correctly for customers who havewindow.default
ordocument-default
set. - at.js 1.8.3 now explicitly sets
Samesite=None
andSecure
to ensure that third-party domain cookies are set properly.
at.js 2.6.1 (August 16, 2021)
- Bug fix for “No cached artifact available for hybrid mode” when using on-device decisioning.
at.js 2.6.0 (July 16, 2021)
- Added secure attribute to cookies whenever at.js settings
secureOnly
is set totrue
. - Response tokens are now available when using
triggerView()
. - Fixed an issue related to the
CONTENT_RENDERING_NO_OFFERS
event. Now this event is triggered correctly whenever there is no content returned from Target. - Analytics for Target (A4T) click metrics details are correctly returned when using
prefetch
requests. - UUID generation no longer uses
Math.random()
, but relies onwindow.crypto
. - The
sessionId
cookie expiry is correctly extended on every network call. - The Single Page Application (SPA) view cache initialization is now correctly handled and honors
viewsEnabled
settings. SettingviewsEnabled
to thefalse
value now disables thetriggerView()
function. See Order of operations for initial page load.