You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 92b3b44
Browse filesBrowse the repository at this point in the historyBrowse files
Show and clear split_override cookies from the dashboard
"Force for current user" sets a split_override cookie, but the dashboard
gave no sign it had done so. Because an override is not counted as a
participant unless store_override is set, a pinned experiment reads zero
participants while still rendering an alternative, which looks like the
experiment is broken.
The dashboard now lists the overrides active in the browser at the top of
the page, explains why the numbers can read zero, marks the pinned
alternative in the experiment's table, and can clear them one at a time or
all at once.
The cookie name is now a constant shared by the helper and the dashboard,
instead of being spelled out at each use.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -168,6 +168,8 @@ If you have an experiment called `button_color` with alternatives called `red` a
168
168
169
169
will always have red buttons. This won't be stored in your session or count towards to results, unless you set the `store_override` configuration option.
170
170
171
+
The dashboard's "Force for current user" button does the same thing for your browser, by setting a `split_override` cookie. Because an override is not counted, an experiment you have pinned can keep reading zero participants. The dashboard lists any overrides active in your browser at the top of the page, and lets you clear them individually or all at once.
172
+
171
173
In the event you want to disable all tests without having to know the individual experiment names, add a `SPLIT_DISABLE` query parameter.
<pclass="intro">The list below contains all the registered experiments along with the number of test participants, completed and conversion rate currently in the system.</p>
0 commit comments