ads-server-side-tracking

Audit server-side advertising pipelines to diagnose conversion data loss.

8|5|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/shenxingy/Clade --skill ads-server-side-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ads-server-side-tracking
Source: https://github.com/shenxingy/Clade/tree/main/configs/skills/ads-server-side-tracking
Command: npx skills add https://github.com/shenxingy/Clade --skill ads-server-side-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you identify and fix data loss and mismatches in your server-side ad tracking pipeline so your modeled conversions remain accurate despite iOS ATT, ITP, and ad blockers.

Core Features & Use Cases

  • End-to-end pipeline audit of sGTM, Meta CAPI / CAPI Gateway, and event flow from client to server using controlled test events.
  • Deduplication and event_id validation to ensure the same canonical events are deduped correctly across Pixel and CAPI.
  • PII hashing and compliance discipline checks that server-side forwarding uses the correct hashing conventions and never sends plain PII.
  • Actionable health scoring and reporting that outputs a full findings document plus an EMQ improvement roadmap and hit-ratio recommendations.

Quick Start

Use the ads-server-side-tracking skill to audit your server-side pipeline by validating the full event flow and producing a health report with PASS/WARNING/FAIL findings.

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 server-side tracking reliability for Meta CAPI and sGTM?

To audit server-side tracking reliability, you validate the full event flow from client to server using controlled test events, then score health against defined thresholds to output a PASS/WARNING/FAIL findings document.

Why does event deduplication fail between my Pixel and Meta Conversions API?

Event deduplication fails when Pixel and CAPI lack consistent event schemas or matching event_id parameters. You can validate deduplication by cross-referencing conversion-tracking baselines and reproducing test events end-to-end.

How do I verify PII hashing in server-side GTM without sending plain data?

You verify PII hashing in server-side GTM by checking that forwarding uses correct hashing conventions and never sends plain PII, ensuring your measurement pipeline maintains compliance discipline.

Can I use server-side tracking to fix conversion data loss from iOS ATT and ad blockers?

Yes, server-side tracking fixes conversion data loss from iOS ATT, ITP, and ad blockers by routing measurement through a server pipeline, which you can audit to identify mismatches and restore modeled conversion accuracy.

What's the best way to diagnose conversion data loss in my ads tracking pipeline?

The best way to diagnose conversion data loss is auditing the server-side advertising measurement pipeline, cross-referencing baselines, and scoring hit ratio performance to produce an EMQ improvement roadmap.

Does server-side tracking require event_id parameters for purchase and lead measurement?

Yes, server-side tracking requires event_id parameters for purchase and lead measurement to ensure the same canonical events are deduped correctly across Pixel and CAPI implementations.