- Optimizely Feature Experimentation
Follow this article to receive email notifications when new Optimizely Feature Experimentation content is added for 2024.
November
Released Custom Flags Dashboard to all customers.
October
- Released Custom Flags Dashboard to beta.
- Released event properties to open beta. See event properties.
September
- Released Optimizely Reporting for Experimentation, providing you with dashboards and reports that show key metrics such as experiment velocity, conclusive rate, win rate, and uplift.
- Updated the Event Key text field to automatically populate with the Event Name formatted in lowercase, replacing any non-alphanumeric characters with underscores. See Create an event in Optimizely Feature Experimentation using the UI.
August
- Began rolling out Flag Lifecycle Management to customers, which helps you view the state of your experiments and targeted deliveries. See Manage flags and Manage rules.
- Released granular roles and permissions, which gives you fine-grained access control of the entities in your projects.
- Released event properties to beta. Event properties let you filter a created event in Optimizely’s UI based on additional information you have attached to it. When you send events, you can add information about the product or action performed to create a more specific metric when using the event in the experiment results. Contact your Customer Success Manager or sign up for the beta on Optimizely.com. See event properties.
July
Renamed the following Optimizely REST API endpoints to clarify they archive the entities instead of deleting them:
Feature Experimentation REST API enhancements
-
Added variations and metrics to the response for the List Rules endpoint – The
/rules
endpoint now returns high-level information on variations for flag rules and metrics for A/B tests and multi-armed bandits. For example,{ "name": "Repeat Buyers Test", // ... "variations": { "off": { "key": "off", "name": "Off", "percentage_included": 3333, "variation_id": 329457 }, "repeat_buyers_1": { "key": "repeat_buyers_1", "name": "Repeat Buyers 1", "percentage_included": 3333, "variation_id": 373838 }, "repeat_buyers_2": { "key": "repeat_buyers_2", "name": "Repeat Buyers 2", "percentage_included": 3334, "variation_id": 373839 } }, "metrics": [ { "event_id": 27053200523, "scope": "visitor", "aggregator": "unique", "winning_direction": "increasing",
"display_title": "addToCart" }, { "scope": "visitor", "aggregator": "sum", "winning_direction": "increasing", "display_title": "Overall Revenue" } ]
} - Updated the API response for the List Reports endpoint – The revision field was previously documented in the API reference but not actually returned by the API. The API response was updated to return the revision field.
- Updated documentation for layer_experiment_id – The following API endpoints return the layer_experiment_id field, but it was not consistently documented. Updated the Feature Experimentation API reference to ensure consistency with actual API behavior.
June
- Released the ability to sign up for email notifications when Optimizely Experimentation detects a sample ratio mismatch in your running experiments. See Enable email notifications in Optimizely Experimentation.
- Updated the
/reports
endpoint to return tokens for pagination of results as a stand-alone element (previously only included in URLs in response). This makes it easier to programmatically form URLs to request reports from other pages.- Also updated the
/reports
endpoint to return valid endpoints forfetch_results_api_url
andfetch_results_ui_url
to fetch experiment results with subsequent API calls.
- Also updated the
- Released lifecycle management for flags and rules to open beta. This introduces new statutes and makes it easier to see the state of your experiments. See Manage flags and Manage rules.
May
- Released the ability to use cross-project events to track events from your Optimizely Web Experimentation projects in your Optimizely Feature Experimentation project. See Cross-project events.
- Launched automatic creation of flag variables by brainstorming using Opal.
- Renamed and released Advanced Audience Targeting to Real-Time Segments for Feature Experimentation. This lets you use Optimizely Data Platform (ODP) real-time segments to build your Feature Experimentation audiences.
- Updated the minimum SDK versions required for migration from Full Stack (Legacy) to Feature Experimentation. See Upgrade to Optimizely Feature Experimentation from Optimizely Full Stack.
- Java SDK version 3.6+.
- Android SDK version 3.7+.
- No other SDKs have minimum versions.
- Launched automatic creation of flag variations by brainstorming using Opal.
April
Released the ability to link a hypothesis in Collaboration with an experiment in Optimizely Feature Experimentation.
March
Released the ability to use bucketing IDs to decouple user bucketing from user identification.
February
- Increased the allowlist total from 10 to 50 users.
- Released the Scheduling API, which lets you list, create, update, and delete scheduled changes for your Feature Experimentation flags and rules.
January
Breaking change for SDKs
Released a major version update for the following SDKs. See the SDK's GitHub release notes for details, including breaking changes.
- Agent – v4.0.0
- Android SDK – v4.0.0
- C# SDK – v4.0.0
- Go SDK – v2.0.0
- Java SDK – v4.0.0
- JavaScript (Browser and Node) SDK – 5.0.0
- Python SDK – 5.0.0
- React SDK – 3.0.0
- React Native SDK – 3.0.0
- Ruby SDK – 4.0.0
- Swift SDK – 4.0.0
The release includes Advanced Audience Targeting, which was renamed to Real-Time Segments for Feature Experimentation in May 2024.
Please sign in to leave a comment.