Server-Side Tracking Losing Click IDs: GCLID, FBCLID and Attribution Problems
When server-side tracking loses click IDs like GCLID or FBCLID, the advertising click identifiers that connect a lead back to the ad click disappear. These identifiers have to survive from the landing URL through storage and the server request to your CRM or ads platform. Find where the click ID drops to restore attribution.
Table of Contents
- 01.What click IDs do
- 02.What to check first
- 03.Landing URL and redirects
- 04.Storage and forms
- 05.Server request and CRM transfer
- 06.Consent and privacy
- 07.How to test it
What click IDs do
Click IDs are identifiers appended to landing page URLs by ad platforms. GCLID comes from Google Ads and FBCLID from Meta. They link a visitor back to the specific ad click, which is what makes offline conversion tracking and ad platform attribution work. If the click ID is lost, a lead may still arrive in your CRM but with no connection to the ad that produced it.
| Step | What happens | Where the ID drops |
|---|---|---|
| 1. Ad click | Platform appends GCLID or FBCLID to landing URL | URL not configured to carry it |
| 2. Landing URL | Click ID present in the URL | Redirect strips the parameter |
| 3. Storage | Click ID stored in cookie or form field | Storage blocked, not captured |
| 4. Server request | Click ID sent to server container | Variable not mapped into request |
| 5. CRM or ads platform | Click ID written to lead record or sent back | Field missing, not transferred |
What to check first
- Confirm the click ID is present on the landing page URL after redirects.
- Confirm your tracking captures the click ID into storage on first visit.
- Confirm the web request to the server endpoint includes the click ID.
- Confirm the server tag passes the click ID to the CRM or ads platform.
- Check the CRM lead record for the click ID field.
Landing URL and redirects
The click ID arrives in the landing page URL. If a redirect forwards the visitor to a clean URL, the click ID is gone before any tracking runs. Test the actual landing URL from a real ad click and confirm the click ID survives any redirect. Not every platform appends every click identifier, so confirm which identifiers your ad platforms actually use before you expect them.
Storage and forms
The click ID has to be captured and held so it is available when the visitor submits a form or triggers an event later in the session. Most setups store it in a cookie and also write it into a hidden form field. If storage is blocked or the hidden field is missing from the form, the click ID never reaches the CRM. Confirm the capture runs on the landing page and the form includes the click ID field.
Server request and CRM transfer
For server-side setups, the click ID has to travel in the web request to the server container and then be forwarded by the server tag. If the variable is not mapped into the request, the server never sees it. For direct CRM capture, the form has to write the click ID into the lead record field. Confirm the field exists in the CRM and that the data flow populates it. The role of the click identifier in offline conversion tracking is covered in the guide on how qualified lead data can be sent back to Google Ads.
Consent and privacy
Click ID capture can depend on consent, because storing the identifier may require consent in some setups. Do not bypass consent to capture a click ID. If consent is not given, the identifier may not be stored, which is the correct behavior even though it costs attribution. Build your measurement to work within consent rather than around it.
How to test it
- 1.Click a real ad and confirm the click ID is on the landing page URL.
- 2.Confirm the click ID is captured into storage on first visit.
- 3.Submit a form and confirm the click ID is in the form data or server request.
- 4.Confirm the CRM lead record or ads platform receives the click ID.
- 5.If missing, check redirects, storage, the form field and the server mapping.
Frequently Asked Questions
Do all ad platforms use the same click ID?
No. Google Ads uses GCLID and Meta uses FBCLID, and not every platform appends a click identifier. Confirm which identifiers your platforms actually use before you expect them in the landing URL.
Can I capture a click ID without consent?
Storing a click identifier can depend on consent depending on your setup and region. Do not bypass consent to capture it. Build your measurement to work within consent requirements rather than around them.
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
Server-Side Tracking Losing UTM Parameters: How to Diagnose Attribution Problems
UTMs have to survive the journey from landing page through the browser and server to analytics or your CRM. Find the step where the parameters drop to recover attribution.
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.
GA4 and CRM Lead Numbers Do Not Match: How to Audit the Lead Journey
A GA4 lead is an event and a CRM lead is a contact record. They are different things. Find where the journey breaks between the website action and the CRM record before treating a gap as a tracking error.