v2.4.0-alpha.0

2.4.0-alpha.0

v2.3.0

2.3.0

v2.2.0

2.2.0

2.1.0

v2.1.0

2.1.0

v1.0.0

1.0.0

v0.2.1

0.2.1

Beta v 0.1.1

v0.1.1

0.1.1

Alpha 8

Release notes:

• Refactor the Request/Event schema:

In order to make the format of the Request is more readable, and to support overriding automatically collected data, we have refactored the Request schema:

When using the event command, you will need to use the xdm option instead of the data option.

More info: Tracking Events - Adobe Experience Platform Web SDK

More details will be added to the public doc soon on how to override the automatically collected data.

• Support idSyncContainerId config.

• Rename stitchID to eventMergeId.

• Support promises within options objects: Read more

• Enforce unique propertyId and imsOrgId across instances.

• Support link tracking.

• Support hashing customer IDs.

• Use beacon API for exit links only.

• Add timestamp to events.

Alpha 7

Release notes:

• Integration with Target.

• Added Personalization actions: appendHtml, prependHtml, replaceHtml....

• Personalization component processing images and script tags.

• Implemented Opt-In: all or nothing, with support to pre-optIn commands queuing. Enable with optInEnabled: true.

• Add new config to suppress errors: suppressErrors.

• Implement Stitch ID.

• Implement setCustomerIDs. (Hashing personal IDs and customer IDs as config coming soon)

• Trigger ID Syncs based on TTL.

• Changed the way to specify a View Start. Instead of type: "viewStart", you need to set a boolean when triggering an event command: viewStart: true.

• Bug fixes and code improvements including: Support responses with multiple payloads with same type, fix cookie proxy (cache), fix util that retrieves top level domain...

Alpha 3

Release notes:

• Rename the debug config to log:

alloy("configure", { ... log: true ... });

• Pass an alloy_log query parameter in the URL to enable logging:

https://www.example.com?alloy_log=true

• Return the request & response bodies in the event command:

alloy("event", {...}).then( ({ requestBody, responseBody ? }) => {...} ); 

• Log Sending request / Receiving response in the console if logging is enabled:

[alloy] Sending network request: {events: Array(1), meta: {…}, identityMap: {…}}
...
[alloy] Received network response: {handle: Array(3), requestId: "6bb9cf07220a"}

• If the configure call fails, don’t show any more errors until it's fixed.

• Support Beacon calls when possible:

https://developer.mozilla.org/en-US/docs/Web/API/Beacon_API/Using_the_Beacon_API

"The Beacon interface schedules an asynchronous and non-blocking request to a web server."