@optimizely/optimizely-sdk
Advanced tools
Changelog
5.0.0-beta
May 4, 2023
The 5.0.0-beta 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 persistent VUID
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. (#762)
ODPManager
in the SDK is enabled by default. Unless an ODP account is integrated into the Optimizely projects, most ODPManager
functions will be ignored. If needed, ODPManager
can be disabled when OptimizelyClient
is instantiated.murmurhash
dependency to version 2.0.1
.uuid
dependency to version 8.3.2
.102.0
.84.0
.91.0
.76.0
.13.0
.14
.createUserContext
's userId
parameter to be optional due to the Browser variation's use of the new vuid
field. Note: The Node variation of the SDK does not use the new vuid
field and you should pass in a userId
when within the context of the Node variant.Changelog
[4.9.0] - January 14, 2022
Add a set of new APIs for overriding and managing user-level flag, experiment and delivery rule decisions. These methods can be used for QA and automated testing purposes. They are an extension of the OptimizelyUserContext interface (#705, #727, #729, #730):
For details, refer to our documentation pages: OptimizelyUserContext and Forced Decision methods.
Changelog
[4.8.0] - November 29, 2021
OptimizelyConfig
creation from initialization. The OptimizelyConfig
object is now created on the first call to getOptimizelyConfig
API.json-schema
package version to 0.4.0
to fix a high-severity vulnerability (Prototype Pollution).Changelog
[4.8.0-beta.2] - November 1, 2021
Changelog
[4.8.0-beta] - October 18, 2021
OptimizelyConfig
creation from initialization. The OptimizelyConfig
object is now created on the first call to getOptimizelyConfig
API.Changelog
[4.7.0] - September 15, 2021
OptimizelyConfig
. (#683, #698)
OptimizelyFeature
OptimizelyExperiment
OptimizelyFeature.experimentsMap
of OptimizelyConfig
is deprecated as of this release. Please use OptimizelyFeature.experimentRules
and OptimizelyFeature.deliveryRules
(#698)