https://www.growthbook.io/ logo
Join Slack
Powered by
Do experiment names and tracking keys need to be d...
# ask-questions
i
Do experiment names and tracking keys need to be different for production and staging or does GB handle that on its own?
🙏 1
r
Hi, can someone confirm this? We're waiting to launch the experiment but want to make sure it's set up correctly.
f
Hi Matjaz - they don't need to be different- on the assignment side, the SDKs will be a different. The event tracking on dev is usually disabled or sent to a separate source so as to not contaminate the events. If the experiment name is the same, and the data ends up in the data warehouse, GrowthBook would have no way to tell the difference between the events.
i
Ok, so experiment key (and name) need to be different for production and staging right?
f
do you track staging data to the same location as production?
Do you have any way to filter out that data?
i
What do you mean by "track data". Metrics?
f
so there is an exposure event that is called from the trackingCallback()
is that event logged by you?
i
No, we let GB handle that
We don't save any experiment data ourselves.
f
ah, GrowthBook stores no event data ourselves
the trackingCallback needs to be set up
do you have any event trackers?
i
Wait, no, we use Segment to track experiment views.
Sorry, I'm not the dev. Just looking through the code and was checking dev branch.
f
okay
you should check with the dev team - usually events from dev/staging are not logged to avoid messing with the data
i
I think we do it so we can test it through.
But, anyways, having a different experiment name and key for staging and production is probably the safest bet?
f
yes, I guess so
i
Alright, thanks.
9 Views
Open in Slack
PreviousNext
Powered by