KB 01 — Conversion Tracking & Server-Side (the "why is it zero" doc)
Serves decisions: D1 (is tracking broken, where), D2 (LinkedIn/Reddit zero). Dated: 2026-07-17. Every claim cites 01-CANON.md. Weighted B2B; ecommerce notes flagged.
1. The single most important idea
Zero tracked conversions is not zero actual conversions. In B2B especially, a platform can report 0 while clicks genuinely convert. Before ever judging a channel, confirm the tracking chain is intact end-to-end. The chain has five links; a break in any one produces a zero or a leak:
- Tag fires on the landing/thank-you page (Insight Tag / Pixel / gtag / UET) — and the visitor stays long enough for it to fire.
- Conversion action is configured as PRIMARY in an active goal (not secondary/observational).
- Click-ID + UTMs survive to the conversion (no redirect stripping gclid/li_fat_id/rdt_cid/utm).
- Server-side backup exists (CAPI / server-side GTM) so ad-blockers, ITP, consent-loss don't erase the event.
- The event reaches the CRM with correct source mapping (covered in KB 02).
2. Why a platform reports 0 conversions — the checklist (cite these)
- Conversions set to secondary/observational. Only Primary actions appear in the "Conversions" column and feed bidding; secondary actions report only in "All conversions." An account can show 0 while converting. Google — primary vs secondary. Prime suspect for MSAI LinkedIn/Reddit.
- No Conversions API, long sales cycle. Browser tags (Insight Tag) capture only a short cookie window (LinkedIn ~7 days); B2B deals close weeks/months later, outside it. CAPI/RAR extends this and posts server-side. LinkedIn CAPI adopters saw ~31% more attributed conversions; RAR window is now 365 days. LinkedIn RAR (2024-06-14); Social Media Today (2025-02-19).
- Ad-blockers / ITP / consent loss. ~30%+ of users block or deny browser tags; browser-only tracking structurally under-reports. Server-side is the durability fix. Search Engine Land (2026-05-11); Meta CAPI dedup.
- Redirect strips the click-ID/UTMs. http→https, non-www→www, link shorteners, consent gateways drop the query string before the tag stores it → unattributed = reported 0. Blue Frog (2026). This is exactly the WTWH-redirect question Katie flagged 2026-07-09.
- Bounce before the tag fires. Slow mobile pages (2.5-2.7s) bounce ~38-46% before analytics/conversion tags record anything. Magnet CWV (2025). MSAI: hundreds of LinkedIn clicks → 86 GA4 sessions.
- Tag missing/misfiring on the actual conversion page, or the conversion happens off-site (LinkedIn Lead Gen Forms not synced to CRM). LinkedIn Help a6884246.
- The offline upload never runs (Google ECL/offline import): the qualified-lead event must actually be uploaded from the CRM or the Conversions column stays 0. Google ECL.
3. Server-side is the durable foundation
Move tag execution to a first-party tagging server (server-side GTM) so events fire from your own domain — resilient to ad-blockers, ITP, and third-party-cookie deprecation. It's the pipe that feeds every platform's CAPI reliably. Google server-side overview; Simo Ahava. Pixel/tag + CAPI run redundantly, deduplicated on a shared event_id+event name — send a matching ID from both sources or you double-count. Meta dedup.
4. Per-platform quick reference
| Platform | Browser tag | Server-side | Click-ID | Dedup key | Notes |
|---|---|---|---|---|---|
| Google Ads | gtag / GTM | Enhanced Conversions for Leads + offline import | gclid | order/user data | FLAG: OCI/ECL move to Data Manager API; classic Ads API upload blocked from 2026-06-15. ECL |
| Insight Tag | Conversions API + RAR (HubSpot/SF/Dynamics) | li_fat_id | event_id | secondary conversions + no CAPI = 0 in B2B. RAR | |
| Reddit Pixel | Conversions API | rdt_cid | shared event ID | heavy ad-blocking audience → CAPI near-mandatory. Reddit CAPI | |
| Meta | Pixel | Conversions API (offline API retired 2025) | fbclid | event_id | primary for ecommerce clients. Meta |
| Microsoft | UET | UET Conversions API | msclkid | — | often cheaper B2B search. UET |
5. The diagnostic order (what the agent runs)
- Are conversion actions Primary? (fastest, most common zero cause)
- Does the tag fire on the real conversion page? Test with the platform's helper/preview.
- Do click-IDs/UTMs survive the final URL → LP (test
?gclid=test, check redirects)? - Is there a CAPI/server-side backup, or browser-only?
- Is the LP fast enough that visitors don't bounce pre-tag (<2s target)?
- Does the event reach the CRM with correct source (→ KB 02)? Each "no" is a finding with the fix + citation above.