[5.0.0] - January 19, 2024
New Features
The 5.0.0 release introduces a new primary feature, Advanced Audience Targeting enabled through integration with Optimizely Data Platform (ODP) (#765, #775, #776, #777, #778, #786, #789, #790, #797, #799, #808).
You can use ODP, a high-performance Customer Data Platform (CDP), to easily create complex real-time segments (RTS) using first-party and 50+ third-party data sources out of the box. You can create custom schemas that support the user attributes important for your business, and stitch together user behavior done on different devices to better understand and target your customers for personalized user experiences. ODP can be used as a single source of truth for these segments in any Optimizely or 3rd party tool.
With ODP accounts integrated into Optimizely projects, you can build audiences using segments pre-defined in ODP. The SDK will fetch the segments for given users and make decisions using the segments. For access to ODP audience targeting in your Feature Experimentation account, please contact your Customer Success Manager.
This version includes the following changes:
-
New API added to
OptimizelyUserContext
:-
fetchQualifiedSegments()
: this API will retrieve user segments from the ODP server. The fetched segments will be used for audience evaluation. The fetched data will be stored in the local cache to avoid repeated network delays. -
When an
OptimizelyUserContext
is created, the SDK will automatically send an identify request to the ODP server to facilitate observing user activities.
-
-
New APIs added to
OptimizelyClient
:-
sendOdpEvent()
: customers can build/send arbitrary ODP events that will bind user identifiers and data to user profiles in ODP. -
createUserContext()
with anonymous user IDs: user-contexts can be created without a userId. The SDK will create and use a persistentVUID
specific to a device when userId is not provided.
-
For details, refer to our documentation pages:
Additionally, a handful of major package updates are also included in this release including murmurhash
, uuid
, and others. For more information, check out the Breaking Changes section below. (#892, #762)
Breaking Changes
-
ODPManager
in the SDK is enabled by default. Unless an ODP account is integrated into the Optimizely projects, mostODPManager
functions will be ignored. If needed,ODPManager
can be disabled whenOptimizelyClient
is instantiated. - Updated
murmurhash
dependency to version2.0.1
. - Updated
uuid
dependency to version9.0.1
. - Dropped support for the following browser versions.
- All versions of Microsof Internet Explorer.
- Chrome versions earlier than
102.0
. - Microsoft Edge versions earlier than
84.0
. - Firefox versions earlier than
91.0
. - Opera versions earlier than
76.0
. - Safari versions earlier than
13.0
.
- Dropped support for Node JS versions earlier than
16
.
Changed
- Updated
createUserContext
'suserId
parameter to be optional due to the Browser variation's use of the newvuid
field. Note: The Node variation of the SDK does not use the newvuid
field and you should pass in auserId
when within the context of the Node variant.
https://github.com/optimizely/javascript-sdk/releases/tag/v5.0.0
Article is closed for comments.