Automated Optimizely Experiment Register
Every Monday, WebRun opens Optimizely, lists every running and paused experiment with its start date, traffic allocation and status, updates an Airtable experiment register, and raises a Trello card for each test that has overrun its planned end date or is not collecting enough traffic to ever conclude.
How do I keep track of which Optimizely experiments are still running?
WebRun opens Optimizely every Monday and lists every running and paused experiment with its owner, start date and traffic. It keeps an Airtable register up to date and raises a Trello card for any test that has overrun its planned end date or is starved of traffic, so nothing runs forever unnoticed.
- No experiment runs for months after everyone stopped watching it
- One Airtable register replaces a spreadsheet nobody keeps current
- Low traffic tests get fixed or killed instead of quietly wasting sessions
Built for experimentation teams · growth marketers · product managers · CRO consultants
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.optimizely.comin a real browser with your saved login - no setup, no API keys. -
1
Optimizely - list every running experiment
optimizely.com
WebRun opens Optimizely to list every running experiment. - Sign in to Optimizely and open your projects list
- For each project, capture every running and paused experiment
- Record the name, owner, status, start date, traffic allocation, and the metrics it targets
- Note how many days each experiment has been live
- Flag experiments that are live but receiving little or no traffic
Done when Every running and paused experiment is captured with its age and traffic state.
-
2
Airtable - maintain the experiment register
airtable.com
WebRun opens Airtable to maintain the experiment register. - Open your experiment register base in Airtable
- Add or update one row per experiment with owner, status, start date, days live, and target metric
- Mark rows whose experiments have been concluded or archived in Optimizely
- Keep a weekly snapshot column so you can see how long each test has been open
- Sort the view so the oldest live experiments sit at the top
Done when The Airtable register matches what is actually running in Optimizely.
-
3
Trello - raise a card for overrunning tests
trello.com
WebRun opens Trello to raise a card for overrunning tests. - Open your experimentation board in Trello
- Create a card for each experiment past its planned end date, naming the owner and the days live
- Create a card for each low traffic experiment so someone can decide to fix or kill it
- Skip experiments that already have an open card
- Leave the decision to stop or extend a test to the owner. WebRun never pauses or concludes an experiment
Done when Every overrunning or starved experiment has an owned card on the board.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it pause or stop an experiment?
No. WebRun only reads Optimizely and reports. Pausing, concluding, or shipping a variation stays with the experiment owner, who gets a Trello card asking for the decision.
How does it know a test has overrun?
It compares days live against the planned end date recorded on the experiment's row in your Airtable register, so your own planning window decides what counts as overdue.
What about experiments in other projects?
It walks every project you give it access to, so a register covering several sites or apps stays in one Airtable base.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.