Hey, have a issue with a url redirect experiment. ...
# experimentation
n
Hey, have a issue with a url redirect experiment. SRM is really high and consistent over time. What would be the steps to troubleshoot this? I'd rather relaunch the experiment. Attaching some screenshots.
f
Hi Radvile, good morning! Apologies for the delayed response and thank you for your patience. Please can you confirm which SDK you are using to build this redirect test?
Also are you using GTM in your implementation?
If so, what you've described is a known problem with URL Redirect tests, and the issue is especially pronounced when using Google Tag Manager (GTM). Not sure if you're using that or not.
What happens is that the inherent latency of the trackingCallback causes the URL Redirect to take place before the trackingCallback can complete, which means a much larger exposure to the control URL than to the redirect URL.
We have a PR open to help address this for some common use cases, and this PR will be particularly useful for folks using the HTML Script Tag SDK. It won't completely eliminate the problem, but will make it less egregious.
In the interim, you can try increasing the amount of time the trackingCallback has in order to complete by setting the
context.navigateDelay
to a larger number, such as 300ms instead of the default 100ms as per the guidelines here.
However, the PR is scheduled to be merged late this week or early next week.
If performance is critical, we recommend doing A/B testing using Edge Workers instead of on the client. We have an example using Cloudflare here, but also support Fastly and AWS.
As for the PR, for some tracking libraries like GA4 and GTM, GrowthBook waits until the tracking call finishes. So this will likely be much faster than 300ms unless the user is on a very slow network. For other tracking libraries like Segment, we follow their best practices and wait a standard 300ms.
It's also worth mentioning that this problem with URL Redirects, especially when used in combination with GTM, is not unique to GrowthBook. Any A/B testing tool that supports client-side redirects will have this same problem.
Hope this helps and sorry for the lengthy response, we wanted to make sure you had all context 🙏
n
Hey @flaky-noon-11399 thanks for all this. We use a mix of direct implementation (HTML Script Tag SDK) + GTM implementation (in-app, where most of conversion happen). I'll talk to our developers and share what you shared with me and see what's the next best step forward. I'll come back here if I have any follow up questions.
f
Hi @nutritious-market-77567 it was my absolute pleasure to assist and yes this would definitely be the culprit given your implementation of GTM and the HTML SDK.