Server-side GTM doesn’t automatically know which user is making a request. Without proper client ID management, you’ll see duplicate sessions, broken user journeys, and incorrect attribution. This guide covers generation strategies and persistence mechanisms that work in production environments. Learn more in our guide on GTM Variable Priority.

Understanding the Client ID Problem in Server-Side GTM

In client-side GTM, the browser handles identity via first-party cookies. Server-side GTM breaks this because server containers don’t automatically access browser cookies. Each request is isolated. Learn more in our guide on Server-Side GTM Consent.

Client ID Generation: UUID vs Deterministic Hashing

Two approaches dominate. UUID generation creates a random unique ID per new user — simple, compatible with GA4, but requires backend persistence. Deterministic hashing derives an ID from stable signals like IP and user agent — no storage needed but carries privacy risks and fragility.

Persistence Mechanism 1: First-Party Cookies

The simplest persistence method is a server-set first-party cookie storing the client ID. Set the cookie domain to .yourdomain.com to share across subdomains. Use Secure and SameSite=Lax flags. This persists across sessions automatically and is accessible to client-side GTM.

Persistence Mechanism 2: Backend Database or Cache

For higher privacy or cross-domain scenarios, store client IDs in a backend cache (Redis) mapped to session tokens. This survives cookie deletion, works across domains and mobile apps, and gives you a complete audit trail. Use a fast cache layer to avoid database latency on every request.

Persistence Mechanism 3: Auth-Based Identity

For logged-in users, their account ID becomes the persistent identifier. Use auth_{user_id} as the client ID, falling back to cookie-based IDs for anonymous users. This enables cross-device tracking and matches GA4’s user-ID feature.

Client ID Reconciliation

Users often accumulate multiple client IDs across anonymous and authenticated sessions. Implement merge logic on authentication: mark the anonymous ID as merged into the auth ID, then use the auth ID for all future events. In BigQuery, join on userId when available to unify sessions across client IDs.

Testing Your Implementation

• Make multiple requests from the same client and verify the client ID stays constant
• Delete the cookie and verify recovery or new session creation
• Check different clients generate different client IDs
• Monitor GA4 or BigQuery for duplicate sessions or broken user journeys

Server-side GTM client ID management is foundational to accurate tracking. Choose your persistence mechanism based on privacy requirements and infrastructure capabilities, then test thoroughly.