server-side-conversion-tracking

Implements server-side conversion reporting to Facebook, TikTok, Google Ads, and Bing with click id passthrough.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill server-side-conversion-tracking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: server-side-conversion-tracking
Source: https://github.com/github/awesome-copilot/tree/main/skills/server-side-conversion-tracking
Command: npx skills add https://github.com/github/awesome-copilot --skill server-side-conversion-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browser pixels lose a large share of conversions to iOS tracking prevention, ad blockers, cookie limits, and cross-domain hops, so ad platforms under-report purchases and their bidding models learn from bad data. This Skill guides the full server-side tracking setup so reported conversions match real orders.

Core Features & Use Cases

  • Seven-step pipeline model: Capture click ids and UTMs on first hit, persist them server-side, carry them across funnel steps and domains, attach them to the order, report server-to-server, dedupe browser and server events, then verify against your own order table.
  • Platform-specific guidance: Covers Facebook Conversions API, TikTok Events API, Google Ads click conversion import, and Microsoft Bing CAPI, including credentials, click id parameters (fbclid, ttclid, gclid, msclkid), and PII hashing rules.
  • Verification checklist: Reconcile platform-reported conversions against your database, monitor click id coverage on paid orders, and use platform event debuggers before scaling spend.
  • Use Case: Your store records 45 orders but Facebook claims 40 and Google claims 30. Use this Skill to diagnose where click ids are being dropped, wire up server-side events with shared event ids, and stabilize the reporting ratio.

Quick Start

Ask the AI to set up server-side conversion tracking for your funnel so purchases are reported accurately to Facebook, TikTok, Google, and Bing despite ad blockers and iOS restrictions.

Frequently Asked Questions about server-side-conversion-tracking

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

FAQPage Schema
How do I set up server-side conversion tracking for Facebook and Google Ads?

Capture click ids (fbclid, gclid) and UTMs on the landing page, persist them in a server-side session, attach them to the order record, then send purchase events server-to-server via Facebook Conversions API and Google Ads click conversion import with hashed customer identifiers.

Why does Facebook report fewer purchases than my actual orders?

Browser pixels lose conversions to iOS tracking prevention, ad blockers, cookie lifetime caps, and cross-domain redirects. Server-side reporting through the Conversions API with click ids and hashed PII restores most of that lost reporting.

How do I deduplicate browser pixel and server-side conversion events?

Send the same event id on both the browser pixel event and the server event for each purchase. Facebook additionally matches on fbp and fbc cookie values. Without a shared event id you double-count conversions.

Does server-side tracking work across different domains in a funnel?

Yes, but click ids and UTMs must be forwarded explicitly in the redirect to the next domain and re-persisted there. A redirect that drops the query string destroys attribution for that campaign, which is where most funnels silently fail.

What are the limitations of server-side conversion tracking?

It improves conversion reporting and matching, not user-level cross-site identity resolution. Platform numbers still will not agree with each other due to differing attribution models, and consent and privacy requirements still apply to hashed PII sent server-side.