Release 3.6.1

3.6.1

November 19th, 2020

Bug Fixes

• Added "enabled" field to decision metadata structure. #217

Release 3.6.0

3.6.0

November 2nd, 2020

New Features

• Added support for upcoming application-controlled introduction of tracking for non-experiment Flag decisions. #215

Release 3.5.0

3.5.0

October 1st, 2020

New Features:

• Version targeting using semantic version syntax. #213
• Datafile accessor API added to access current config as a JSON string. #211

Release 3.4.0

3.4.0

July 8th, 2020

New Features:

• Introduced 2 APIs to interact with feature variables:
  • getFeatureVariableJSON allows you to get value for JSON variables related to a feature.
  • getAllFeatureVariables gets values for all variables under a feature.
• Added support for fetching authenticated datafiles. HTTPProjectConfigManager now accepts datafileAccessToken to be able to fetch datafiles belonging to secure environments.

Bug Fixes:

• Adjusted log level for audience evaluation logs. (#198)

Release 3.3.1

3.3.1

May 29th, 2020

Bug Fixes:

• This release adds an SDK key param to Optimizely constructor. The user can now create an Optimizely instance only using an SDK key. Previously the user was required to create a HTTPProjectConfigManager, and pass it as a config manager in the constructor. (#189, #193)

Release 3.3.0

3.3.0

January 27th, 2020

New Features:

• Added a new API to get project configuration static data.
  • Call getOptimizelyConfig() to get a snapshot of project configuration static data.
  • It returns an OptimizelyConfig instance which includes a datafile revision number, all experiments, and feature flags mapped by their key values.
  • For more details, refer to our documentation page: https://docs.developers.optimizely.com/full-stack/docs/optimizelyconfig-php.

Release 3.2.0

3.2.0

August 28th, 2019

New Features:

• Added support for datafile management via HTTPProjectConfigManager:
  • The HTTPProjectConfigManager is an implementation of the ProjectConfigManagerInterface.
  • Users will have to initialize and pass in the config manager to be able to use it:

  $configManager = new HTTPProjectConfigManager(<<SDK_KEY>>);
  $optimizely = new Optimizely(<<DATAFILE>>, null, null, null, false, null, $configManager);  
  

  • The fetch method allows you to refresh the config. In order to update the config, you can do something like:

  $configManager->fetch();
  

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. (#159)

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.1

3.0.1

April 19th, 2019

Security Fix:

• Removed CurlEventDispatcher. (#168)
  • ID: opt-2019-0001
  • Overall CVSSv3: 6.0
  • Optimizely Severity: High

Release 3.0.0

3.0.0

March 6th, 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 float or int 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 float or int 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.
  • We're also renaming the clearNotifications and cleanAllNotifications methods. They're now called clearNotificationListeners and clearAllNotificationListeners, respectively. The original methods are now deprecated and will be dropped in a future release. (#120)

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.
• 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.
• Ignore the user's whitelisted variation if it has been stopped. (#123)