Detect Global-e

PluginView evaluates public page signals in these classes when identifying Global-e. Individual fingerprint rule bodies are proprietary and are not published.

• Cookies
• Script sources
• JavaScript globals

Illustrative indicators derived from public catalog metadata for Global-e. A live scan may match additional proprietary rules beyond these examples.

• GlobalE_CT_Data
• GlobalE_Data
• GlobalE_SupportThirdPartCookies
• .global-e.com
• GLOBALE_ENGINE_CONFIG
• GlobalE

Establishes

One or more public signals on the scanned page matched a known Global-e signature (6 rules) at the time of the scan.

Does not establish

A sitewide install of Global-e, an active vendor contract, exclusive use, or that Global-e is still in place today.

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Global-e signals.
2. 2. PluginView reads only public responses (cookies, script sources, javascript globals) and scores them against the Global-e signature set (6 rules).
3. 3. Review the confidence score and text explanation for Global-e on the results page.

Can PluginView detect Global-e without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Global-e — typically cookies, script sources, javascript globals. It does not bypass authentication or paywalls.

What category is Global-e?

Global-e is classified under Cross border ecommerce in the PluginView directory.

How many fingerprint rules cover Global-e?

This reference currently tracks 6 fingerprint rules across cookies, script sources, javascript globals. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Global-e?

Illustrative public indicators for Global-e include GlobalE_CT_Data; GlobalE_Data; GlobalE_SupportThirdPartCookies. A live scan may match additional proprietary rules beyond these examples.