How to Prevent GA4 Session Splintering and Internal Self-Referrals

Session integrity in Google Analytics 4 dictates the accuracy of every acquisition report, conversion path, and attribution model. In multi-brand portals, subdomains, and decentralized web funnels, session continuity frequently breaks down mid-journey.

When a user navigates from your marketing blog to a portal application or returns from an external payment gateway, GA4 often drops the active session parameters and instantiates a brand-new session.

The analytical damage of this «session splintering» is severe:

• Attribution Erasure: Organic search, paid media campaigns, and referral touchpoints are stripped, and the final conversion is credited to Direct or an Internal Self-Referral.
• Inflated Session Counts: Metrics show an artificial surge in sessions paired with plummeting engagement rates and distorted average session duration.
• Funnel Collapse: Multi-step funnels show sudden drop-offs at the transition point, even though users successfully completed the conversion.

This technical playbook breaks down the exact mechanics of GA4 session creation, how to diagnose cross-domain linker parameter loss, and how to eliminate internal attribution overwrites.

The Core Trigger: How GA4 Determines Session Boundaries

Unlike Universal Analytics, which terminated sessions at midnight or upon encountering new campaign parameters mid-session, GA4 determines session continuity via two tokens evaluated client-side:

1. ga_session_id: A UNIX epoch timestamp indicating the moment the session was initiated.
2. ga_session_number: A cumulative integer recording how many sessions that specific client_id has generated.

A session breaks and splinters under three specific conditions:

Diagnostic 1: Detecting Linker Parameter Drops Across Redirects

When users navigate across distinct domains configured inside your cross-domain measurement settings, GA4 appends the _gl parameter:

https://checkout.externaldomain.com/?_gl=1*1abcde*_ga*MTEyMjMzNDQ...*_ga_XXXXXX*...

If your destination web server executes an HTTP 301 or 302 redirect (such as stripping trailing slashes or redirecting from HTTP to HTTPS) without explicitly forwarding the query string, the browser drops _gl. The landing page script executes without the linker payload, treating the visitor as new.

How to Verify Query Forwarding via Terminal:

Bash

curl -I -L "https://checkout.externaldomain.com/?_gl=1*test*"

Inspect the response headers:

• If the Location header in the redirect response omits ?_gl=1*test*, your web server configuration or proxy (such as Cloudflare rules configured without URL preservation, as explored in our Cloudflare edge cache bypass guide) is actively dropping attribution tokens.

Diagnostic 2: Identifying Internal Referral Leaks in BigQuery

To locate where session fragmentation happens in production, run this diagnostic SQL query against your raw GA4 export. This query isolates sessions where the referrer belongs to your own web properties:

SQL

SELECT
  (SELECT value.string_value FROM UNNEST(event_params) WHERE key = 'page_referrer') AS referrer,
  COUNT(DISTINCT CONCAT(user_pseudo_id, (SELECT value.int_value FROM UNNEST(event_params) WHERE key = 'ga_session_id'))) AS split_sessions_count
FROM
  `your-gcp-project.analytics_123456789.events_*`
WHERE
  event_name = 'session_start'
  AND (
    (SELECT value.string_value FROM UNNEST(event_params) WHERE key = 'page_referrer') LIKE '%yourprimarydomain.com%'
    OR (SELECT value.string_value FROM UNNEST(event_params) WHERE key = 'page_referrer') LIKE '%checkoutplatform.com%'
  )
  AND _TABLE_SUFFIX >= FORMAT_DATE('%Y%m%d', DATE_SUB(CURRENT_DATE(), INTERVAL 7 DAY))
GROUP BY
  referrer
ORDER BY
  split_sessions_count DESC;

If internal domains appear in the results, those URLs are failing to pass the linker parameter or are missing from your GA4 referral exclusion list.

Step 1: Configure GA4 Cross-Domain Linking & Unwanted Referrals

To prevent session breaks across multi-domain ecosystems:

1. Navigate to Admin > Data Streams > Web Stream > Configure tag settings.
2. Select Configure your domains:
   • Add all root domains involved in the conversion journey (e.g., brand.com, checkout-portal.com, booking-app.com).
   • Do not add subdomains (e.g., app.brand.com and shop.brand.com share first-party cookies automatically at the root level and do not require cross-domain linking).
3. Navigate to List unwanted referrals:
   • Add your primary domains and any third-party payment gateways (e.g., paypal.com, stripe.com, klarna.com).
   • Marking payment gateways as unwanted referrals ensures that when the user returns to your confirmation page, GA4 ignores the payment gateway as a new referrer and preserves the original source.

If transactions occur across decoupled single-page apps or headless frontends, implement custom URL token handshakes as documented in our guide to fixing GA4 checkout tracking in headless Shopify stores.

Step 2: Stop Internal UTM Tagging (The Session Killer)

A frequent operational mistake is tagging internal promotional banners or navigation links with UTM parameters:

HTML

<!-- DANGEROUS: Destroys active campaign attribution -->
<a href="/pricing/?utm_source=internal_banner&utm_medium=website">View Pricing</a>

When GA4 detects incoming UTM parameters on an internal click:

1. It immediately closes the active campaign attribution window.
2. It overwrites the traffic source with internal_banner / website.
3. If an initial ad click from Google Ads brought the user, that paid click is overwritten, destroying ROAS data and preventing offline revenue uploads like those in our Meta CAPI offline deal deduplication pipeline.

The Fix: Remove all internal UTM parameters. Track internal promotion performance strictly via the native select_promotion and view_promotion enhanced ecommerce events.

Step 3: Handle Cross-Domain Navigation via JavaScript Links

If your site initiates navigation across domains via JavaScript rather than native HTML <a> tags:

JavaScript

// Native GA4 automatic linker CANNOT intercept this:
window.location.href = 'https://portal.externalbrand.com/signup';

Native linker decorators only hook standard click events on anchor elements. If you use programmatic redirection, decorate the URL manually using the Google Tag API:

JavaScript

function navigateWithGa4Linker(destinationUrl) {
  if (typeof gtag !== 'function') {
    window.location.href = destinationUrl;
    return;
  }

  gtag('get', 'G-XXXXXXXXXX', 'linker_param', function(linkerParam) {
    var url = new URL(destinationUrl);
    
    if (linkerParam) {
      // Split the key/value pair (e.g., "_gl=1*abc*...")
      var parts = linkerParam.split('=');
      url.searchParams.set(parts[0], parts[1]);
    }
    
    window.location.href = url.toString();
  });
}

If your application architecture hosts forms inside embedded frames rather than standard top-level redirects, standard linker decoration will fail completely. In those architectures, deploy the messaging bridge detailed in our guide on fixing cross-domain tracking in iFrame checkouts.

Frequently Asked Questions

Does switching between subdomains split the GA4 session?

No, provided both subdomains share the exact same Measurement ID and the cookie domain is set to auto (the default in GA4 and GTM). GA4 writes cookies to the highest possible domain level (e.g., .brand.com), ensuring sessions persist across app.brand.com and shop.brand.com without special cross-domain configurations.

Why do sessions split after user consent is granted?

If your Consent Management Platform (CMP) fires pageviews before consent is resolved and re-fires them upon acceptance with differing settings, a race condition occurs. To prevent consent-driven session restarts, follow our setup protocols in the Google Consent Mode v2 unassigned traffic guide.

How long does a GA4 session remain active during inactivity?

By default, a GA4 session terminates after 30 minutes of user inactivity. If your application involves long-form task completion (such as loan applications or document signing), extend the session timeout under Web Stream > Configure tag settings > Adjust session timeout up to the maximum allowable limit of 7 hours and 55 minutes.

---