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.
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.
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.
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.