Traffic Splitting

Show localized sites under paths next to your existing site content

Setting up Traffic Splitting

Requirements

To use Traffic Splitting, you must have a service in your tech stack that can forward requests based on the URL pattern. We have included examples for different software and platform providers.

Selecting in-scope Paths

When deciding to implement Traffic Splitting, you have to identify all paths where Glopal should show localized site content. You would need to delegate those paths to Glopal.

Directory Path

Delegate to Glopal?

/fr/*

✅

/de/*

❌

/us/*

✅

/ch/*

✅

/ch/checkout/*

❌

/it/*

❌

If you identify URLs that should be excluded from scope — for example, /ch/checkout/* — we recommend using a negative match to ensure these endpoints are not passed to Glopal.

Please contact your Implementation Specialist for assistance if you need help crafting condition.

Generic instructions

Update your CDN, cache, or web server configuration to proxy in-scope paths to Glopal. This configuration cannot work as a simple redirection, since visitors should stay on your domain and not be redirected to Glopal. Many setups have options to delegate specific paths to another origin (Glopal); this is where you can enter Glopal endpoint details.
If possible, add the original Host value (your domain) in the X-Forwarded-Host header when delegating requests to Glopal and pass the original source IP address in the X-Forwarded-For header.
Once the setup is in place, visiting your in-scope URL should display the Glopal logo while the URL remains on your domain.