Meta Conversions API — Server-Side Tracking Setup

Tools Used: Google Tag Manager · Cloudflare Workers · Facebook Events Manager
Website: sakibh.work | Status: ✅ Live

What I Did

I personally set up Meta Conversions API (Server-Side Tracking) on my own website sakibh.work as a live working example of advanced ad tracking.

This setup sends Facebook ad data directly from the server — bypassing ad blockers and iOS privacy restrictions that block normal pixel tracking.

The Problem I Solved

Normal Facebook Pixel gets blocked by ad blockers and browser privacy settings, causing up to 40% data loss — making ad campaigns less accurate and wasting ad spend.

How I Built It

• ✅ Configured Google Tag Manager with a Custom HTML tag to fire on every page visit
• ✅ Built and deployed a Cloudflare Worker (sakibh.work/capi) to receive and forward events server-side to Meta
• ✅ Set up SHA-256 hashing inside the Worker for user data privacy
• ✅ Tracked events: PageView (standard) + 40s_stay (custom event)
• ✅ Implemented event deduplication so browser + server data doesn’t get double-counted

Results on My Own Website