ads-server-side-trackinglisted

# Server-Side Tracking Pipeline Audit Audits the entire server-side measurement pipeline that backs every paid channel's modeled conversion data. Without server-side tracking in 2026, expect 30-40% conversion data loss from iOS ATT, ITP, and aggressive ad blockers — that's the gap between what's actually happening and what your bid algorithms can see. This sub-skill is technical and deep. It's NOT the same as `ads-attribution`, which audits the *attribution model* sitting on top of these events. ## Process 1. Collect server-side stack inventory: sGTM container info, Meta CAPI integration method (Gateway / direct / partner integration), event schema documentation, hosting infrastructure (Cloud Run / GCS / AWS) 2. Read `ads/references/conversion-tracking.md` for cross-platform baseline 3. Test event flow: trigger known events → verify they appear in BOTH client-side (Pixel Helper / Tag Assistant) AND server-side (Events Manager test events / GA4 DebugView) 4. Audit deduplication, hashing, and parameter completeness 5. Score health PASS / WARNING / FAIL per surface 6. Generate findings report ## What to Analyze ### Server-Side Google Tag Manager (sGTM) - **sGTM container deployed** — hosted on Cloud Run, GCS, App Engine, or custom infrastructure. Self-hosted preferred over Google-managed for cost and data residency - **Custom domain configured** (`tags.example.com`) — first-party domain avoids ITP / ad-blocker blocking that hits googletagmanager.com - **