many-jordan-29770
12/09/2024, 12:45 PMStickyBucketing
Config
1. Configured a simple experiment with StickyBucketing activated
a. id
-> hash
b. deviceId
-> fallback attribute
c. LocalStorageStickyBucketService
2. Configured mixpanel integrations without any additional property
3. When mixpanel is loaded, we set the deviceId. Otherwise, the SDK starts with an empty attributes config
4. Next.js integration with React sdk
5. Using LocalStorageStickyBucketService
User Flow
1. The user (generally) lands anonymous
a. We add a deviceId
property that points from mx.get_distinct_id()
2. The experiment starts
3. The user fills out the form and signs up
a. We mx.identify(user_id)
b. Add set the id
proeprty of the user to growth book sdk while keeping the deviceId
c. Dispatch the event to mixpanel
4. After login, an additional One additional call to trackingCallback
seems to be made, with the new id as an attribute
Expected Result
• A single metrics result is generated, pointing w/ 100% rate
Current result
• 2 metric results are created(one anonymous, one logged most likely?), resulting in a 50/50% rate
Are we missing something? Shouldn't StickyBucketing
handle this? Or is it a misconfiguration?
Thanks!fresh-football-47124
fresh-football-47124
fresh-football-47124
green-dream-17832
12/09/2024, 10:26 PM0/3
green-dream-17832
12/09/2024, 10:27 PMExtra UserId Property (optional)
used for when configuring the MP data source?green-dream-17832
12/09/2024, 10:29 PMmany-jordan-29770
12/10/2024, 1:00 PMfresh-football-47124
fresh-football-47124
many-jordan-29770
12/14/2024, 10:47 AMmany-jordan-29770
12/17/2024, 3:24 PMfresh-football-47124
many-jordan-29770
12/19/2024, 10:26 PMfresh-football-47124
fresh-football-47124
many-jordan-29770
12/19/2024, 10:35 PM