Shopify's native Meta integration is the easiest path to Conversions API. Here's how to set it up correctly — including the deduplication step most stores skip.
Why CAPI matters in 2026
iOS 14.5+ + ad blockers + ITP cookie restrictions mean roughly 30–40% of your iOS traffic never reports back to Meta via the standard pixel. CAPI is the server-side fallback that recovers most of that signal.
Step 1: Connect Shopify to Meta Business Manager
In Shopify admin, go to Online Store → Preferences → Customer events. Connect your Meta Business account and select the pixel you want to use. Shopify will automatically install both browser pixel + server-side CAPI events.
Step 2: Verify in Test Events
Open Meta Events Manager → Test Events. Make a test purchase. You should see two events — one labeled "Browser" and one "Server". The deduplication ID should match between them.
Step 3: Common deduplication issue
If Meta shows the same event twice (Purchase × 2), the dedup key isn't matching. Usually because:
- You also have a third-party pixel app installed (Pixel Perfect, Trackify) that fires its own pixel without sharing the event_id.
- Theme code includes a hard-coded pixel block from a previous setup.
Fix: disable the third-party app's pixel firing OR remove the theme block. Stick with one source.
Step 4: Advanced Matching
Shopify's native integration doesn't push hashed PII (email, phone, name) to Meta by default in all regions. Enable "Maximum data sharing" in Customer events for higher EMQ scores.
When to escalate to GTM-based setup
If you need fine-grained control — custom event values, dynamic product IDs, or multi-pixel routing — Shopify's native integration runs out. We rebuild through GTM in those cases.
