ads-server-side-tracking

Audits server-side tracking pipelines including sGTM, Meta CAPI, event deduplication, and PII hashing.

1|1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill ads-server-side-tracking-muhammaddadu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ads-server-side-tracking
Source: https://github.com/muhammaddadu/ai-skill-collection/tree/main/growth/ads-server-side-tracking
Command: npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill ads-server-side-tracking-muhammaddadu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Server-side tracking gaps from iOS ATT, ITP, and ad blockers cause 30-40% conversion data loss, leaving ad platform bid algorithms blind to real performance. This Skill audits the entire server-side measurement pipeline to find and score those gaps. ## Core Features & Use Cases - Pipeline Health Audit: Scores sGTM deployment, Meta CAPI / CAPI Gateway setup, event deduplication, server-side hit ratio, and PII hashing quality against defined PASS / WARNING / FAIL thresholds. - End-to-End Event Validation: Walks through Pixel Helper, Events Manager Test Events, Tag Assistant, and GA4 DebugView to confirm events fire on both client and server with matching event_id values. - Use Case: After noticing Meta reporting fewer purchases than your backend, run this audit to discover your dedup rate is 55% and EMQ is 5.2, then follow the generated EMQ improvement roadmap to fix parameter coverage. ## Quick Start Audit my server-side tracking setup covering sGTM, Meta CAPI, event deduplication, and hashing, then give me a health score and findings report.

Frequently Asked Questions about ads-server-side-tracking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit my server-side tracking setup?▼

Inventory your sGTM container, Meta CAPI integration method, and event schema, then trigger known events and verify they appear in both client-side tools (Pixel Helper, Tag Assistant) and server-side tools (Events Manager Test Events, GA4 DebugView). Score each surface against PASS / WARNING / FAIL thresholds.

What is a good Event Match Quality score for Meta CAPI?▼

An EMQ of 8.0 or higher for Purchase events is considered passing. Scores between 6.0 and 7.9 are a warning, and below 6.0 is failing. Improve EMQ by sending more customer_information parameters such as hashed email, phone, name, and fbc/fbp.

How does event deduplication work between Pixel and Conversions API?▼

Generate an event_id client-side and include it in both the Pixel event and the CAPI payload so Meta deduplicates the pair. Target a dedup rate of at least 90% in Events Manager Diagnostics, and keep server-side timestamps within 5 minutes of the client-side event.

What server-side hit ratio should I expect versus client-side?▼

Server-side hits should be at least 80% of client-side hits for Purchase and Lead events. Ratios above 100% are acceptable since server-side captures conversions the client missed, while drops below 60% indicate broken server-side firing or missing event_id values.

How should PII be hashed before sending to Meta CAPI?▼

Lowercase and trim emails and names, format phones as E.164, then apply SHA-256 before sending. Never double-hash values or send plain PII server-side, and confirm consent state is read before forwarding any hashed data for GDPR and CPRA compliance.

What is the difference between server-side tracking audit and attribution audit?▼

A server-side tracking audit examines the event collection pipeline itself: sGTM, CAPI, deduplication, and hashing. An attribution audit examines the model sitting on top of those events that assigns conversion credit across channels.