ChecklistAnalyticsEcommerceMeta Ads

Shopify Pixel + CAPI Checklist: EMQ, Dedup and Event QA

A Shopify-specific Meta Pixel and Conversions API checklist: channel settings, standard events, shared event_id dedup, user-data for EMQ, consent, and Events Manager pass/fail.

Updated 2026-08-2411 min read

A Shopify store with a Pixel and no Conversions API is flying on whatever the browser still sends. This checklist is the dual-setup gate: channel settings, events, shared event_id, match-quality fields, consent, and the Events Manager reads before you scale spend.

Pixel and CAPI are one event, two pipes

The browser Pixel catches people the page can see. The Conversions API catches the same conversion when the browser cannot — ITP, ad blockers, iOS prompts, checkout on a thank-you page that dropped cookies. You run both. Meta deduplicates on event_name plus event_id for a limited window (treat 48 hours as the working rule). If Shopify's sales channel and a second app both fire Purchase without the same event_id, you will double-count or drop events and then 'optimise' a lie. One Pixel ID per storefront you actually advertise. Two Pixels 'just in case' is how diagnostics go to noise. The thank-you page is not the only Purchase: checkout extensions, Shop Pay, and upsell apps each need a plan.

EMQ is a parameter problem, not a Pixel-install problem

Event Match Quality scores how well an event can be matched to a Meta account: hashed email and phone do the heavy lifting, then name, location, external_id, fbp, fbc, IP and user agent. A store that shares 'email only when the customer opts into marketing' will look worse than a store that shares checkout identifiers they already hold, inside the law and their CMP. Turn the Facebook & Instagram channel customer data-sharing up to the highest setting you are allowed to use. If EMQ on Purchase sits in the basement, do not buy another creative test until hashed em/ph and click IDs are actually on the server event. Creative cannot fix a user_data object that is empty.

QA in Events Manager, not in Ads Manager CPA

CPA will look 'fine' on duplicated purchases and 'broken' on under-reported ones; neither teaches you the Pixel. Test a real checkout, confirm the event fires once per order, confirm value and currency match the order, confirm event_id is stable on refresh, and confirm CAPI coverage is not a sliver of browser volume. If you cannot see a Purchase from the last 24 hours after a test order, you do not have tracking. Klip Kanvas is not in this path — it makes the ads; this sheet is the store plumbing those ads report into. Do not launch a 3×2 creative grid on a hope.

How to use the tables below

Work top to bottom as a red/green sheet before the first dollar of a creative test. Channel and Pixel first — one ID, maximum allowed customer-data sharing, catalog IDs that match. Events and shared event_id second: a refresh must not mint a new Purchase id. User_data and EMQ third: hashed email and phone on the server event, fbp/fbc surviving checkout. Consent and extra apps fourth, then the Events Manager pass/fail on a real test order from the last 24 hours. A red row blocks spend even if creative is ready. Two CAPI apps without a shared event_id is a launch fail, not a 'belt and suspenders' setup. Value and currency must match the order definition you will live with.

5 checklists inside: Shopify channel and Pixel install, standard events with shared event_id, dedup and coverage rules, user_data and EMQ fields, then Events Manager plus consent and extra-app pass-fail gates.

Locked

Unlock the full cheatsheet

Enter your email and we'll instantly unlock the complete cheatsheet — plus send you fresh ad playbooks every month.

No spam. Unsubscribe anytime.

Ready to put this into practice?

Create your first AI UGC video ad in minutes — no filming, no actors, no editing.

Try Klip Kanvas free

More in this section

Ready to make ads like these?

Paste a product link and Klip Kanvas writes the script, casts the creator and renders the ad — no filming, no actors, no editing.