React SDK for Optimizely Feature Experimentation and Optimizely Full Stack (legacy)
Full Changelog: https://github.com/optimizely/react-sdk/compare/3.0.1...3.1.0
Full Changelog: https://github.com/optimizely/react-sdk/compare/3.0.0...3.0.1
The 3.0.0 release introduces a new primary feature, Advanced Audience Targeting enabled through integration with Optimizely Data Platform (ODP) ( #229, #214, #213, #212, #208, #207, #206, #205, #201, #200, #199)
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 release leverages the Optimizely JavaScript SDK 5+
This version includes the following changes:
New APIs added to ReactSDKClient:
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.
getUserContext(): get the current OptimizelyUserContext object in use at the React SDK level.
getVuid(): provides access to the anonymous client-side visitor ID (VUID) generated by the JS SDK. This ID is used to identify unique visitors in Optimizely Results in the absence of a standard user ID.
sendOdpEvent(): customers can build/send arbitrary ODP events that will bind user identifiers and data to user profiles in ODP.
For details, refer to our documentation pages:
102.0.84.0.91.0.76.0.13.0.16.@optimizely/optimizely-sdk to version 5.0.0 (#230).@optimizely/js-sdk-* packages.OptimizelyProvider to (#229)
userId? and user? interface fields, using the DefaultUser to signal to client-side contexts to use the new vuid identifier.The 3.0.0-beta release introduces a new primary feature, Advanced Audience Targeting enabled through integration with Optimizely Data Platform (ODP) (#214, #213, #212, #208, #207, #206, #205, #201, #200, #199)
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 release leverages the Optimizely JavaScript SDK beta5+
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:
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.enzyme with react testing library to make unit tests work with React 18 (#159).fixed issue #49: Return type of createInstance was OptimizelyReactSDKClient which is the implementation class. Changed it to the ReactSDKClient interface instead (#148).
fixed issue #121:ActivateListenerPayload and TrackListenerPayload types were exported from @optimizely/optimizely-sdk but were missing from @optimizely/react-sdk exports. (#150).
useDecision hook to auto-update and reflect changes when forced decisions are set and removed (#133).