Server-side customizations

Varying origin response

This will work for stores on platforms that allow access to server-side code (i.e. Magento or SFCC). For SaaS services like Shopify or BigCommerce, please use CSS or JavaScript customizations.

If CSS and JavaScript customizations do not meet your needs, you can customize the response of the origin site (and so content to be localized) based on custom request headers.

We can enable for all traffic from localized sites headers like:

X-Glopal: <unique_key> - to determine and verify that visit comes from Glopal.

X-Glopal-Country: <country_code> - to present content based on the country.

X-Glopal-Currency: <currency_code> - to present content based on the currency.

X-Glopal-Language: <language_code> - to present content based on the language.

If your site uses request headers to serve different content to Glopal, and you have a page caching solution in place, make sure that all relevant X-Glopal-* headers are included in the cache key. Some caching providers let you configure the cache key or cache policy directly. Others rely on the Vary response header, which must list all X-Glopal-* headers used for content variation.

Glopal customizations

Glopal can handle many edge cases in the sites localization process. All of that happens without any actions taken by the store owners. Some examples of possible server-side customizations:

• modifying HTML source

• change of HTTP headers and cookies

• HTTP redirections for selected parts of the website

• overwriting response with data from external URL

• rewriting external JavaScript files