Release 3.2.2

[3.2.2] - Aug 21, 2024

Bug fixes

• Multiple instances of the Logger make the log system unconfigurable - bug fix. (#276)

Release 3.2.1

[3.2.1] - Aug 15, 2024

Bug fixes

• clientReady is true even though internal client promise returns success == false bug fix(#273)
• useDecision hook set the update listener on overy render bug fix(#273)
• setForcedDecision does not reflect the changes in optmizely instance and useDecision hook bug fix(#274)

Changed

• Performance improvements in both hooks and client instance(#273, #274)

Release 3.2.0

[3.2.0] - July 10, 2024

New Features

• The new useTrackEvent hook is now available for tracking events within functional components. This hook offers all the existing track event functionalities provided by the SDK. (#268)

Release 3.1.2

Changed

[3.1.2] - July 2, 2024

Changed

• JS SDK bump up for react native polyfill support (#266)

Release 3.1.1

[3.1.1] - May 22, 2024

Bug Fixes

• ODP integration error. (#262)

Release 3.1.0

[3.1.0] - April 9, 2024

Bug Fixes

• Error initializing client. The core client or user promise(s) rejected.
  (#255)
• Unable to determine if feature "{your-feature-key}" is enabled because User ID is not set(#255)

Changed

• Bumped Optimizely JS SDK version in use (#255)
• Resolve dependabot dependency vulnerabilities (#245, #247, #248, #251, #253)
• Add node versions during testing (#249)

Full Changelog: 3.0.1...3.1.0

Release 3.0.1

[3.0.1] - February 27, 2024

Changed

• Updated @optimizely/optimizely-sdk to version 5.0.1 (#242)
• Updated Dependabot alerts (#239, #241)

Full Changelog: 3.0.0...3.0.1

Release 3.0.0

[3.0.0] - January 24, 2024

New Features

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:

• Advanced Audience Targeting

• Client SDK Support

• Initialize React SDK

• Advanced Audience Targeting segment qualification methods

• Send Optimizely Data Platform data using Advanced Audience Targeting

Breaking Changes

• Dropped support for the following browser versions.
  • All versions of Microsoft 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 @optimizely/optimizely-sdk to version 5.0.0 (#230).
• Removed use of deprecated @optimizely/js-sdk-* packages.
• Minor version bumps to dependencies.

Bug Fixes

• Updated OptimizelyProvider to (#229)
  • correctly adhere to optional userId? and user? interface fields, using the DefaultUser to signal to client-side contexts to use the new vuid identifier.
  • correctly use of the correct React lifecyle methods.

Release 3.0.0-beta2

[3.0.0-beta2] - December 26, 2023

Bug fixes

• Tag release correctly during publishing
• Updated datafile variable in README
• AAT gap fill
• Rendering default OptimizelyVariation when not last
• OptimizelyVariation with default and variation props set

Release 3.0.0-beta

[3.0.0-beta] - September 22, 2023

New Features

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:

• Advanced Audience Targeting

• Client SDK Support

• Initialize React SDK

• Advanced Audience Targeting segment qualification methods

• Send Optimizely Data Platform data using Advanced Audience Targeting

Breaking Changes

• 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.
• Updated murmurhash dependency to version 2.0.1.
• Updated uuid dependency to version 8.3.2.
• Dropped support for the following browser versions.
  • All versions of Microsoft 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 14.

Changed

• Updated createUserContext's userId parameter to be optional due to the Browser variation's use of the new vuid field.