GA4 sessions or users jumped after moving to server-side GTM: which jump is it and where to look.
- “GA4 users doubled after server-side GTM”
- “GA4 sessions increased after server-side tagging”
- “GA4 new users spike after moving to server-side GTM”
- “GA4 traffic jumped after sGTM”
- “GA4 FPID new users spike”
- “server managed client ID new users GA4”
- “GA4 sessions up after server-side tagging”
Baris Asa, tracking specialist, London · Last checked: 14 November 2026
Check for a counting change before you assume growth. If new users jumped far more than total users, the server probably gave returning visitors new IDs. If users and events both stepped up on one date, the same hits are probably being sent twice. If only sessions jumped, sessions are probably being split. These are my readings; Google documents the mechanisms, not the size.This is the opposite of server-side GTM errors, where hits stop arriving. Here they arrive and are counted differently. It is filed as F-401 . How to plan the move so it does not happen is in the migration plan.
Which number moved?
| What you see in GA4 | What it usually means | Your first check |
|---|---|---|
| New users far ahead of total users | Returning visitors got new IDs | Compare New users with Total users either side of the date |
| Users and events both step up on one date | The same hits reach GA4 twice | One test visit’s Network tab (for your developer) |
| Sessions up, users flat | Split sessions | Traffic acquisition by date: did a (not set) or direct row grow? |
| Purchases up too | Purchase events sent twice | Purchase fires twice, F-101 |
Date the jump to the day, not the week. A step on the day of one publish points at that publish.
No developer to run the checks? Send me the GA4 property and the container and I will tell you which jump it is: server-side tracking.
Did the visitor ID change?
GA4 counts a new user when it sees a first_visit event. Which browser counts as new depends on a visitor ID. Server Managed is a setting in the server container’s GA4 client: the server keeps that ID instead of the browser. Google’s course tells you to start on JavaScript Managed, where the browser keeps it. Google also offers an over-time migration option for properties with existing traffic, so old IDs are not cut off. The mechanics are in Stage 6 of the migration plan.
My inference: Server Managed switched on without that option gives a returning visitor a new ID, and they log first_visit again. New users jump; total users barely move, because those people were already counted. Google documents the setting and the option, not the effect.
GA4-only check: Reports, Tech, Tech details, with the date range split at the change. Add New users and Total users as columns if they are missing, or build the same table in Explore. A gap of tens of points, not a few, is the signal. That threshold is my rule of thumb.
| Same dates | Reset | Real recovery |
|---|---|---|
| New users | +60% | +9% |
| Total users | +4% | +9% |
| Store orders | flat | +8% |
| Return visit, same ID? | no | yes |
If the extra users are visitors you previously lost, orders would be expected to move with them. If orders stay flat, suspect a counting change. Google publishes no figures for either case.
For your developer: open the GA4 client in the server container and read the cookie setting that is selected. Do not go on what you remember choosing.
Is every hit going through one route?
Google says not to keep a server-side and a standalone client-side implementation on the same page for the same property. It also says that with Server Managed IDs every measurement for the stream must flow through the server tag, with none sent directly to Google.
A leftover tag, a plugin or a hard-coded gtag.js that still sends by the old route can count the same page view twice.
For your developer: DevTools, Network, filter for collect, load one test page and click one test action. Google’s course says outgoing requests should go to your tagging server instead of google-analytics.com. Any GA4 hit that goes to a Google host instead of your tagging server, such as google-analytics.com, is a candidate second route. Confirm it by checking that the same hit is not also arriving in server Preview. Then open server Preview on the same visit: the Incoming HTTP Request should match the Network tab.
If the second route sends purchases, revenue doubles only when the two copies carry different transaction_id values or none. GA4 deduplicates purchase events with the same ID. An empty string is a separate mistake: GA4 then treats every purchase with an empty ID as one. Check the ID first. The fault is F-101 .
Are sessions being split?
A session starts when a page is viewed while no session is active, and by default one times out after 30 minutes of inactivity. At the start GA4 creates a session ID (ga_session_id), the start time in seconds.
The Google tag in the browser attaches that ID to events. Google’s sessions page says Measurement Protocol and Data Import events do not get it automatically, and its Measurement Protocol page says a new session_id creates a new session. So a sender other than the browser tag, such as a CRM sending conversions, is a place to look. That reading is mine, not something Google says about server-side setups.
Google’s tagging guidance names two more causes of split or missing identity:
- Tag order. The config command can affect user and session identity for the rest of the page, and custom events fired before it are batched with
session_start. - Cookie prefix. The prefix changes the first-party cookie that holds client and session state. Google recommends one prefix across the site and says inconsistent prefixes mean users cannot be tied across sessions.
Google lists (not set) rows, wrong user and session counts, and a large share of direct traffic as the symptoms. If paid clicks are being filed as direct, that is F-204 , not this note.
What do I do once I know?
- Reset: nothing to undo. Annotate the date so nobody reads it as growth. If you have not switched yet, use the migration option first.
- Two routes: remove the one that should not send. Publish one change at a time and check the Network tab after each.
- Split sessions: one tag owns session identity, one cookie prefix, config before custom events.
After any fix, wait for a full reporting day and look again. A step that does not move after the fix was not the cause. Filed under F-401 , closed when orders and the Network tab agree.
When is it more than a settings change?
- Google Ads bids on GA4 key events and the jump touched purchases.
- Two web streams or properties receive the data.
- A second domain, a roll-up cookie or a CRM sender is in the picture. Each carries an identity of its own.
- The server drops out for part of the day and the numbers swing with it. That is hosting, covered in who maintains what.
If it is not clear which jump it is, send me the container and the GA4 property and I will tell you.
Common questions
Why did my GA4 users jump after I set up server-side GTM?
New users jump when returning visitors get new IDs. See “Did the visitor ID change?” above. The other cause is the same hit reaching GA4 by two routes.
Is a jump in sessions after server-side tagging real traffic?
Usually not, but check before you decide. Compare sessions with store orders or CRM leads for the same dates. Real growth moves orders.
Will the jump settle on its own?
In my reading, a one-off ID reset is a bump that fades as returning visitors are re-counted, not a trend. Google does not publish how long that takes. A double route does not settle: it stays until one route is removed.
Why did direct traffic or (not set) grow after the move?
Google lists missing user or session identity as a cause of both. If those rows grew on the date of the move, treat it as the same problem. Paid clicks filed as direct is a different fault, F-204 .
Sources
Read on 14 November 2026:
- Analytics Help, Tagging best practices to avoid unassigned, (not set), and direct traffic issues (no server-side and standalone client-side on the same page for the same property; Server Managed substitutes a separate client ID; over-time migration option; all measurements through the server tag; config command and event order; cookie prefix;
(not set), wrong counts and direct traffic as symptoms) - Google for Developers, Configuring the Google Analytics data stream with server-side tagging (start with JavaScript Managed; outgoing requests should go to your tagging server instead of
google-analytics.com) - Google for Developers, Preview and debug server containers (the incoming request mirrors the Network tab)
- Analytics Help, About Analytics sessions (session starts; 30-minute default timeout;
ga_session_idis the start time in seconds; Measurement Protocol and Data Import events do not get session IDs automatically) - Analytics Help, Understand user metrics (New users are those who logged
first_openorfirst_visit) - Analytics Help, Minimize duplicate key events with transaction IDs (purchase events with the same transaction ID are deduplicated; do not send an empty string as the ID)
- Google for Developers, Measurement Protocol: sending events (a new
session_idcreates a new session;client_idshould match the website tag’s) - Simo Ahava, FPID cookie and server-side tagging (third-party description of Server Managed IDs and the migration option; not Google’s wording)