- Optimizely Web Experimentation
- Optimizely Performance Edge
- Optimizely Personalization
You can view the change history for your projects and identify changes that might have caused problems with your experiments.
Optimizely Experimentation logs actions performed for a project, like creating a page, modifying a variation, and adding and removing audiences. These actions are listed in the change history, which shows the record of user activity for each of your projects.
If an experiment starts to behave strangely or stops working correctly, you can troubleshoot by checking the change history to see the changes that were made, when, and by which collaborator. The change history creates an activity trail that provides additional security to individuals and teams with multiple collaborators.
For each project, go to History.
Click Show details drop-down list to see changes.
Use the drop-down lists to filter the Type, Date, and Source (if the change was made using the REST API or the Optimizely Web Experimentation UI).
Press Alt (Windows) or Option ⌥ (Mac) + click Show details or Hide details to display or collapse all change details.
Change history in Optimizely Web Experimentation
The following lists the changes Web Experimentation saves in each project's change history:
Audience
- Created
- Archived
- Unarchived
- Modified name, description, or conditions
Event
- Created
- Modified
Experience templates
- Changes to Apply JS, Reset JS, HTML, and CSS in the extension builder
Experiment
- Created
- Archived
- Unarchived
- Modified name or description
- Changed variation
- Changed element
- Inserted HTML or image
- Added redirect
- Changed variation CSS or JavaScript
- Changed shared code (JavaScript or CSS)
- Added or removed page
- Added or removed event
- Changed primary metric
- Changed traffic allocation
Page
- Created
- Modified
Project JavaScript – All changes
Variation changes made with the Visual Editor – All changes
Variation changes made with the Code Editor – All changes to CSS and JavaScript code
Please sign in to leave a comment.