getting multiple exposures warning and can't figur...
# ask-questionsr
ripe-dinner-7830
04/15/2024, 8:44 AMgetting multiple exposures warning and can't figure out why, we're got a persistent cookie that we put as "id" in the sdk and use for hashing, and then we push viewed experiment to GA and that's it. is there any place where a mixup with things normally happen here? like a common mistake or so?
ripe-dinner-7830
04/15/2024, 8:54 AMi find this so difficult to track down and debug
ripe-dinner-7830
04/15/2024, 8:55 AMour custom cookie has a lifetime of 60 days, and we get multiple exposures on tests (2%) on tests that have ran for only 4 days
f
fresh-football-47124
04/16/2024, 6:06 AM
this happens usually in two days
fresh-football-47124
04/16/2024, 6:06 AM
either you changed the split percentages
fresh-football-47124
04/16/2024, 6:06 AM
or you're using a different identifier for reporting than you are for assignment
fresh-football-47124
04/16/2024, 6:15 AM
sounds like the latter, to me. Are you sure it's being set on first load? Is it possible that this cookie isn't being saved correctly or is added conditionally?
r
ripe-dinner-7830
04/16/2024, 7:16 AM@fresh-football-47124 thanks for replying, the cookie is always set, but i found yesterday that it wasn't set as "necessary" in cookiebot
ripe-dinner-7830
04/16/2024, 7:16 AMso i'm hoping that change will help things
ripe-dinner-7830
04/16/2024, 7:16 AMi mean
ripe-dinner-7830
04/16/2024, 7:17 AMto me the only explanation is that the cookie is somehow lost or recreated due to something, like a cookiebot blocking the cookie in an xhr forcing the logic to create a new one which then makes the user end up on a different experiment
15 Views