Hi, I have a question about redirect tests. We've decided to resort to using it for an upcoming test where we will test two different pages against each other. It's definitely not the optimal approach, but due to resource and time constraints we have decided to take this approach. The issue we have now is that since we randomize users on an essential cookie, i.e. before they accept cookies (to avoid flickering), the experiment_viewed datalayer event can not be pushed since the users won't have time to accept the cookies before being redirected. This will obviously cause SRM, so no point in even starting the test as it is now. That leads me to my question which is how you that use redirects on the regular have handled this? Or are we doomed from the get go?

its a bit of a pickle and depends on your comfort with setting any cookies even ones that are essential (like ones for showing feature flags)

Thanks for the answer! Yeah we are comfortable with setting the cookie before consent and randomizing on it, but that is also what is causing the issue with the redirect. But we would of course instead face major flickering if we were to wait for a cookie that only loads after consent or wait for redirect before consent is given. I guess there are not so many options here, but it just felt weird since it feels like redirect is widely used (even in frontend implementations) but I have a hard time thinking that you'd just accept SRMs or major flickering 🤔