Lookalike Audiences<\/strong> from these groups. Meta finds new people who share characteristics with your best customers - this is often the most cost-effective way to scale Facebook and Instagram ads for a Shopify store.<\/p>\nConversions API: Why You Need It Too<\/h2>\n
The Meta Pixel runs in the visitor\u2019s browser, which means it\u2019s affected by ad blockers, cookie restrictions, and browser privacy settings like Safari\u2019s Intelligent Tracking Prevention. Over the past few years, this has caused gaps in tracking data for many store owners.<\/p>\n
The Conversions API (CAPI)<\/strong> solves this by sending event data from Shopify\u2019s server directly to Meta - bypassing the browser entirely. When you use both the pixel and CAPI together (called \u201credundant setup\u201d), Meta deduplicates the events and gives you the most complete picture of your ad performance.<\/p>\nGood news: if you install the Facebook & Instagram sales channel on Shopify, the Conversions API is included and configured automatically. No extra setup needed.<\/p>\n
iOS 14.5+ ATT and What It Does to Your Meta Pixel Data<\/h2>\n
If you\u2019re running ads to iOS users (which for most consumer Shopify stores is 40-60% of traffic), the Meta Pixel does not work the way it did before April 2021. Apple\u2019s App Tracking Transparency (ATT) framework - the prompt that asks \u201cAllow [App] to track your activity?\u201d - radically changed what data Meta receives from Safari and the Facebook iOS app. The numbers matter:<\/p>\n
\n- Roughly 70-85% of iOS users opt out of tracking<\/strong> when prompted, depending on the app and category. That means for those users, the browser pixel essentially can\u2019t attribute events back to the Meta ad they saw.<\/li>\n
- Attribution windows are capped at 7 days click and 1 day view<\/strong> for iOS users - down from the previous 28-day click default. Conversions outside that window simply don\u2019t appear in Ads Manager.<\/li>\n
- Aggregated Event Measurement (AEM)<\/strong> replaces direct event tracking for iOS users. AEM lets you track up to 8 prioritized events per domain, and it sends those events back as aggregated, time-delayed data rather than per-user real-time signals.<\/li>\n<\/ul>\n
What you actually need to do:<\/strong><\/p>\n\n- Verify your domain in Meta Business Manager.<\/strong> Without domain verification, you can\u2019t configure AEM at all. Go to Business Settings > Brand Safety > Domains<\/strong>, add your Shopify store domain, and verify via DNS TXT record (Shopify\u2019s DNS settings make this a 5-minute job).<\/li>\n
- Configure your 8 prioritized events.<\/strong> In Events Manager, go to Aggregated Event Measurement<\/strong> and set the order: Purchase first (highest priority), then InitiateCheckout, AddToCart, ViewContent, and so on. Meta uses event #1 for any iOS user who would otherwise not be tracked at all, then falls back through the priority list.<\/li>\n
- Accept the data is incomplete.<\/strong> For iOS users, your Ads Manager numbers are modeled estimates plus actual events from opted-in users. Don\u2019t expect Ads Manager and Shopify Analytics to match exactly anymore - they won\u2019t, and the gap is structural, not a bug.<\/li>\n
- Use the Conversions API to recover what you can.<\/strong> CAPI sends events server-side from Shopify directly to Meta, bypassing the browser entirely. For iOS users, CAPI doesn\u2019t bypass ATT (Meta still respects the opt-out signal at the modeling layer), but it does fix the cases where ad blockers, browser extensions, or Safari ITP would have dropped events. The recovered fraction varies - typically 10-25% of events that the browser pixel would have lost - and the Event Match Quality score in Events Manager tells you how well CAPI is doing.<\/li>\n<\/ol>\n
The honest bottom line:<\/strong> Meta Pixel data on iOS is approximately right, not exactly right. Plan media decisions on directional trends and CAC math, not on event-level attribution that hasn\u2019t worked at the per-user level for years. Stores still using last-click attribution from a browser pixel alone are running on outdated data.<\/p>\nConversions API Setup Checklist (The Practical Version)<\/h2>\n
Most articles say \u201cyou should also use the Conversions API\u201d and stop there. Here\u2019s the actual setup, in order, for a Shopify store using the native Facebook & Instagram sales channel.<\/p>\n
Step 1: Confirm CAPI is already running through the native sales channel.<\/strong> Install the Facebook & Instagram sales channel from the Shopify App Store if you haven\u2019t. Once connected, CAPI is enabled by default - you don\u2019t have to install a separate app. Verify in Meta Events Manager: open your pixel, click Settings<\/strong>, scroll to Conversions API<\/strong>, and confirm you see \u201cActive\u201d with recent server events listed.<\/p>\nStep 2: Verify event deduplication is working.<\/strong> When both the browser pixel and CAPI send the same event, Meta needs to deduplicate them. The deduplication key is the event_id<\/code> field that the native integration sends automatically. Check this in Events Manager: open the Test Events tool, click through your store, and watch for events labeled Server & Browser<\/strong> (deduplicated) versus Server only<\/strong> or Browser only<\/strong>. If you see large counts of un-deduplicated events, the integration isn\u2019t passing event_id correctly - usually fixed by reinstalling the sales channel.<\/p>\nStep 3: Improve Event Match Quality.<\/strong> In Events Manager, each event has an Event Match Quality (EMQ) score from 0-10. Above 7 is healthy; below 6 means Meta can\u2019t match many events to user profiles, so attribution suffers. The native Shopify integration sends customer email and phone (when available) hashed automatically. To raise EMQ further:<\/p>\n\n- Encourage logged-in checkout (the customer\u2019s saved email is sent with every event automatically).<\/li>\n
- Use Shop Pay where possible (customer identity is verified, so events match cleanly).<\/li>\n
- If your store has a newsletter signup, add it before checkout flows where it makes sense - that captured email then attaches to subsequent events.<\/li>\n<\/ul>\n
Step 4: Don\u2019t run two CAPI integrations at once.<\/strong> If you\u2019ve installed the native Facebook & Instagram sales channel AND a third-party CAPI app (like Trackify or Pixel Perfect Pro), you\u2019ll get duplicate server events that Meta can\u2019t deduplicate properly. Pick one. The native integration is sufficient for most stores. Third-party apps add value mainly for stores with custom event needs (subscription stages, complex multi-step funnels) that the native integration doesn\u2019t capture.<\/p>\nStep 5: Wait 7 days before judging the data.<\/strong> CAPI events take longer to populate Ads Manager than browser pixel events (sometimes 1-3 hours of delay; more during peak load). Don\u2019t run a comparison the day after enabling. Give it a week, then compare your Shopify Purchase count to Meta\u2019s Purchase count for the same period. If Meta is reporting 80-95% of Shopify\u2019s purchases, CAPI is working well. If under 70%, dig into deduplication and EMQ.<\/p>\nCommon reasons CAPI numbers stay low:<\/strong><\/p>\n
![\"Facebook](\"https:\/\/shopthemedetector.com\/blog\/wp-content\/uploads\/2020\/02\/facebook-pixel-e1580997712837.png\")
<\/p>\n