Google _gl Linker Decoder
Paste a link that contains _gl= and see exactly what it carries to the next domain: the GA4 client ID, the session, and Google Ads click IDs. Use it to check cross-domain tracking to a checkout, booking or payment site.
Click a link from your site to the other domain, then copy the full address from the browser bar (it must contain _gl=). Press Ctrl + Enter to decode.
Private by design: everything is decoded in your browser. Nothing you paste is uploaded or stored.
Sessions still break at checkout?
I fix cross-domain and third-party checkout tracking (Stripe, PayPal, Shopify, booking engines) so purchases keep their real source.
How to use the _gl Linker Decoder
When a visitor moves from your site to another domain you own (a checkout, booking engine or payment page), Google tags add a _gl parameter to the link. It carries the GA4 client ID, the current session and any Google Ads click ID, so the second domain can continue the same journey instead of starting a new user with the source "referral".
Step by step
- On your main site, click the link or button that goes to the other domain (for example "Checkout" or "Book now").
- Copy the full address from the browser bar on the destination page before it redirects again.
- Paste it here and click Decode. Check that _ga and your _ga_<ID> session cookie are both there.
- Open the same page in GA4 DebugView or Tag Assistant and confirm that the session continues with the same client ID.
How to read your result
_ga and _ga_<ID> both present
The link carries the user and the session. If GA4 still shows a new session, add both domains under Admin → Data streams → Configure tag settings → Configure your domains.
Only _gcl_* cookies
The Google Ads conversion linker decorates the link, but the GA4 tag does not. Users will look new on the destination domain.
No _gl at all
Cross-domain linking is not configured, the link is added by JavaScript after the tag ran, or a redirect removes the query string.
Common mistakes
- Testing with a link copied from an email or chat: the hash only works in the same browser for about two minutes.
- Redirects on the destination domain that drop the query string, so _gl never reaches the page with the GA4 tag.
- Forms that post to the other domain: the linker only decorates links and forms Google tags can see when they load.
- Adding the domains to GA4 but forgetting the referral exclusion for the payment provider (for example PayPal or Stripe).
Questions
Is the _gl parameter safe to share?
It contains pseudonymous IDs, not names or emails. Still, avoid posting real ones publicly; decoding here happens only in your browser.
Why does the destination ignore a valid _gl?
The hash must match the visitor's browser and be under about two minutes old, and the destination domain must be in your GA4 domain list.
Do I need cross-domain tracking for subdomains?
No. Subdomains of the same site (shop.example.com and example.com) share cookies automatically. You need _gl only between different domains.
Sessions still break at checkout?
I fix cross-domain and third-party checkout tracking (Stripe, PayPal, Shopify, booking engines) so purchases keep their real source.