Releases: adobe/alloy
Alpha 3
Release notes:
- Rename the
debug
config tolog
:
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 theevent
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."
Alpha 2
Release notes:
-
Remove the
viewStart
command. To signal a view start going forward, set thetype
property toviewStart
when makingevent
calls. -
Created an
Alloy
cookie to be used by all the components in the system. -
Created a Network Gateway concept that wraps the Request Payload, Response and actual logic that makes server calls.
-
Trigger ID Syncs and support hiding or showing the referrer.
-
Renamed the
collectionUrl
config toedgeDomain
. -
Fixed the sandbox errors in the IE browser.
Alpha release
Features included in this Alpha release:
- Support for async loading of the Alloy library
- Support for async API
- Support for multiple instances of Alloy
- Audiences Component: URL & Cookie destinations; removal of dest5 demdex iFrame
- Context Component: collect and send context data
- Data Collector Component:
event
andviewStart
commands - Identity Component: Set ECID in a cookie
- Very simple POC of Personalization Component
- Debug mode: Logs and error handling
Getting started guide: https://launch.gitbook.io/adobe-experience-platform-web-sdk/get-started/getting-started