-
FBCLID Lost After Redirect
Redirect stacks strip Meta's click ID before forms save it, so Events Manager never sees the real visitor.
-
FBCLID Not Stored in CRM
The landing page receives fbclid, but the form, middleware, or CRM record drops it before Meta attribution and lead reporting can reuse the identifier.
-
GCLID Not Stored in CRM
The landing page receives gclid, but the form, middleware, or CRM record drops it before Google Ads attribution, offline imports, or downstream lead scoring can reuse the click ID.
-
GCLID Not Passed to Landing Page
Auto-tagged Google Ads clicks hit the landing page without gclid, so bidding models operate blind.
-
Click ID Not Stored in CRM
Landing pages capture identifiers, but middleware or the CRM drops them before analysts ever see the data.
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.
Guides
15 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.
-
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
A protocol upgrade drops UTMs on the secure hop, so the landing page loads but analytics and attribution lose the campaign context.
-
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.
-
Postback Not Working
Networks show zero conversions because callbacks never trigger, leave the queue late, or fail partner validation.
-
Postback Returns 200 but No Conversion
The callback is accepted, but credit still fails because the partner cannot match, approve, or trust the conversion.
-
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 still contain literal {clickid} or {payout} strings because the template never swapped values.
-
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.
-
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 request, but schema errors, weak match keys, or low-trust payload fields stop the event from becoming usable attribution data.
-
Pixel Missing After Redirect
The approved destination loads after the redirect chain, but the Meta pixel or tag stack disappears on the real landing page that paid traffic actually reaches.
-
Google Tag Not Detected on Landing Page
The landing page loads, but the Google tag or GTM container never initializes on the real page that paid traffic reaches.