Change Management

Every experiment and every remote configuration in ABetterChoice keeps a per-object change timeline. Use it to answer questions like "who started this experiment?", "when did the rollout percentage change?" and "did a setup edit happen before the SRM alert?".

Where to find history

Experiment history

1. Open the experiment from Experiments in the left sidebar.
2. On the detail page, click … in the top-right corner (next to Make Decision).
3. Choose History.

A drawer opens with the chronological list of events for this experiment, including:

• Lifecycle transitions (Not Started → In Progress → Shipped → Archived).
• Setup edits — variants, parameters, targeting, traffic, metrics.
• Statistical-engine setting changes (significance, power, FDR, variance reduction).
• Decisions made via Make Decision.

Each entry records the actor (member username) and the timestamp in your workspace time zone (top-right UTC+0 toggle).

Remote configuration log

1. Open the configuration from Remote Config in the left sidebar.
2. On the detail page, click … in the top-right corner (next to Link a new experiment).
3. Choose Log.

The same kind of timeline appears, including:

• Default value and rule changes.
• Group moves (e.g. Ungrouped → iaa).
• Lifecycle changes (Active ↔ Archived).
• Linking to / unlinking from an experiment.

Practical workflows

Diagnosing an SRM alert

Open the experiment's History and look for setup edits (targeting, allowlist, traffic percentage, layer change) immediately before the SRM check started firing. Mid-flight setup edits are the most common cause of SRM, and the history surfaces them by timestamp.

Reverting a remote configuration

ABetterChoice does not have a one-click revert button on the Log entry today. To roll back:

1. Open Log and note the previous values.
2. Click Edit on the configuration to re-apply them.
3. Save. The revert itself shows up as a new entry in Log.

Reviewing experiment decisions

Every time someone clicks Make Decision the choice (launch / rollback / archive / extend) is recorded along with the actor. Use History as the canonical record when post-mortems ask "who decided to ship Variant B?".

What is not covered (yet)

ABetterChoice does not currently expose:

• A project-level audit log that aggregates events across all experiments and configurations.
• Explicit approval / review workflows before a setup edit goes live.
• Webhook delivery of change events to external systems.

If you need any of these, talk to support — they are tracked on the roadmap.