Android-SDK - 4.0.0


January 17th, 2024

New Features

The 4.0.0 release introduces a new primary feature, Advanced Audience Targeting enabled through integration with Optimizely Data Platform (ODP) (#431,#440,#444,#445,#448,#470).

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:

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.
  • minimum Android API level requirements upgraded to 21 or higher.

Bug Fixes

  • support arbitrary client names to be included in logx and odp events. (#459).
  • Added catch block to capture resource not found exception. (#460).
  • Added a proguard rule to suppress warning for java.beans.Transient. Upgraded Java to 11. (#471).
  • Added a proguard rule to keep ODPEvent and added sample codes for ODP. (#456).

Functionality Enhancements

  • Update Github Issue Templates (#461)