Web SDK Changelog

2.14.0 (2026-09-22)

SDK dialog now takes focus on open. This helps to ensure that assistive technology such as screen readers announce the dialog. When the dialog is closed, focus is returned to the HTML element that had focus when the dialog was first opened.
Added a new update() function. Certain use cases require initializing the SDK before the journeyApplicationToken parameter is available. Previously, init() would be called a second time to provide that parameter once it became available. Now, update() should be used to set that parameter rather than a second init(), as update() is lightweight and streamlined for that use case.

SDK plugins may request a transparent modal backdrop and background, enabling full-window and borderless plugin experiences.
Removed Sentry dependency.

SDK modal now uses the dialog HTML element, which improves focus trapping, screen-reader semantics (aria-label), and keyboard accessibility.
Content outside of the SDK modal is no longer selectable while the dialog is visible. By default, the dialog uses a gray partially-transparent backdrop to indicate this. The backdrop can be made transparent using the customStyle init parameter (customStyle.componentOverride.Dialog.backdrop.background: 'transparent').
New closeOnEscapeKey init parameter. Accepts true or false. When true, the SDK modal is dismissed when the user presses the Esc key.

Fixed frame-ancestors CSP violation error by only loading services when configured.

Added support for an SDK plugin to hide/resize the SDK modal, enabling a more native experience for certain SDK plugins.
New services property on the result from alloy.init(). Plugins may now provide actions through the services property.