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 Microsoft IIS, NGINX and Cloudflare.
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 during your planning you find that there are URLs that shouldn't be inscope, for example, we have decided that /ch/checkout/* should not be inscope, we would recommend negative regex so these endpoints are not passed to Glopal.
If you need assistance writing the regex, please reach out to your Implementation Specialist who will be able to assist you.
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, as 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-Hostheader when delegating requests to Glopal and pass the original source IP address in theX-Forwarded-Forheader.Once the setup is in place, visiting your in-scope URL should display the Glopal logo while the URL remains on your domain.
Platform instructions
Select below the correct instructions for the service you are running.
Last updated
