Release 4.0.0-beta

4.0.0-beta

May 4th, 2023

New Features

The 4.0.0-beta release introduces a new primary feature, Advanced Audience Targeting enabled through integration with [Optimizely Data Platform (ODP)](https://docs.developers.optimizely.com/optimizely-data-platform/docs (#431,#440,#444,#445,#448).

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 Android SDK

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

Release 3.13.4

3.13.4

March 16th, 2023

• Update README.md and other non-functional code to reflect that this SDK supports both Optimizely Feature Experimentation and Optimizely Full Stack. (#450).

Bug Fixes

• Catch exception from event service and restart the service. (#446).

Release 3.13.3

3.13.3

December 2nd, 2022

Bug Fixes

• Set timeouts to UrlConnections for DatafileClient and EventClient so resources can be released when connection fails (#432).
• Call end of compression inflater/deflater to avoid leaks (#422).

Release 3.13.2

3.13.2

April 7th, 2022

Bug Fixes

• Fix for Android 12 support (PendingIntent flag requirement when built with targetSdkVersion=31+) (#400).
• OptimizelyManager overrides the client name/version (to be included in events) (#410).
• Change default attributes to more meaningful values (#415).

Release 3.13.1

3.13.1

February 3rd, 2022

Bug Fixes

• Move background-watchers file read to a background thread when DatafileRescheduler is invoked.
  This will fix a potential source of ANRs (#401).
• Fix NotificationManager to be thread-safe (add-handler and send-notifications can happen concurrently). See the Optimizely Java SDK release 3.10.1 for details.

Release 3.13.0

3.13.0

January 11th, 2022

New Features

This release updates the SDK to use the Optimizely Java SDK 3.10.0 which includes the following:

• 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.
  • setForcedDecision
  • getForcedDecision
  • removeForcedDecision
  • removeAllForcedDecisions

• For details, refer to our documentation pages: OptimizelyUserContext and Forced Decision methods.

Bug Fixes

• Unschedule background polling worker when interval is not set. This fixes the bug that a polling worker scheduled before is not disabled when Optimizely is initialized again with polling disabled. (#397).

Release 3.12.0

3.12.0

December 9th, 2021

Add reachability checking for datafile-fetch and event-dispatch (#389).

• Add connection constraints to WorkManager requests for datafile-fetch and event-dispatch.
• Fix event-dispatch retry to disabled by default (configurable).

Release 3.11.1

3.11.1

October 4th, 2021

Bug Fixes

• Support long lists of event attributes (> 100) and/or large event batch size (> 100) over the WorkManager Data 10KB size limit (386).

Release 3.11.0

3.11.0

September 16th, 2021

This release updates the SDK to use the Optimizely Java SDK 3.9.0 which includes the following:

New Features:

• Add new public properties to OptimizelyConfig. (#379)
  • sdkKey
  • environmentKey
  • attributes
  • audiences
  • events
  • experimentRules and deliveryRules to OptimizelyFeature
  • audiences to OptimizelyExperiment
• For details, refer to our documentation page: https://docs.developers.optimizely.com/full-stack/v4.0/docs/optimizelyconfig-android.

Deprecated

• OptimizelyFeature.experimentsMap of OptimizelyConfig is deprecated as of this release. Please use OptimizelyFeature.experimentRules and OptimizelyFeature.deliveryRules. (#379)

Bug Fixes

• Fix proguard rules for GSON to one recommended by the GSON repo. (#383)

Release 3.10.2

3.10.2

June 2nd, 2021

Bug Fixes

• Android devices with API-19 and lower are set to use TLS1.2 for both datafile download and event upload (373).