Hi everyone,
I have a use case, and I’d like to know if it’s possible to implement:
1. A non-logged-in user visits the site. We use a tracker ID or anonymous ID to assign them to a specific A/B test bucket.
2. Later, the same user logs in, at which point we assign them a user ID. This user ID remains the same across sessions, but the tracker ID or anonymous ID can change.
The challenge is that we want to ensure the user is assigned to the same A/B test bucket when they log in, regardless of the change in their tracker ID.
Ideal Solution:
• Initially, the user is assigned to a bucket based on the tracker ID.
• The next time the user logs in, we send both the tracker ID and user ID to the GrowthBook.
• Going forward, when we call the system again (whether the tracker ID changes or not), we should be able to retrieve the same A/B test bucket for that user based on their user ID.
In other words, even if the user comes back with a different tracker ID, as long as we know their user ID, we should be able to ensure they are placed in the same bucket as before.
Is this something that can be done in GrowthBook, or do you have any suggestions on how to implement this?