Release notes

This document covers the release notes for the Adobe Experience Platform Web SDK.
For the latest release notes on the Web SDK tag extension, see the Web SDK tag extension release notes.

Version 2.12.0 - June 29, 2022

  • Change the requests to the Edge Network to use the cluster cookie location hint as part of the URL. This ensures that users who change their location (e.g. through a VPN or driving with mobile devices, etc) mid session hit the same edge and have the same personalization profile.
  • Stringify configured functions in the getLibraryInfo command response.

Version 2.11.0 - June 13, 2022

New features

  • You can now deliver personalized experiences more accurately, by sharing visitor IDs between mobile apps and mobile web content, and across domains. See the dedicated documentation to learn more.
  • You can now render or execute an array of propositions from Adobe Target into single-page applications, without incrementing the analytics metrics. This reduces reporting errors and increases analytics accuracy. See the dedicated documentation to learn more.
  • Added additional information to the getLibraryInfo command including available commands and the final configuration for the instance.

Fixes and improvements

  • Updated cookie settings to use sameSite="none" and secure flag on HTTPS pages.
  • Fixed an issue where personalized content was not applied correctly when using the eq pseudo selector.
  • Fixed an issue where localTimezoneOffset could fail Experience Platform validation.

Version 2.10.1 - May 3, 2022

  • Fixed an issue where multiple persistent iframes were created for ID syncs and segment destinations.

Version 2.10.0 - April 22, 2022

  • Use a persistent iframe for all ID syncs and segment destinations.
  • Fixed an issue where merged metrics propositions were duplicated in the sendEvent result.

Version 2.9.0 - March 10, 2022

  • Added support for tracking control (default) Adobe Target experiences.
  • Optimized the view-change events for single page applications. The display notification is now included with the view-change event when personalized experiences are rendered.
  • Removed console warning when no eventType is present.
  • Fixed an issue where the propositions property was only returned from a sendEvent command when experiences were requested or retrieved from the cache. The propositions property will now always be defined as an array.
  • Fixed an issue where hidden containers were not shown when there was an error returned from the Adobe Experience Edge.
  • Fixed an issue where the interact events were not being counted in Adobe Target. This was fixed by adding the view name to the XDM at web.webPageDetails.viewName.
  • Fix broken documentation links in console messages.

Version 2.8.0 - January 19, 2022

  • Support shadow DOM selectors for personalization.
  • Renamed personalization event types. (display and click become decisioning.propositionDisplay and decisioning.propositionInteract)
  • Fixed an issue where HTML offers with inline script tags added the script tags twice to the page even though the script was only run once.

Version 2.7.0 - October 26, 2021

  • Expose additional information from Experience Edge in the return value from sendEvent, including inferences and destinations. The format of these properties may change as these features are currently rolling out as part of a Beta. For more information, see Tracking Events.

Version 2.6.4 - September 7, 2021

  • Fixed an issue where set HTML Adobe Target actions applied to the head element were replacing the entire head content. Now set HTML actions applied to the head element are changed to append HTML.

Version 2.6.3 - August 16, 2021

  • Fixed an issue where objects not intended for public use were exposed through the resolved promise from the configure command.

Version 2.6.2 - August 4, 2021

  • Fixed an issue where a warning about the deprecation of result.decisions (provided by the sendEvent command) would be logged to the console even when the result.decisions property wasn’t being accessed. No warning will be logged when accessing the result.decisions property, but the property is still deprecated.

Version 2.6.1 - July 29, 2021

  • Fixed an issue where rendering personalization for a single-page app view that has no personalization content would throw an error and cause the promise returned from the sendEvent command to be rejected.

Version 2.6.0 - July 27, 2021

  • Provides more personalization content in the sendEvent resolved promise, including Adobe Target response tokens. When the sendEvent command is executed, a promise is returned, which is eventually resolved with a result object containing information received from the server. Previously, this result object included a property named decisions. This decisions property has been deprecated. A new property, propositions, has been added. This new property provides customers with access to more personalization content, including response tokens.

Version 2.5.0 - June 2021

  • Added support for redirect personalization offers.
  • Automatically collected viewport widths and heights that are negative values will no longer be sent to the server.
  • When an event is canceled by returning false from an onBeforeEventSend callback, a message is now logged.
  • Fixed an issue where specific pieces of XDM data intended for a single event was included across multiple events.

Version 2.4.0 - March 2021

  • The SDK can now be installed as an npm package.
  • Added support for an out option when configuring default consent, which drops all events until consent is received (the existing pending option queues events and sends them once consent is received).
  • The onBeforeEventSend callback can now be used to prevent an event from being sent.
  • Now uses an XDM schema field group instead of meta.personalization when sending events about personalized content being rendered or clicked.
  • The getIdentity command now returns the edge region ID alongside the identity.
  • Warnings and errors received from the server have been improved and are handled in a more appropriate fashion.
  • Added support for Adobe’s Consent 2.0 standard.
  • Consent preferences, when received, are hashed and stored in local storage for an optimized integration among CMPs, Platform Web SDK, and Platform Edge Network. If you are collecting consent preferences, we now encourage you to call setConsent on every page load.
  • Two monitoring hooks, onCommandResolved and onCommandRejected, have been added.
  • Bug Fix: Personalization interaction notification events would contain duplicate information about the same activity when a user navigated to a new single-page app view, back to the original view, and clicked an element qualifying for conversion.
  • Bug Fix: If the first event sent by the SDK had documentUnloading set to true, sendBeacon would be used to send the event, resulting in an error regarding an identity not being established.

Version 2.3.0 - November 2020

  • Added nonce support to allow for stricter content security policies.
  • Added personalization support for single-page applications.
  • Improved compatibility with other on-page JavaScript code that may be overwriting window.console APIs.
  • Bug Fix: sendBeacon was not being used when documentUnloading was set to true or when link clicks were automatically tracked.
  • Bug Fix: A link wouldn’t be automatically tracked if the anchor element contained HTML content.
  • Bug Fix: Certain browser errors containing a read-only message property were not handled appropriately, resulting in a different error being exposed to the customer.
  • Bug Fix: Running the SDK within an iframe would result in an error if the iframe’s HTML page was from a different subdomain than the parent window’s HTML page.

Version 2.2.0 - October 2020

  • Bug Fix: The Opt-in object was blocking Alloy from making calls when idMigrationEnabled is true.
  • Bug Fix: Make Alloy aware of requests that should return personalization offers to prevent a flickering issue.

Version 2.1.0 - August 2020

  • Remove the syncIdentity command and support passing those IDs in the sendEvent command.
  • Support IAB 2.0 Consent Standard.
  • Support passing additional IDs in the setConsent command.
  • Support overriding the datasetId in the sendEvent command.
  • Support Alloy Monitors (Read more)
  • Pass environment: browser in the implementation details context data.

On this page