HomeGuidesAPI Reference
Submit Documentation FeedbackJoin Developer CommunityLog In

Optimizely logs most actions you can perform for a project, such as creating a page, modifying a variation, and adding and removing audiences. These actions are listed in the change history, which displays 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 which changes were made, when, and by which collaborator. The detailed change history creates an activity trail that provides additional security to individuals and teams with multiple collaborators.

Filter and view change history

Each project’s change history is listed under Experiments > History.

Click image to enlargeClick image to enlarge

Click image to enlarge

Use the filters at the top of the page to refine the changes displayed. Currently you can filter to show changes by type and / or date range.

Click image to enlargeClick image to enlarge

Click image to enlarge

For each change, you will see a Show details button. Click the button to view the specific change details, or hold alt / option (Mac) + click to show or hide all changes.

Click image to enlargeClick image to enlarge

Click image to enlarge

The change history detail panel displays descriptions of each change, along with the original (before changes) in red on the left side and the updated code (after changes) in green on the right side. If you are interested, you can find out more about how this data is structured in our public API Reference. To collapse the change detail view, click the Hide details button.

Click image to enlargeClick image to enlarge

Click image to enlarge

Full Stack changes

Type

Action

Captured?

A/B test

Feature Test

Creation

Run/Pause

Archive/Unarchive

Variations

Audience Targeting

Metrics

Traffic Allocation

X

Distribution Mode

Groups

Whitelist

Name

Description

Feature (for Feature Tests)

Type

Action

Captured?

Features

Creation

Run/Pause

Archive/Unarchive

Key

Description

Variables

Edit Controls (Traffic Allocation)

Audiences

Type

Action

Captured?

Groups

Create

Name

Description

Experiment

Traffic Allocation

Type

Action

Captured?

Audiences

Create

Name

Description

Conditions

Type

Action

Captured?

Attributes

Create

Key

Description

Type

Action

Captured?

Account

All Changes

X

Type

Action

Captured?

Project Settings

Create

Name

Description

Statistical Significance

Create Webhook

X

Regenerate Webhook Secret

X

Delete Webhook

X

Integrations

X

Collaborators

X

Time Zone

X

IP Anonymization

X

Bot Filtering

Type

Action

Captured?

Event

Key

Description

Type

Action

Captured?

Environments

Creation

Key

Description

Archive/Unacrhive

X

Restricted Access

📘

Notes

  1. Various Project updates (captured and not) may result in updates to tracked project keys (e.g., code_revision, js_file_size).

  2. Custom Analytics Integrations are technically Extensions, so those changes will be found with a type of Extensions.

  3. Pageview Events are technically just Pages, so those changes will be found with a type of Pages.

  4. Default Environments will not have corresponding change logs upon project creation.


Did this page help you?