- Optimizely Web Experimentation
- Optimizely Personalization
- Optimizely Optimizely Performance Edge
- Optimizely Feature Experimentation
- Optimizely Full Stack (Legacy)
Follow this article to receive email notifications when new Optimizely Experimentation Analytics content is added for 2023.
December
- Renamed the Enriched Events Export to Experimentation Events Export.
- Released Optimizely's automatic sample ratio mismatch detection.
October - November
In 2022, Optimizely partnered with Google to innovate and bring you stronger data capabilities.
As part of this partnership, Optimizely is taking the next step and is migrating a large part of the Optimizely data infrastructure to the Google Cloud Platform (GCP). This will come with some new features and changes to how Optimizely calculates experiment results for specific user segments. The transition should be seamless for you, and no downtime is expected. Your experiment results will stay accessible, and running experiments will not need to be paused or restarted.
Result page segmentation update
Starting to roll out on October 9, 2023, Optimizely is transitioning to event-based segmentation on the results page. This new approach will reflect the specific attribute values of each event rather than the last touch within a session, offering a more accurate insight into individual events and their associated attributes. Event-based segmentation aligns more closely with advanced analytical tools, enhancing the precision of attribute assignment during segment filtering.
Additional information
-
Decision event attribute values are only considered for visitor count when segmenting on the experimentation results page.
- The conversion event has to contain the segmented attribute value for the metric count to assign the event towards the segment, as segmentation is now event-scoped. For information, see Count conversions when filtering by segment.
- Optimizely Personalization campaigns will continue to consider the attribute value of the decision event, as you may qualify for multiple experiences in one session.
- The event-based segmentation update is not a UI change. Instead, it modifies how numbers are displayed on the results page.
Enriched Events Export
- Removed automatically generated session IDs from the Enriched Event Export. Optimizely will not automatically create session IDs in the event pipeline, as they are rarely used for outside analysis. Sessions are now calculated as part of experiment results to improve data accuracy.
- Removed the automatically generated
experiments
andexperiment_id
fields for conversions, as part of the GCP migration. To attribute conversions to an experiment, map the conversions to the decisions table using thevisitor_id
. This is recommended because you also need to consider the timing of the decision and conversion event.
Bot filtering
Updated the bot and spider filtering to improve data quality and accuracy.
Event API updates
Enforced the maximum payload size for the Optimizely Event API to 3.5 MB, as part of the GCP migration.
June
Fixed a bug when switching the baseline on the results page would show the wrong baseline's data.
May
Results page improvements
- Fixed a bug where the legend for the Conversion Rate Over Time graph was overlapping.
- Added Last update and Last event dates on the Experiment Results page.
Additional improvements
- Added 202 return code for the
get_experiment_results
andget_experiment_timeseries
endpoints for the Optimizely REST API, indicating that the requested operation was received, but not completed, and users should wait and try again later. -
Added back the ability to unarchive experiments for the following products:
- Improved page load performance of the results page by not blocking when encountering stale cache data.
Bug Fixes
- Fixed a bug where changing the baseline in the Results page would interfere with the Statistical Significance being displayed.
March
Fixed an issue where a single experiment in a Personalization Campaign would attribute the variation data to the wrong row in the Experiment Summary table.
February
Architectural updates
Moved backend architecture to Google Cloud Platform, allowing Optimizely Experimentation to deliver more complex features quicker, measure success effectively, and enable data democratization.
Added new result page alerts that provide details about experiment result data freshness.
Bug Fixes
Fixed the date logic for the result page segmentation feature. The date picker now properly handles the start and end dates chosen by the user.
Fixed ResultsAPI to handle traffic allocations set to less than 100% correctly.
Please sign in to leave a comment.