[5.3.0] - April 8, 2024

Changed

• Refactor: ODP corrections #920 including
  • ODPManager should not be running and scheduling timer if ODP is not integrated to the project (which causes memory leak if one sdk instance is created per request)
  • CreateUserContext should work even when called before the datafile is downloaded and should send the identify ODP events after datafile download completes
  • Other automatic odp events (vuid registration, client initialized) should also be sent after datafile is available and should not be dropped if batching is disabled.
  • [see PR for more]

[5.2.1] - March 25, 2024

Bug fixes

• Fix: empty segments collection is valid (#916)
• Update vulnerable dependencies (#918)

[5.2.0] - March 18, 2024

New Features

• Add persistentCacheProvider option to createInstance to allow providing custom persistent cache implementation in react native (#914)

[5.1.0] - March 1, 2024

New Features

• Add explicit entry points for node, browser and react_native, allowing imports like import optimizelySdk from '@optimizely/optimizely-sdk/node', import optimizelySdk from '@optimizely/optimizely-sdk/browser', import optimizelySdk from '@optimizely/optimizely-sdk/react_native' (#905)

Changed

• Log an error in DatafileManager when datafile fetch fails (#904)

[5.0.1] - February 20, 2024

Bug fixes

• Improved conditional ODP instantiation when odpOptions.disabled: true is used (#902)

Changed

• Updated Dependabot alerts (#896)
• Updated several devDependencies (#898, #900, #901)

[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 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 JavaScript SDK

• OptimizelyUserContext JavaScript SDK

• Advanced Audience Targeting segment qualification methods

• Send Optimizely Data Platform data using Advanced Audience Targeting

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, 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 9.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'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.

[4.10.0] - October 11, 2023

New Features

• Add support for configurable closing event dispatcher, and dispatching events using sendBeacon in the browser on instance close (#876, #874, #873)

[5.0.0-beta5] - September 1, 2023

Changed

• Exported logging related types and values from the package entrypoint (#858)
• Removed /lib directory from the published pacakage (#862)

[5.0.0-beta4] - August 22, 2023

New Features

• Added support for configurable user agent parser for ODP (#854)

Bug fixes

• Fixed typescript compilation failure due to missing types (#856)

[5.0.0-beta3] - August 18, 2023

Bug fixes

• Fixed odp event sending not working for Europe and Asia-Pacific regions (#852)

Changed

• Remove 1 second polling floor to allow datafile polling at any frequency but for intervals under 30 seconds, log a warning (#841).