Cloud SDK release notes

Version: 0.3

events package

The following table contains release notes for the Cloud SDK events package:

Version

Release notes

0.3.1

The Cloud SDK now stores a new cookie named sc_{SitecoreEdgeContextId}_personalize in the web browser. This cookie persists the guest ID between sessions.

0.3.0

We simplified the eventData object and updated function signatures so that the order of function parameters is consistent across packages.

Changes to eventData:

  • The channel and currency attributes used to be required. They are now optional.

  • The extensionData object used to be separate from the eventData object. It is now part of eventData.

  • In the event and the addToEventQueue functions, the type parameter used to define the event name. type is now an attribute in eventData.

Changes to function signatures:

  • eventData is now the last parameter in server-side functions because it's optional in some cases.

  • request is now the first parameter in server-side functions, followed by response, if available.

0.2.4

Bug fixes and performance improvements.

0.2.3

Bug fixes and performance improvements.

0.2.2

The event queue functions are now asynchronous.

0.1.3

You can now track site visitors' behavior by capturing VIEW, IDENTITY, FORM, and custom events in real time.

personalize package

The following table contains release notes for the Cloud SDK personalize package:

Version

Release notes

0.3.1

The Cloud SDK now stores a new cookie named sc_{SitecoreEdgeContextId}_personalize in the web browser. This cookie persists the guest ID between sessions.

personalizationData now accepts the pageVariantIds parameter. This is an array of strings representing IDs of personalized page variants.

0.3.0

We updated function signatures so that the order of function parameters is consistent across packages:

  • personalizationData is now the last parameter in server-side functions. This way, the order of function parameters is consistent with that in the events package.

  • request is now the first parameter in server-side functions, followed by response, if available.

0.2.4

The payload of the personalize function now includes UTM parameters from the URL of the webpage where the function runs.

0.2.3

Bug fixes and performance improvements.

0.2.2

Bug fixes and performance improvements.

0.1.3

You can now show personalized content to site visitors.

Do you have some feedback for us?

If you have suggestions for improving this article,