Hi team, we're implementing GB into our environment and now have an issue I was wonder if there is a way GB can handle it. below is a message from our developer.

The new and old PDP run as separate applications on separate servers.

When a user requests a URL, AWS (or Cloudflare) must determine which server to route the request to.

GrowthBook operates at the application or client level, meaning the routing decision has already been made before GrowthBook is applied—whether the user lands on the PHP app or the Next.js (React) app

is there any way to get around this issue and utilize GB to split the traffic for the mv tests? Thank you!

Hello, Thank you for reaching out! GrowthBook has a Cloudflare Edge SDK that supports this use case! docs.growthbook.io/lib/edge/cloudflare Basically you would move the routing decision itself to the edge, one layer earlier than where AWS/Cloudflare currently picks an origin. Instead of your CDN/LB making a static routing rule, you put a Cloudflare Worker (or Lambda Edge) in front of both origins. That worker: 1. Runs the GrowthBook SDK to evaluate the experiment for each visitor (with a cookie for consistent bucketing across visits) 2. Based on the assigned variation, proxies the request to either the PHP app or the Next.js app 3. Keeps the public-facing URL unchanged for the user I hope this helps. Please let me know if you have any questions!