Hi Mario, good morning đź‘‹
Yeah, as long as this is enabled in the org as per
this PR.
This setup can technically work, with a couple of gotchas to be aware of.
• GrowthBook assigns users by
hashing user id + experiment tracking key, so if both experiments use the same key, any user who hits both will get the same variation in both places.
• A namespace only limits who can be in the experiment; it doesn’t change variation assignment. So one rule can use a namespace (limited traffic) and another can skip it (full traffic) and they’ll stay consistent where they overlap.
I suppose the main caveat is reporting; if both rules use the same Experiment Key, the exposure/results data may be grouped together even though one version is namespace-limited and the other is full-traffic. That can make the results harder to interpret, so this is only safe if you intentionally want both placements treated as the same experiment population.
Could you share a bit more about the use case?
Mainly, are these two placements meant to be analysed as one single experiment, or do you need to understand performance separately for the namespaced page vs the non-namespaced pages?
It would also help to know why the namespace is needed on one page but not the others, and whether users are likely to see both experiences during the same session. That’ll help us make sure the setup keeps assignment consistent without making the reporting harder to interpret later.