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.