Knowledge base
Explore the hub as an incident-routing system, not a passive article archive. It groups the site's strongest clusters: redirect plus UTM breakdowns, click ID loss, postback troubleshooting, and Pixel plus Meta CAPI validation.
Use this page when the team knows revenue or attribution drift is real but still needs to prove where the break starts. The shortest useful path is usually: trace the live URL, confirm the landing-page state, compare the downstream payload, then branch into the one support or fix page that owns the repair.
That workflow matters because the same incident often touches multiple layers. A redirect can strip fbclid, the landing page can lose UTMs, the CRM can fail to store the surviving click ID, or Meta can reject the event even though the browser looked healthy. This hub keeps those branches connected so you stop reopening the same investigation from scratch.
Teams that keep this page inside launch checklists and QA runbooks usually recover faster, because everyone shares the same proof pack: original URL, redirect trace, final landing URL, click-ID state, browser-side tag evidence, and the exact callback or CAPI response that changed the outcome.
Why it matters
Indexable troubleshooting pages work only when they solve a specific ownership question. This hub is built to answer which layer owns the loss before you send traffic back into the same broken funnel.
How to use it
Start from the cluster card or quickstart article that matches the symptom, collect proof with the linked tool, then move forward into one focused support or fix page instead of opening unrelated diagnostics.
Evidence to collect
A useful escalation should include the original campaign URL, redirect trace, final landing URL, click ID state, browser-side tag proof, and any postback or server-event payload that proves exactly where the data changed.
What happens next
Once the failing layer is isolated, continue into the matching support article, fix library, or audit request with the same evidence pack instead of re-explaining the incident to every stakeholder.
Start here
Use these category entry points when you need one first article, one first tool, and a clear explanation of what to prove before you escalate.
Click IDs
Protect fbclid, gclid, ttclid, and msclkid across complex funnels.
Best first article
What is fbclid?
Understand how Meta's click identifier powers bidding, deduplication, and offline attribution, then learn how to keep it intact.
Best first tool
Redirect Checker >Pixel + CAPI
Compare browser-side tags and server-side Meta events before match quality, deduplication, or payload validation breaks attribution.
Best first article
How to compare Pixel vs CAPI event
Compare the browser-side Meta Pixel signal with the server-side CAPI event so you can prove where match quality, deduplication, or payload accuracy starts breaking.
Best first tool
Facebook CAPI Tester >UTMs
Govern naming conventions, audit campaign links, and prove which source deserves credit.
Best first article
UTM parameters lost after redirect
Stop redirect chains from stripping utm_source, utm_medium, and custom parameters before they reach analytics or CRM systems.
Best first tool
Redirect Checker >Redirects
Trace every hop in a smartlink, cloaker, or tracker and document what happens to query strings.
Best first article
fbclid lost after redirect
Diagnose and fix Meta Click ID loss caused by smartlinks, cloakers, and caching rules that rewrite URLs mid-flight.
Best first tool
Redirect Checker >Postbacks
Validate macros, payloads, and server-to-server callbacks before payouts shift.
Best first article
What is postback tracking?
Understand the server-to-server callback model, the fields a healthy payload should carry, and when to move into QA or live-incident debugging.
Best first tool
Postback Tester >Recovery paths
These four lanes keep the hub focused on the strongest live clusters. Each one starts with a core diagnostic tool and ends with the next support or fix page worth opening.
Redirect + UTM
Use this route when redirects, smartlinks, or protocol changes rewrite the destination before UTMs and click IDs reach the final page. The main goal is to prove which hop changed the URL and which launch checklist page should own the retest.
Click ID loss
Use this route when the landing page, hidden fields, CRM handoff, or tracker storage breaks attribution even though the ad click itself was valid. The best evidence is the final landing URL plus the exact place the identifier stops surviving.
Postback troubleshooting
Use this route when the live request exists but the payout, conversion, or partner log still does not match expectations. The owner is usually a macro, payload, or template mismatch, not another round of redirect guessing.
Pixel + Meta CAPI
Use this route when you need to separate browser-side tag presence from server-side event quality. The key question is whether the missing conversion belongs to weak landing-page tags, low match-key coverage, or a rejected Meta payload.
Core reads
These articles solve the recurring routing, launch QA, and recovery questions that tend to block multiple paid-media teams at once.
9 min read
Diagnose and fix Meta Click ID loss caused by smartlinks, cloakers, and caching rules that rewrite URLs mid-flight.
Open article >10 min read
Stop redirect chains from stripping utm_source, utm_medium, and custom parameters before they reach analytics or CRM systems.
Open article >10 min read
Use this page for live callback incidents where real conversions should already be credited, but production delivery, transport, or payload failures break the callback.
Open article >9 min read
Run a pre-launch callback QA routine so trackers, affiliate networks, and partners agree before paid traffic starts.
Open article >8 min read
Use a repeatable pre-launch QA process so tagged campaign URLs survive redirects, reach the right landing page, and stay readable in analytics.
Open article >8 min read
Run a pre-launch redirect QA process so campaign links resolve to the right landing page, keep attribution parameters, and avoid hidden hop-level failures.
Open article >9 min read
Validate the handoff from a Meta ad click to the final landing URL so fbclid survives redirects and reaches your capture layer intact.
Open article >10 min read
Use a pre-launch QA workflow to prove that fbclid, gclid, and other click IDs survive the live path, reach the landing page, and get stored downstream before spend starts.
Open article >9 min read
Compare the browser-side Meta Pixel signal with the server-side CAPI event so you can prove where match quality, deduplication, or payload accuracy starts breaking.
Open article >Evidence path
Use the same sequence every time so redirects, click IDs, landing-page tags, postbacks, and server-side events stay in one evidence pack instead of splitting into separate Slack threads.
Step 1
Start with Redirect Checker whenever the incoming campaign URL can change before the browser reaches the final destination. Redirect proof is the baseline for nearly every UTM, click-ID, and landing-page dispute.
Open Redirect Checker >Step 2
Use Click ID Extractor or Pixel Scanner to verify whether the final destination still carries the identifiers and browser-side tags the campaign depended on before you touch CRM or callback logic.
Open Click ID Extractor >Step 3
When the browser path still looks clean, the next owner is usually the server-side handoff. Validate the postback or event payload before you assume a traffic-source problem.
Open Postback Tester >Step 4
Only branch into the repair guide once the failing layer is clear. That keeps Meta event validation, click-ID storage, redirect QA, and postback debugging from collapsing into one vague incident ticket.
Open the fix library >Next step
Once the knowledge-base article makes the failing layer clear, continue into the next proof page, support article, or fix lane instead of starting over from a generic audit.
Support article
Stay inside the knowledge-base library when the team still needs a focused diagnostic article on redirect QA, click-ID validation, postback payload comparison, or Pixel versus CAPI evidence.
Open a deeper troubleshooting article >Fix path
Move into the fix library when the evidence already shows the incident belongs to redirect loss, click-ID storage, postback delivery, or Meta event rejection instead of general education.
Open the fix library >Escalation
Request a tracking audit when the team has already collected the main artifacts but needs a cross-layer review of redirects, landing pages, callbacks, and attribution handoffs together.
Open tracking audit >Click IDs
Protect fbclid, gclid, ttclid, and msclkid across complex funnels.
10 min read
Understand how Meta's click identifier powers bidding, deduplication, and offline attribution, then learn how to keep it intact.
Open article →10 min read
Understand how Google Click ID keeps Ads, Analytics, and offline conversion imports aligned, and learn how to preserve it through complex funnels.
Open article →10 min read
Learn how TikTok's click identifier keeps Spark Ads, Events API uploads, and CRM imports in sync, plus the safeguards that stop it from disappearing.
Open article →9 min read
See how Microsoft Ads relies on msclkid for attribution, offline imports, and UET audiences, and learn the safeguards that keep it alive.
Open article →9 min read
Diagnose and fix Meta Click ID loss caused by smartlinks, cloakers, and caching rules that rewrite URLs mid-flight.
Open article →9 min read
Fix Google Click ID loss when auto-tagging collides with redirect stacks, vanity URLs, or caching layers.
Open article →11 min read
Find and fix leaks between the landing page, storage layer, and CRM so click IDs make it into every downstream system.
Open article →9 min read
Validate the handoff from a Meta ad click to the final landing URL so fbclid survives redirects and reaches your capture layer intact.
Open article →10 min read
Use a pre-launch QA workflow to prove that fbclid, gclid, and other click IDs survive the live path, reach the landing page, and get stored downstream before spend starts.
Open article →9 min read
Compare the browser-side Meta Pixel signal with the server-side CAPI event so you can prove where match quality, deduplication, or payload accuracy starts breaking.
Open article →Pixel + CAPI
Compare browser-side tags and server-side Meta events before match quality, deduplication, or payload validation breaks attribution.
9 min read
Compare the browser-side Meta Pixel signal with the server-side CAPI event so you can prove where match quality, deduplication, or payload accuracy starts breaking.
Open article →UTMs
Govern naming conventions, audit campaign links, and prove which source deserves credit.
10 min read
Stop redirect chains from stripping utm_source, utm_medium, and custom parameters before they reach analytics or CRM systems.
Open article →11 min read
Find and fix leaks between the landing page, storage layer, and CRM so click IDs make it into every downstream system.
Open article →8 min read
Use a repeatable pre-launch QA process so tagged campaign URLs survive redirects, reach the right landing page, and stay readable in analytics.
Open article →8 min read
Run a pre-launch redirect QA process so campaign links resolve to the right landing page, keep attribution parameters, and avoid hidden hop-level failures.
Open article →Redirects
Trace every hop in a smartlink, cloaker, or tracker and document what happens to query strings.
9 min read
Diagnose and fix Meta Click ID loss caused by smartlinks, cloakers, and caching rules that rewrite URLs mid-flight.
Open article →9 min read
Fix Google Click ID loss when auto-tagging collides with redirect stacks, vanity URLs, or caching layers.
Open article →10 min read
Stop redirect chains from stripping utm_source, utm_medium, and custom parameters before they reach analytics or CRM systems.
Open article →8 min read
Use a repeatable pre-launch QA process so tagged campaign URLs survive redirects, reach the right landing page, and stay readable in analytics.
Open article →8 min read
Run a pre-launch redirect QA process so campaign links resolve to the right landing page, keep attribution parameters, and avoid hidden hop-level failures.
Open article →9 min read
Validate the handoff from a Meta ad click to the final landing URL so fbclid survives redirects and reaches your capture layer intact.
Open article →10 min read
Use a pre-launch QA workflow to prove that fbclid, gclid, and other click IDs survive the live path, reach the landing page, and get stored downstream before spend starts.
Open article →Postbacks
Validate macros, payloads, and server-to-server callbacks before payouts shift.
11 min read
Understand the server-to-server callback model, the fields a healthy payload should carry, and when to move into QA or live-incident debugging.
Open article →10 min read
Use this page for live callback incidents where real conversions should already be credited, but production delivery, transport, or payload failures break the callback.
Open article →10 min read
Run a repeatable pre-launch QA routine for postbacks before campaigns go live, partners are onboarded, or callback templates change.
Open article →9 min read
Run a pre-launch callback QA routine so trackers, affiliate networks, and partners agree before paid traffic starts.
Open article →9 min read
Diff the callback you expected against the callback that actually fired so macro, encoding, and partner-side mismatches stop hiding inside 200 responses.
Open article →9 min read
Understand how macros map tracker data into partner payloads and how to manage them as your funnel evolves.
Open article →