This message was deleted.

Hey there! On the link in your screenshot, I can see an error in the console that says that the URL being passed in is invalid. Are you able to see what the URL value is? With your more general questions on redirect tests—they do have their challenges and can be prone to SRM. We have some tips on mitigating those issues here: https://docs.growthbook.io/app/url-redirects#sample-ratio-mismatch-srm-warnings-on-url-redirect-tests This is the main issue:

The inherent latency of the trackingCallback sometimes causes the URL Redirect to take place before the

trackingCallback

can complete, which means a disproportionately larger number of exposures are tracked for the control URL versus the redirect URL. This triggers an SRM warning.

If you can dial in your timing so this doesn't happen, then you should be OK. However, it also depends a bit on what you want to test. If it's not entire pages, for example, you may find your implementation simpler by using feature flags in code. If you provide some more context, I can see if there's anything else I can suggest.

Thanks for the answer Ryan! Our business context is that we're trying to see which website converts better from our ads redirection. So we have 2 websites (1 is for ads, commonly known as Landing Pages + 1 for general product details page) currently and only 1 ads account. @strong-mouse-55694