@braze/web-sdk - npm Package Versions

4.8.0

Changed

• The subscribeToFeatureFlagsUpdates callback will now always be called first with the currently cached feature flags, and when feature flag updates are available.

Fixed

• Fixed the return type for subscribeToContentCardsUpdates().
• Fixed the return type for subscribeToFeatureFlagsUpdates().
• Improved type definitions in Card, InAppMessage and InAppMessageButton classes:
  • Fixed return types for Card.subscribeToClickedEvent() and Card.subscribeToDismissedEvent().
  • Fixed return types for InAppMessage.subscribeToClickedEvent() and InAppMessage.subscribeToDismissedEvent().
  • Fixed return type for InAppMessageButton.subscribeToClickedEvent().
  • Fixed type definition of InAppMessage.extras.

4.7.2

Fixed

• Fixed a regression with the noCookies option which caused some localStorage keys to be persisted in cookie storage.

4.7.1

Fixed

• Improved the type definition of Card.extras.
• Fixed a regression introduced in 4.0.0 where the manageServiceWorkerExternally and disablePushTokenMaintenance initialization options could not work as expected.

4.7.0

Added

• User.setCustomUserAttribute now accepts nested custom attributes and arrays of objects.
  • Adds a merge parameter that specifies whether the value should be merged with the existing value on the backend. If false (default), any existing attribute will be overwritten. If true, existing objects and arrays of objects will be merged. To update an array of objects, follow the guidelines in our public docs.

Fixed

• Fixed an issue where requestPushPermission did not call the deniedCallback if the SDK encountered certain errors when registering push.
• Fixed an issue where requestPushPermission did not log a message if push is not supported on the user's browser.
• Fixed an incorrect typing in subscribeToSdkAuthenticationFailures.

4.6.3

Fixed

• Fixed an issue preventing Feature Flags refreshes when SDK Authentication errors occur.

4.6.2

Changed

• Removed legacy email capture CSS. This is not a breaking change, as all existing web email capture campaigns have been migrated to the new universal email capture type on the Braze backend. This change results in ~1KB size reduction for those using the built-in In-App Message UI.

4.6.1

Fixed

• Improved the type definition of FeatureFlag.properties.

4.6.0

Added

• Added a method braze.logContentCardClick() to log that the user clicked on the given Content Card. This method is equivalent to calling braze.logCardClick() with parameter forContentCards = true.
• Added support for the upcoming Braze Feature Flags product.

Changed

• Improved the check for duplicate in-app messages at display time.

4.5.1

Fixed

• Fixed an issue where sites with globally-scoped svg and img CSS caused certain elements of the built-in UI to display incorrectly.

4.5.0

Added

• Added isControl property to ContentCard base model, to easily determine whether the card is a control card.
• Added isControl property to InAppMessage base model, to easily determine whether the message is a control in-app-message.

Changed

• Improved the reliability of in-app message impression logging in edge cases.