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:

  1. Tag fires on the landing/thank-you page (Insight Tag / Pixel / gtag / UET) — and the visitor stays long enough for it to fire.
  2. Conversion action is configured as PRIMARY in an active goal (not secondary/observational).
  3. Click-ID + UTMs survive to the conversion (no redirect stripping gclid/li_fat_id/rdt_cid/utm).
  4. Server-side backup exists (CAPI / server-side GTM) so ad-blockers, ITP, consent-loss don't erase the event.
  5. The event reaches the CRM with correct source mapping (covered in KB 02).

2. Why a platform reports 0 conversions — the checklist (cite these)

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
LinkedIn Insight Tag Conversions API + RAR (HubSpot/SF/Dynamics) li_fat_id event_id secondary conversions + no CAPI = 0 in B2B. RAR
Reddit 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)

  1. Are conversion actions Primary? (fastest, most common zero cause)
  2. Does the tag fire on the real conversion page? Test with the platform's helper/preview.
  3. Do click-IDs/UTMs survive the final URL → LP (test ?gclid=test, check redirects)?
  4. Is there a CAPI/server-side backup, or browser-only?
  5. Is the LP fast enough that visitors don't bounce pre-tag (<2s target)?
  6. Does the event reach the CRM with correct source (→ KB 02)? Each "no" is a finding with the fix + citation above.