Release 3.3.0

3.3.0

September 26th, 2019

New Features:

• Added non-typed get_feature_variable method (#190) as a more idiomatic approach to getting values of feature variables.
  • Typed get_feature_variable methods will still be available for use.
• Added support for event batching via the event processor.
• Events generated by methods like activate, track, and is_feature_enabled will be held in a queue until the configured batch size is reached, or the configured flush interval has elapsed. Then, they will be batched into a single payload and sent to the event dispatcher.
• To configure event batching, set the batch_size and flush_interval properties in the OptimizelyFactory using OptimizelyFactory.max_event_batch_size(batch_size, logger) and OptimizelyFactory.max_event_flush_interval(flush_interval, logger) and then create OptimizelyFactory.custom_instance.
• Event batching is enabled by default. batch_size defaults to 10. flush_interval defaults to 30000 milliseconds.
• Added the close method representing the process of closing the instance. When close is called, any events waiting to be sent as part of a batched event request will be immediately batched and sent to the event dispatcher.

Deprecated

• EventBuilder was deprecated and now we will be using UserEventFactory and EventFactory to create logEvents.
• LogEvent was deprecated from Activate and Track notifications in favor of explicit LogEvent notification.

Release 3.2.0

3.2.0

July 25th, 2019

New Features:

• Added support for automatic datafile management via HTTPProjectConfigManager:
  • The HTTPProjectConfigManager is an implementation of the Interface
    ProjectConfigManager.
    • Users must first build the HTTPProjectConfigManager with an SDK key and then provide that instance to the Optimizely instance.
    • An initial datafile can be provided to the HTTPProjectConfigManager to bootstrap before making HTTP requests for the hosted datafile.
    • Requests for the datafile are made in a separate thread and are scheduled with fixed delay.
    • Configuration updates can be subscribed to via the NotificationCenter built with the HTTPProjectConfigManager.
    • Optimizely instance must be disposed after the use or HTTPProjectConfigManager must be disposed after the use to release resources.

• The OptimizelyFactory provides basic methods for instantiating the Optimizely SDK with a minimal number of parameters. Check README.md for more details.

Release 3.1.1

3.1.1

May 30th, 2019

Bug Fixes:

• fix(is_feature_enabled): Added rollout experiment key map for onboarding datafile. (#168)

Release 3.1.0

3.1.0

May 3rd, 2019

New Features:

• Introduced Decision notification listener to be able to record:
  • Variation assignments for users activated in an experiment.
  • Feature access for users.
  • Feature variable value for users.

Bug Fixes:

• Feature variable APIs return default variable value when featureEnabled property is false. (#162)

Deprecated:

• Activate notification listener is deprecated as of this release. Recommendation is to use the new Decision notification listener. Activate notification listener will be removed in the next major release.

Release 3.0.0

3.0.0

March 8th, 2019

The 3.0 release improves event tracking and supports additional audience targeting functionality.

New Features:

• Event tracking:
  • The track method now dispatches its conversion event unconditionally, without first determining whether the user is targeted by a known experiment that uses the event. This may increase outbound network traffic.
  • In Optimizely results, conversion events sent by 3.0 SDKs don't explicitly name the experiments and variations that are currently targeted to the user. Instead, conversions are automatically attributed to variations that the user has previously seen, as long as those variations were served via 3.0 SDKs or by other clients capable of automatic attribution, and as long as our backend actually received the impression events for those variations.
  • Altogether, this allows you to track conversion events and attribute them to variations even when you don't know all of a user's attribute values, and even if the user's attribute values or the experiment's configuration have changed such that the user is no longer affected by the experiment. As a result, you may observe an increase in the conversion rate for previously-instrumented events. If that is undesirable, you can reset the results of previously-running experiments after upgrading to the 3.0 SDK.
  • This will also allow you to attribute events to variations from other Optimizely projects in your account, even though those experiments don't appear in the same datafile.
  • Note that for results segmentation in Optimizely results, the user attribute values from one event are automatically applied to all other events in the same session, as long as the events in question were actually received by our backend. This behavior was already in place and is not affected by the 3.0 release.
• Support for all types of attribute values, not just strings.
  • All values are passed through to notification listeners.
  • Strings, booleans, and valid numbers are passed to the event dispatcher and can be used for Optimizely results segmentation. A valid number is a finite Numeric in the inclusive range [-2⁵³, 2⁵³].
  • Strings, booleans, and valid numbers are relevant for audience conditions.
• Support for additional matchers in audience conditions:
  • An exists matcher that passes if the user has a non-null value for the targeted user attribute and fails otherwise.
  • A substring matcher that resolves if the user has a string value for the targeted attribute.
  • gt (greater than) and lt (less than) matchers that resolve if the user has a valid number value for the targeted attribute. A valid number is a finite Numeric in the inclusive range [-2⁵³, 2⁵³].
  • The original (exact) matcher can now be used to target booleans and valid numbers, not just strings.
• Support for A/B tests, feature tests, and feature rollouts whose audiences are combined using "and" and "not" operators, not just the "or" operator.
• Datafile-version compatibility check: The SDK will remain uninitialized (i.e., will gracefully fail to activate experiments and features) if given a datafile version greater than 4.
• Updated Pull Request template and commit message guidelines.

Breaking Changes:

• Conversion events sent by 3.0 SDKs don't explicitly name the experiments and variations that are currently targeted to the user, so these events are unattributed in raw events data export. You must use the new results export to determine the variations to which events have been attributed.
• Previously, notification listeners were only given string-valued user attributes because only strings could be passed into various method calls. That is no longer the case. You may pass non-string attribute values, and if you do, you must update your notification listeners to be able to receive whatever values you pass in.

Bug Fixes:

• Experiments and features can no longer activate when a negatively targeted attribute has a missing, null, or malformed value.
  • Audience conditions (except for the new exists matcher) no longer resolve to false when they fail to find an legitimate value for the targeted user attribute. The result remains null (unknown). Therefore, an audience that negates such a condition (using the "not" operator) can no longer resolve to true unless there is an unrelated branch in the condition tree that itself resolves to true.
• setForcedVariation now treats an empty variation key as invalid and does not reset the variation.
• All methods now validate that user IDs are strings and that experiment keys, feature keys, feature variable keys, and event keys are non-empty strings.

Release 2.1.1

October 11th, 2018

Bug Fixes

• fix(track): Send decisions for all experiments using an event when using track (#120).
• EventBuilder uses the same logger as Project (#122).
• Updating libraries for Ruby SDK (#123).
• fix(datafile-parsing): Prevent newer versions datafile (#124).

Release 2.1.0

2.1.0

July 2nd, 2018

• Introduces support for bot filtering (#106).

Release 2.0.3

June 25th, 2018

Bug Fixes

Fixes #109

Release 2.0.2

See Changelog.

Release 2.0.1

April 25th, 2018

Bug Fixes

Fixes #101