Best use
Open this hub when the failing layer is already mostly known and the team needs a concrete repair path rather than another generic explainer.
Troubleshooting library
Fix Tracking Issues
Guides for diagnosing the recurring tracking bugs that keep media buyers awake.
Every broken launch hides the same patterns: click IDs vanish, UTMs go dark inside analytics, postbacks never fire, or redirect stacks grow unwieldy. This section collects the most common failures so you can work from a checklist instead of improvising each time.
Use the guides when a teammate flags missing conversions or when you want to proactively document a clean QA flow before scaling spend. Each page covers context, root causes, a reproducible troubleshooting path, and links to the in-house tools that shorten the cycle.
What it should produce
A good fix guide should end with an owner, a repeatable remediation sequence, and a retest path using the same live URL or payload.
How to work
Use the fix library after you already have evidence from the tools or knowledge base, not as the first place to guess from symptoms.
Triage flow
How to approach a tracking incident
Start with evidence, narrow the owner of the failure, then choose the guide that matches the break point instead of guessing from symptoms alone.
Confirm the exact live URL
Work from the production ad, tracker, or landing link that real traffic used. Cleaned-up links often hide the actual break.
Capture proof before changing anything
Run the relevant checker, save the final URL, and compare what survived in the browser versus what reached the tracker, CRM, or server event.
Pick the owner of the break
Most incidents belong to one layer: redirect logic, landing-page capture, postback payload, or downstream storage. Fixing the wrong owner wastes time.
Retest with the same path
After the fix, rerun the same live path until the final page and downstream systems all preserve the same identifiers and campaign data.
Problem groups
Start with the family that matches your incident
These groups make it easier to route the issue to the right guide and the right diagnostic tool before the incident spreads.
Guides
Click ID loss
Use this group when fbclid, gclid, ttclid, or CRM-side click IDs disappear somewhere between the ad click and the stored conversion.
How to Fix fbclid Lost After Redirect
Use this repair guide when the browser-visible redirect path strips fbclid before the final landing page can preserve it. If the final page still has fbclid, the issue belongs downstream in CRM or server-event storage instead.
FBCLID Not Stored in CRM
The landing page receives fbclid, but forms, middleware, or CRM mappings drop it before lead records and Meta match workflows can use it.
GCLID Not Stored in CRM
The landing page receives gclid, but forms, middleware, CRM fields, or offline conversion workflows drop it before Google Ads can reconnect the lead to the click.
GCLID Not Passed to Landing Page
Google Ads clicks reach the landing page without gclid, so attribution, Smart Bidding, and offline match workflows lose a critical identifier.
Click ID Not Stored in CRM
Landing pages capture identifiers, but middleware or the CRM drops them before analysts ever see the data.
Guides
UTM and attribution drift
Start here when campaign tags survive at launch but later vanish in redirects, analytics, forms, or reporting exports.
UTM Parameters Lost After Redirect
Redirect chains drop UTMs before analytics fires, so every downstream report goes blank.
UTM Lost After HTTP to HTTPS Redirect
The protocol upgrade keeps the click alive but strips campaign parameters before the secure landing page loads.
UTM Not Visible in Analytics
The landing page receives UTMs, but analytics reports only show 'not set' rows and empty segments.
UTM Stripped by Redirect
A new hop strips UTMs mid-flight, so paid traffic loses attribution even though pages still load.
Guides
Postback and macro failures
Use these guides when server-to-server callbacks stop arriving, send the wrong values, or fail to replace tracker macros.
Postback Not Working
Networks show zero conversions because callbacks never trigger, fail validation, or stop before partner logs can credit the event.
Postback Returns 200 but No Conversion
The endpoint answers successfully, but the network, tracker, or CRM still does not record the conversion you expected.
Postback Not Received
Trackers show callbacks firing, yet partners insist nothing arrived because firewalls or filters intercepted them.
Postback Macro Not Replaced
Callbacks arrive but contain literal {clickid} or {payout} strings because the template never swapped values.
Guides
Redirect path failures
Choose this family when chains become too long, loop, or rewrite URLs in a way that strips identifiers and slows the funnel down.
Redirect Chain Too Long
Users bounce before the landing page loads because the redirect path now includes every experiment ever shipped.
Redirect Loop Detected
Two hops keep sending traffic to one another, so the browser never reaches a stable destination.
HTTP to HTTPS Redirect Problem
Protocol rewrites trigger duplicate redirects, drop parameters, or cause browsers to warn visitors.
Guides
Pixel and Meta CAPI failures
Use this group when browser-side Meta tracking, server-side delivery, or payload validity breaks before Events Manager can trust the conversion.
Facebook CAPI Not Firing
Meta server-side events are missing, blocked, or mismatched, so Events Manager does not show the conversion flow you expect.
CAPI Event Rejected by Meta
Meta receives the server-side event, but rejects, drops, or marks it invalid because the payload, identifiers, consent context, or deduplication fields do not meet validation rules.
Pixel missing after redirect
Tracking looks healthy on the entry URL, but the final landing page reached through redirects no longer shows the expected browser-side pixel or tag.
Google Tag not detected on landing page
GTM, GA4, or Google Ads tags do not appear on the actual landing page, so launches go live without browser-side measurement.
Guides
17 recurring tracking problems
Start with the scenario that matches your current fire drill, then work through the steps and tools to document a durable fix.
Click ID troubleshooting
How to Fix fbclid Lost After Redirect
Use this repair guide when the browser-visible redirect path strips fbclid before the final landing page can preserve it. If the final page still has fbclid, the issue belongs downstream in CRM or server-event storage instead.
Open guide >Meta click ID troubleshooting
FBCLID Not Stored in CRM
The landing page receives fbclid, but forms, middleware, or CRM mappings drop it before lead records and Meta match workflows can use it.
Open guide >Click ID troubleshooting
GCLID Not Passed to Landing Page
Google Ads clicks reach the landing page without gclid, so attribution, Smart Bidding, and offline match workflows lose a critical identifier.
Open guide >Google Ads click ID troubleshooting
GCLID Not Stored in CRM
The landing page receives gclid, but forms, middleware, CRM fields, or offline conversion workflows drop it before Google Ads can reconnect the lead to the click.
Open guide >Click ID troubleshooting
Click ID Not Stored in CRM
Landing pages capture identifiers, but middleware or the CRM drops them before analysts ever see the data.
Open guide >Click ID troubleshooting
TTCLID Not Tracked
TikTok click IDs fall out across translation layers or smartlinks, leaving Events API payloads without match keys.
Open guide >Click ID troubleshooting
MSCLKID Not Recorded
Microsoft click IDs vanish after regional redirects or template reuse, so offline imports fail.
Open guide >UTM governance
UTM Parameters Lost After Redirect
Redirect chains drop UTMs before analytics fires, so every downstream report goes blank.
Open guide >UTM governance
UTM Lost After HTTP to HTTPS Redirect
The protocol upgrade keeps the click alive but strips campaign parameters before the secure landing page loads.
Open guide >UTM governance
UTM Not Visible in Analytics
The landing page receives UTMs, but analytics reports only show 'not set' rows and empty segments.
Open guide >UTM governance
UTM Stripped by Redirect
A new hop strips UTMs mid-flight, so paid traffic loses attribution even though pages still load.
Open guide >Postback troubleshooting
Postback Not Working
Networks show zero conversions because callbacks never trigger, fail validation, or stop before partner logs can credit the event.
Open guide >Postback troubleshooting
Postback Returns 200 but No Conversion
The endpoint answers successfully, but the network, tracker, or CRM still does not record the conversion you expected.
Open guide >Postback troubleshooting
Postback Not Received
Trackers show callbacks firing, yet partners insist nothing arrived because firewalls or filters intercepted them.
Open guide >Postback troubleshooting
Postback Macro Not Replaced
Callbacks arrive but contain literal {clickid} or {payout} strings because the template never swapped values.
Open guide >Pixel and tag troubleshooting
Google Tag not detected on landing page
GTM, GA4, or Google Ads tags do not appear on the actual landing page, so launches go live without browser-side measurement.
Open guide >Redirect and pixel troubleshooting
Pixel missing after redirect
Tracking looks healthy on the entry URL, but the final landing page reached through redirects no longer shows the expected browser-side pixel or tag.
Open guide >Meta server-side troubleshooting
Facebook CAPI Not Firing
Meta server-side events are missing, blocked, or mismatched, so Events Manager does not show the conversion flow you expect.
Open guide >Meta payload troubleshooting
CAPI Event Rejected by Meta
Meta receives the server-side event, but rejects, drops, or marks it invalid because the payload, identifiers, consent context, or deduplication fields do not meet validation rules.
Open guide >Redirect diagnostics
Redirect Chain Too Long
Users bounce before the landing page loads because the redirect path now includes every experiment ever shipped.
Open guide >Redirect diagnostics
Redirect Loop Detected
Two hops keep sending traffic to one another, so the browser never reaches a stable destination.
Open guide >Redirect diagnostics
Meta Refresh Redirect
A meta refresh tag forces visitors to wait before the real page loads, often stripping parameters in the process.
Open guide >Redirect diagnostics
HTTP to HTTPS Redirect Problem
Protocol rewrites trigger duplicate redirects, drop parameters, or cause browsers to warn visitors.
Open guide >