This message was deleted.

Hi Josh. In order to run an experiment or do a rollout with a feature, GrowthBook needs some sort of user identifier in the attributes. If it's an anonymous visitor, you can use something like a session cookie or a distinct id stored in local storage.

Thanks Jeremy. Got it, so either we don't instantiate Growthbook till we have access to a user identifier or we use a generate a session cookie.

We recommend passing two identifiers into GrowthBook attributes.

id

for logged in user id (set to empty string for anonymous) and

anonId

with a cookie id or similar that is passed for all users, logged in and anonymous.

Great so you are saying that Growthbook does merge permanent and anon IDs. Does it give priority to the permanent Id on repeat visits? For example, someone starts with anonId and then adds a permanent ID later in the session when they create their account. When the user comes back to the app the next time and we initialise them with the permanent ID will they still be placed into anon ID bucket they started with the first time ?

When you create an experiment, you specify what attribute you want to use for bucketing. So if you choose an anonymous id, it will always use that to assign a variation, whether or not the person is logged in.

So what is the rationale for passing in a anonymous ID and a permanent ID when instantiating context if they cannot be merged and experiments will only ever use one of them?

Some experiments may only be on the logged in portion of your app. In that case you could use a userId for assignment. That way if the person logs in on another device, they will keep seeing the same variation. Other times you want to test something that includes logged out users so you would use an anonymous id. The assignment part for an experiment will only use one of the IDs. But when analyzing results, we can map between the IDs when needed. For example if the person sees an experiment, then logs in and completes an action, we can tie those together.

Got it. I think I understand. I may have follow-up questions once I've digested this. But this is ridiculously helpful. Thank you so much.

Are you using the React SDK?

Vanilla JS

So there's a hook in the GrowthBook instance to set a render function that is called anytime attributes or features change. You can use that to re-render your application and re-evaluate all of the features.

growthbook.setRenderer(() => {
  // re-render your app here
})

Then when the user switches accounts, you would just call

setAttributes

with the new account info

Amazing. That's exactly what I was hoping for. Super grateful for your help Jeremy.