Projects: experiment name chevron-publish -> chevron-publish-v2 #24537
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There were a couple of major flaws with my initial set up for the A/B test of publishing in different ways from the
PersonalProjectsTable
.1.) I was logging a 'page-load' every time the table (re)rendered rather than only when the projects page was loaded. Fixed in #24527.
2.) I timed the set up of my user based experiment on production too late based on my other changes so there was a duration where everyone was only seeing one variation.
To collect accurate data, I've updated the experiment name from
chevron-publish
tochevron-publish-v2
in this PR, and set up new experiments on production and staging and stopped the previous version.staging
set up new
chevron-publish-v2
stop
chevron-publish
production
set up new
chevron-publish-v2
stop
chevron-publish
Note, there is potential for slight user bad with this change. Someone previously in one variation of the study might be randomized into the other, which could be confusing. Hopefully, publishing is straightforward enough via either UI that it won't be too disruptive - and we're about to find out which method is more discoverable!