Set up Meta Conversions API for a Bangladesh e-commerce site
Recover the 30–50% of conversion signal lost to iOS ATT and ad blockers. Walkthrough of server-side event tracking via Meta CAPI on a Next.js / Shopify / WooCommerce stack.
Set up Meta Conversions API for a Bangladesh e-commerce site
Tools
- · Meta Events Manager
- · Meta Business Suite
- · Server-side webhook
Prerequisites
- · Existing Meta Pixel installed
- · Server-side language access (Node, PHP, Python — any HTTP-capable runtime)
- · Access token from Meta Events Manager
Step-by-step
Generate a Conversions API access token
Meta Events Manager → Data Sources → your pixel → Settings → Set up manually → Generate access token. Store it in your server secrets (NEVER in client code).
Emit events server-side from purchase / lead routes
POST /v18.0/{pixel_id}/events with the same event_name + event_id you use client-side. Matching event_ids let Meta dedupe between browser + server events.
Hash all PII before sending
Email, phone, name fields must be SHA-256 hashed before sending. Meta's docs show the exact normalization (lowercase email, strip whitespace, etc.) — follow it exactly.
Verify event match quality in Events Manager
Wait 24 hours, then check Events Manager → Overview → Event Match Quality. Target ≥ 7.0; below 5.0 means your PII isn't matching Meta's user records.
Test before going live
Use Meta's Test Events feature to fire a sample event and confirm it lands. Don't enable CAPI ads-side optimization until match quality is verified.
In the glossary
Terms used.
Meta Conversions API (CAPI)
Server-to-server event tracking from your site/CRM to Meta's ad platform, used to recover conversion signal lost to iOS ATT and ad blockers.
Open
ROAS (Return on Ad Spend)
Revenue generated for every BDT spent on advertising. A ROAS of 4× means BDT 4 of revenue per BDT 1 of ad spend.
Open
CTR (Click-Through Rate)
The fraction of ad impressions that became clicks. Calculated as clicks ÷ impressions × 100.
Open
FAQ
Frequently asked.
- How long does Set up Meta… typically take?
- Roughly 1h for the steps in this playbook end-to-end, assuming the prerequisites are already in place.
- What do I need before I start?
- Existing Meta Pixel installed; Server-side language access (Node, PHP, Python — any HTTP-capable runtime); Access token from Meta Events Manager
- Can Public Pulse run this for me?
- Yes. This playbook is open documentation but we do this work for clients. Free 30-minute consultation to scope.