Hi everyone. I'm experiencing the Multiple Exposure issue, and need advice on how to try to solve it. I've looked into our datawarehouse. For users with this issue, the pattern in consistent. • Users get 1 growthbook-experiment event with one variation. And then, often 3-4 seconds later, they will get another growthbook-experiment event with the other variation. • And from then on, all remaining events will contain the 2nd variation. This is our implementation code:

window.growthbook_config = window.growthbook_config || {};

window.growthbook_config.attributes = {

"visitorState": "Company",

"userIsLoggedIn": "foo",

"useQuarterlyBonus": "foo",

"PageTemplate": "foo",

"item_list_name": "foo",

"lomax_source": "foo"

};

window.growthbook_config.trackingCallback = function(experiment, result) {

if (typeof dataLayer !== 'undefined') {

dataLayer.push({

'event': 'growthbook_experiment',

'experiment_id': experiment.key,

'variation_id': result.key

});

}

console.log("GrowthBook experiment:", experiment.key, "variation:", result.key);

};

Greatly appreciate any advice on how we can try to resolve this 🙏 🙏 🙏

Hi @acoustic-pencil-84832 👋 The multiple exposure issue is fundamentally caused by a mismatch between the attribute that you are randomizing on (your "hash attribute") and the identifier being stored in your data warehouse. We have our tech docs here on how to debug this issue. Please can you review the doc linked to further debug?

Hi @flaky-noon-11399 When I visit your documentation link, and then click "you can read more about this problem and how to solve it here", nothing happens. I'm not taken to any new page; clickin the link only appends a param to th URL: https://docs.growthbook.io/kb/experiments/troubleshooting-experiments#solution-3-ensure-the-hash-attribute-and-identifier-type-match Can you provide the direct URL to read about the solution?

Thank you for bringing that to our attention, I'll update it now. It should point to this URL: https://docs.growthbook.io/kb/experiments/troubleshooting-experiments#solution-4-ensure-the-hash-attribute-and-identifier-type-match

Thanks you. I'll take a look, and return if I have further questions 🙂

Thank you Kim, hope you have a lovely and sunny weekend too!! The forecast looks pretty decent in the UK so should be a great weekend here 🙏🏾🌞🫶🏿

This is happening to me too!

Hi @mysterious-salesmen-51192 Not yet, unfortunately. It's in my developer's backlog. I can report back to you when my company sees progress (I can't provide an ETA however)

@acoustic-pencil-84832 It's possible it is not on your end. We experienced a similar thing Edge writes one gbuuid in set-cookie, but another in the page source on the first load, after the next load, the page source and storage gbuuid cookie match. It is a confirmed known bug with growthbook. They are working on a fix. I'm unsure if that's your exact issue, but we experienced very similar things, so it may be. Just an fyi

@mysterious-salesmen-51192 Thank you for the update. 🙂 It is definitely valuable to get your perspective, so I very much appreciate it. I will add this insight to my dev's ticket for context.

@acoustic-pencil-84832 It was confirmed to me in chat by one of the team members. You can also see the PR here: https://github.com/growthbook/growthbook-proxy/pull/118 Unfortunately it looks like it's taken longer than I'd hoped for a fix, but hopefully we'll get one soon.