Server-Side Tracking Losing UTM Parameters: How to Diagnose Attribution Problems
When server-side tracking loses UTM parameters, attribution data disappears between the campaign click and the destination platform. UTMs have to survive the journey from the landing page through the browser and the server to analytics or your CRM. Find the step where the parameters drop to recover attribution.
Table of Contents
- 01.The UTM journey
- 02.What to check first
- 03.Landing page and redirects
- 04.Capture into cookies or storage
- 05.Web request to the server endpoint
- 06.Server tag mapping to the destination
- 07.Session changes and CRM transfer
- 08.How to test it
The UTM journey
UTM parameters carry campaign attribution. They arrive on the landing page URL, get captured into cookies or storage, travel with the web request to the server container and then forward to analytics or a CRM. If any step drops them, the destination sees a visit with no campaign context. The loss usually happens at a redirect, a storage failure or a mapping gap between layers.
| Step | What happens | Where UTMs drop |
|---|---|---|
| 1. Campaign click | Ad sends visitor to landing page with UTMs | UTMs not appended to the URL |
| 2. Landing page | UTMs present in the URL | Redirect strips query parameters |
| 3. Capture | UTMs stored in cookies or storage | Storage blocked, consent not given |
| 4. Web request | UTMs sent to server endpoint | Variables not mapped into request |
| 5. Server to destination | Server forwards UTMs to analytics or CRM | Server tag does not pass parameters |
What to check first
- Confirm the UTMs are present on the landing page URL after any redirects.
- Confirm your tracking captures UTMs into cookies or storage on first visit.
- Confirm the web request to the server endpoint includes the UTM values.
- Confirm the server tag maps UTMs into the destination request.
- Check the destination platform for the UTM dimensions.
Landing page and redirects
The first place UTMs disappear is the landing page itself. If an ad sends a visitor to a URL with UTMs but a redirect forwards them to a clean URL without the query parameters, the UTMs never reach your tracking. Test the actual landing URL from the ad and confirm the UTMs survive any redirect. A redirect that rebuilds the URL without preserving query strings is a common silent attribution killer.
Capture into cookies or storage
Most first-party collection stores UTMs in a cookie or browser storage on the first visit so they persist across the session. If storage is blocked by browser settings or consent is not given, the UTMs are not captured and later events have no campaign data. Confirm your capture runs on the landing page and that it respects consent while still attempting to store what it lawfully can.
Web request to the server endpoint
The web tracking layer has to include the UTM values in the request it sends to the server endpoint. If the variables that hold the UTMs are not mapped into the request, the server container never sees them. Check the web tag that sends to the server and confirm the UTM variables are included in the payload. A tag that sends the event but omits the UTM variables produces events with no attribution at the server.
Server tag mapping to the destination
Once the server container has the UTMs, the destination tag has to pass them along. For GA4, that means mapping UTMs into the campaign parameters. For a CRM, that means writing them into the lead record fields. If the server tag does not map the UTM values into the destination request, the attribution is lost at the final step. Confirm the server tag references the UTM variables and includes them in the outgoing request.
Session changes and CRM transfer
UTMs can also be lost when a session changes, such as a visitor returning directly later, or when the data moves into a CRM. If the CRM does not store the UTM fields on the lead record, the campaign context is gone from the sales side. Confirm the CRM fields exist and that the data flow writes the UTMs into them. The relationship between analytics and CRM lead data is covered in the guide on GA4 and CRM lead numbers not matching.
How to test it
- 1.Click a campaign link and confirm the UTMs are on the landing page URL.
- 2.Confirm the UTMs are captured into storage on first visit.
- 3.Trigger an event and confirm the web request to the server includes the UTMs.
- 4.Confirm the server tag maps the UTMs into the destination request.
- 5.Check the destination platform for the campaign dimensions.
Frequently Asked Questions
Why do my UTMs show on the landing page but not in GA4?
The UTMs may not be captured into storage, or the web request to the server may not include them, or the server tag may not map them into the GA4 request. Test each step to find where the values drop.
Can a redirect remove UTM parameters?
Yes. A redirect that rebuilds the URL without preserving query strings will strip the UTMs before your tracking sees them. Test the actual landing URL from the ad and confirm the parameters survive any redirect.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
GA4 UTM Parameters Not Appearing Correctly: What to Check
UTMs in the URL is not the same as UTMs in GA4. The parameters have to be captured and processed into the right acquisition dimension. Confirm the URL, the capture and the dimension scope.
GA4 Source and Medium Are Wrong: How to Diagnose Attribution Problems
Wrong source and medium usually come from missing UTMs, redirects stripping parameters or self-referrals. Find where the wrong value originates before changing attribution settings.
Server-Side Tracking Losing Click IDs: GCLID, FBCLID and Attribution Problems
Click IDs link a lead back to the ad click. They have to survive from the landing URL through storage and the server request to your CRM or ads platform. Find where the identifier drops.