Click ID troubleshooting
FBCLID Lost After Redirect
Redirect stacks strip Meta's click ID before forms save it, so Events Manager never sees the real visitor.
Open guide >Troubleshooting library
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.
Guides
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
Redirect stacks strip Meta's click ID before forms save it, so Events Manager never sees the real visitor.
Open guide >Click ID troubleshooting
Auto-tagged Google Ads clicks hit the landing page without gclid, so bidding models operate blind.
Open guide >Click ID troubleshooting
Landing pages capture identifiers, but middleware or the CRM drops them before analysts ever see the data.
Open guide >Click ID troubleshooting
TikTok click IDs fall out across translation layers or smartlinks, leaving Events API payloads without match keys.
Open guide >Click ID troubleshooting
Microsoft click IDs vanish after regional redirects or template reuse, so offline imports fail.
Open guide >UTM governance
Redirect chains drop UTMs before analytics fires, so every downstream report goes blank.
Open guide >UTM governance
The landing page receives UTMs, but analytics reports only show 'not set' rows and empty segments.
Open guide >UTM governance
A new hop strips UTMs mid-flight, so paid traffic loses attribution even though pages still load.
Open guide >Postback troubleshooting
Networks show zero conversions because callbacks never trigger or fail validation.
Open guide >Postback troubleshooting
Trackers show callbacks firing, yet partners insist nothing arrived because firewalls or filters intercepted them.
Open guide >Postback troubleshooting
Callbacks arrive but contain literal {clickid} or {payout} strings because the template never swapped values.
Open guide >Redirect diagnostics
Users bounce before the landing page loads because the redirect path now includes every experiment ever shipped.
Open guide >Redirect diagnostics
Two hops keep sending traffic to one another, so the browser never reaches a stable destination.
Open guide >Redirect diagnostics
A meta refresh tag forces visitors to wait before the real page loads, often stripping parameters in the process.
Open guide >Redirect diagnostics
Protocol rewrites trigger duplicate redirects, drop parameters, or cause browsers to warn visitors.
Open guide >