This message was deleted.
# experimentationw
worried-planet-2191
10/08/2024, 1:56 AMThis message was deleted.
r
rhythmic-agent-34208
10/08/2024, 8:27 AMHi Luke, yes you're understanding is correct for both. The navigateDelay will only affect redirect tests and it will increase the amount of time the trackingCallback has in order to complete, so up to 300ms.
rhythmic-agent-34208
10/08/2024, 8:30 AMWe had a PR to address this here, 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.
rhythmic-agent-34208
10/08/2024, 8:30 AMIf 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: https://docs.growthbook.io/lib/edge/cloudflare
111 Views