Hi Team, I had a quick question on re-ramping exp...
# experimentation
s
Hi Team, I had a quick question on re-ramping experiments. Based on the wiki here, we figured that re-ramping an experiment would re-bucket the users with a new experiment key. I do see a new experiment key after the re-ramp with a <test_name>
-re
appended.. But in the data warehouse we still see traffic with old name <test_name>.. Is this expected ? We were trying to find traffic with the new key but no data was found.. Wanted to confirm if using the old experiment key would still re-bucket the users..
@strong-mouse-55694 Am I asking this question on the right channel ? Do you suggest I ask this elsewhere ?
s
This is the right channel. I think we need some more info on how you re-ramped. Here's some general info on making changes to experiments that might be helpful: https://docs.growthbook.io/app/making-experiment-changes
s
Let me get back to you on this
s
sounds good
s
So just checked with our engineers.. 1. In our case, we had deleted previous experiment 2. started a new experiment with same name and ramped it up Wanted to understand couple of things. Based on my reading - 1. hashing algo uses experiment_key_id and unit_id (user/visitor) 2. When we re-bucket users into the experiment, we should either a. create a New Phase b. create a new experiment_id right ?
I believe we don't have sticky bucketing as of now.. so just trying to understand what we do with our current experiements
Could you explain if 2.a is true how does it rebucket users ?
s
A lot's going to depend on why you're creating a new experiment. What's the reasoning there? Also, the hashing algo will fall back to the experiment.key, but it'll use a generated UUID (seed) by default.