If you run Facebook ads for your boutique Shopify, you have probably noticed that rapported performance has deteriorated since Apple's iOS 14+ privacy changes rolled out. Conversions appear lower, ROAS seems worse, and your ad optimization feels less effective. The problem is not necessarily that your ads are performing worse — it is that your tracking is missing a large portion of conversions.

The Facebook Pixel is a JavaScript snippet that runs in the visiteur's browser. When an iOS user opts out of tracking (which 75-85% now do), the Pixel cannot fire. When a visiteur uses an ad blocker, the Pixel is blocked. When third-party cookies are restricted (increasingly the default), the Pixel's ability to match users degrades. The result: Facebook sees fewer conversions, attributes less chiffre d’affaires to your ads, and optimisers your campaigns based on incomplete données.

API de Conversions Facebook (CAPI) solves this by sending conversion events directly from your Shopify server to Facebook's servers. No browser involved, no JavaScript to block, no cookie to restrict. When a client completes a achat on your boutique Shopify, Shopify sends the achat event to Facebook server-to-server, along with client données (email, phone, IP address) that Facebook uses to match the conversion to the ad click that initiated it.

This guide walks through the complete CAPI setup for Shopify, explains how event deduplication works, and covers how your on-site outils (popups, upsells, and other apps) interact with server-side tracking.

How API de Conversions Facebook Works

The Conversions API is a server-side integration that allows you to send web events directly from your server to Facebook. Instead of relying on a browser-based pixel that runs JavaScript on the user's device, CAPI makes HTTPS POST requests from your server to Facebook's Graph API endpoint.

When a client takes an action on your boutique Shopify — views a product, adds to cart, initiates checkout, or completes a achat — two things happen simultaneously in a properly configured setup:

  1. Browser-side (Pixel): The Facebook Pixel JavaScript fires in the visiteur's browser and sends the event to Facebook. This works for visiteurs who have not blocked tracking.
  2. Server-side (CAPI): Shopify's server sends the same event directly to Facebook via the Conversions API. This works regardless of the visiteur's browser settings, iOS version, or ad blocker status.

Facebook receives both events, uses event deduplication to count them as a single conversion (not double), and uses the server-side données to fill gaps where the pixel was blocked. The result is more complete conversion données, better attribution, and more effective ad optimization.

Pixel vs CAPI: Understanding Both Systems

Fonctionnalité Facebook Pixel Conversions API
How it sends données Browser JavaScript Server-to-server HTTPS
Blocked by iOS 14+ Yes (for opted-out users) No
Blocked by ad blockers Yes No
Affected by cookie restrictions Yes No
Tracks browsing behavior Yes (PageView, scroll, etc.) Limited (server-triggered events)
Données accuracy 60-80% (declining) 95%+ (server-verified)
Setup difficulty Easy (paste code snippet) Moderate (Shopify handles most)
Recommended use Always on (alongside CAPI) Always on (alongside Pixel)

iOS 14+ Impact on Facebook Ad Tracking

Apple's App Tracking Transparency (ATT) framework, introduced with iOS 14.5 in April 2021, fundamentally changed how Facebook advertising works. Here is what happened and why CAPI is now essential:

What Changed

Before iOS 14, the Facebook app on iPhones could track user activity across apps and websites using Apple's IDFA (Identifier for Advertisers). This allowed Facebook to see when someone who clicked an ad later achatd on your website, even across sessions and devices. When Apple required apps to ask permission before tracking, 75-85% of iOS users chose to opt out.

Impact on Shopify Advertisers

  • Under-rapported conversions: Facebook cannot see achats from opted-out iOS users via the Pixel. A store with 50% iOS traffic might see 20-40% of conversions disappear from Facebook rapporting.
  • Degraded ad optimization: Facebook's algorithm learns from conversion données. With less données, it makes worse decisions about who to show your ads to, leading to higher CPAs and lower ROAS.
  • Attribution window reduction: Facebook shortened the default attribution window from 28 days to 7 days, further reducing rapported conversions.
  • Limited event tracking: iOS 14+ limits each domain to 8 prioritized conversion events, down from unlimited events before.

How CAPI Fixes These Issues

CAPI bypasses all browser-level restrictions because it sends données server-to-server. When a client completes a achat, Shopify sends the achat event to Facebook directly, along with client information (hashed email, phone number, and IP address) for user matching. Facebook can then attribute the achat to the original ad click, even for opted-out iOS users.

💡 Données Récupérery: boutiques Shopify that implement CAPI alongside the Pixel typically récupérer 15-30% of previously unrapported conversions. This does not mean ventes augmenterd — it means Facebook can now see (and optimiser for) ventes that were happening but invisible. Better données leads to better optimization, which leads to genuinely améliorerd performance over time.

Setting Up CAPI on Shopify (Étape-by-Étape)

Shopify has made CAPI setup straightforward through its Facebook & Instagram ventes channel. No custom coding is required for the standard implementation.

Étape 1: Install the Facebook & Instagram Channel

In your tableau de bord Shopify, go to Ventes channels → Add channel → Facebook & Instagram. If you already have this channel installed, make sure it is updated to the latest version.

Étape 2: Connect Your Facebook Business Manager

Follow the setup wizard to connect your Facebook Business Manager account. You will need to authenticate with a Facebook account that has admin access to the Business Manager. Select the correct Ad Account, Facebook Page, and Pixel to connect.

Étape 3: Enable Conversions API

In the Facebook & Instagram channel settings, navigate to the Données sharing section. You will see three données sharing levels:

  • Standard: Uses Facebook Pixel only (browser-side tracking).
  • Enhanced: Uses Facebook Pixel with additional browser-side données matching.
  • Maximum: Uses both Facebook Pixel and Conversions API (recommended). This is the setting you want.

Select Maximum to enable CAPI. Shopify will automatically configure server-side event sending for all standard e-commerce events.

Étape 4: Verify Domain

Domain verification is required for proper CAPI and Aggregated Event Measurement (AEM) functionality. In Facebook Business Manager, go to Business Settings → Marque Safety → Domains. Add your Shopify domain and verify it using the DNS TXT record method or HTML meta tag method. Shopify's Facebook channel often handles this automatically.

Étape 5: Configure Aggregated Event Measurement (AEM)

After domain verification, configure your 8 prioritized events in Events Manager. Go to Events Manager → Aggregated Event Measurement → Configure Web Events. Set your events in priority commande (highest to lowest):

  1. Achat
  2. InitiateCheckout
  3. AddToCart
  4. ViewContent
  5. Lead (if you collect email signups)
  6. AddPaymentInfo
  7. Search
  8. PageView

Events and Event Matching

CAPI sends events to Facebook using client matching parameters. The more parameters you provide, the higher the match rate — meaning Facebook can more accurately attribute conversions to ad clicks.

Key Matching Parameters

  • Email address (hashed) — the strongest matching signal. Available when clients provide their email at checkout or through signup forms.
  • Phone number (hashed) — another strong signal, especially for mobile conversions.
  • IP address — helps match anonymous browsing sessions to known users.
  • User agent — browser and device information used for probabilistic matching.
  • fbclid — the Facebook click ID parameter appended to URLs when users click ads. The strongest deterministic matching signal when available.
  • fbc and fbp cookies — Facebook browser cookies that Shopify can access and pass to CAPI.

Shopify's CAPI implementation automatically sends all available matching parameters. For achat events (where the client has provided their email and phone at checkout), match rates typically exceed 90%. For earlier funnel events (PageView, ViewContent), match rates are lower because less client données is available.

Event Deduplication: Avoiding Double-Counting

When both the Pixel and CAPI send the same event, Facebook needs to know they represent the same action, not two separate actions. This is handled through event deduplication using an event_id parameter.

When Shopify sends a Achat event, both the Pixel and CAPI include the same event_id (typically the Shopify commande ID). Facebook sees both events, matches them by event_id, and counts them as a single conversion. If only one arrives (because the Pixel was blocked), Facebook counts the CAPI event alone.

Shopify's built-in integration handles deduplication automatically. If you are using custom CAPI implementations or third-party tracking apps, ensure they use the same event_id format as your Pixel events to avoid double-counting.

Testing Your CAPI Setup

After setup, verify that CAPI is working correctly before relying on its données for optimization decisions.

Use Facebook's Test Events Tool

In Events Manager, go to Test Events. This shows real-time events as they arrive from both the Pixel and CAPI. Visit your boutique Shopify, view a product, ajout au panier, and complete a test achat. You should see events from both "Browser" (Pixel) and "Server" (CAPI) sources.

Check Event Match Quality

In Events Manager, navigate to the Aperçu tab and check the Event Match Quality (EMQ) score for each event. This score (1-10) indicates how well your server events can be matched to Facebook users. Aim for a score of 6 or higher. Scores below 4 indicate missing client parameters.

Verify Deduplication

In the Test Events view, check that duplicate events are being properly deduplicated. You should see a "Deduplicated" label on matching Pixel/CAPI event pairs. If events are not being deduplicated, check that both sources are using the same event_id.

Monitor the Diagnostics Tab

Events Manager's Diagnostics tab flags issues with your setup — missing parameters, high error rates, or deduplication problems. Check this tab weekly for the first month after setup, then monthly after that.

How CAPI Works With Popups, Upsells, and Other Apps

If you use applications Shopify like EA Roue de la Fortune Popup Email for email collection or EA Upsell & Vente Croisée for upsells, you might wonder how these interact with CAPI tracking.

Popup Email/SMS Signups

When a visiteur submits their email through a popup roue de la fortune, this is typically tracked as a Lead or CompleteRegistration event by the Facebook Pixel (browser-side). CAPI does not natively capture this event because it happens before checkout. However, when that visiteur later achats, the email they provided at signup is sent to Facebook via CAPI as a matching parameter, improving the match rate for the achat event.

In this way, popups actually améliorer CAPI performance — by collecting client email addresses earlier in the journey, you provide Facebook with a stronger matching signal for the eventual achat event.

Upsell and Vente Croisée Achats

When a client accepts an upsell offer and adds an additional product to their commande, the final achat event captured by CAPI reflects the total commande value, including any upsell items. Facebook sees the full chiffre d’affaires from the conversion, which améliorers your rapported ROAS. This is one reason why upsell apps like EA Upsell & Vente Croisée are particularly valuable for Facebook advertisers — they augmenter the chiffre d’affaires attributed to each Facebook-driven achat.

Barre de Livraison Gratuites and Other Conversion Outils

On-site conversion outils like barre de livraison gratuites, sticky ajout au panier buttons, and comptes à rebours operate independently of CAPI. They influence the visiteur's behavior on your store (increasing the likelihood and size of a achat), and CAPI captures the resulting achat event with the full commande value. Better on-site conversion means more achat events for Facebook's algorithm to optimiser against.

💡 Stack Effect: The combination of CAPI (for accurate tracking) and on-site conversion outils (for higher taux de conversion and AOV) creates a compounding effect. More complete conversion données means Facebook optimisers better, and higher taux de conversion mean each ad click generates more chiffre d’affaires. Stores using both see 25-40% better Facebook ROAS than stores using neither.

Optimizing CAPI for Maximum ROAS

Once CAPI is set up and verified, these optimizations squeeze more value from your Facebook advertising:

  1. Maximiser event match quality. Send as many client parameters as possible — email, phone, name, city, state, zip code. Shopify sends most of these automatically for achat events. For earlier funnel events, collecting email through popups provides additional matching signals.
  2. Use value-based optimization. With accurate achat données from CAPI, enable value-based bidding in your Facebook campaigns. This tells Facebook to optimiser for highest-value achats, not just any achat, improving ROAS.
  3. Monitor event match quality weekly. A drop in EMQ score often indicates a technical issue — check that the Facebook channel is properly connected and all matching parameters are being sent.
  4. Keep the Pixel and CAPI running simultaneously. Do not remove the Pixel when you add CAPI. The Pixel still captures real-time browsing signals that CAPI cannot (scroll depth, time on page, micro-interactions) which help Facebook build richer audience profiles.
  5. Prioritize your conversion events correctly. Under AEM, arrange your 8 events with Achat as the highest priority. Facebook will always attempt to capture the highest-priority event for each user within the 7-day attribution window.
  6. Use UTM parameters inconvénientsistently. While CAPI handles Facebook attribution, UTM parameters help you verify Facebook's rapported données against your own analytics (GA4, Shopify Analytics) for a more complete performance picture.

Common CAPI Issues and Solutions

Issue: Event Match Quality score is low (below 4). Ensure Shopify's Facebook channel is set to "Maximum" données sharing. Check that client email and phone fields are populated at checkout. Inconvénientsider collecting emails earlier via popup forms to améliorer matching.

Issue: Events are being double-counted. Check that event deduplication is working by verifying event_id inconvénientsistency between Pixel and CAPI events. If using a third-party tracking app alongside Shopify's built-in channel, you may have conflicting implementations.

Issue: CAPI events show in test mode but not in production. Ensure your Facebook channel is fully connected and not in a disconnected or error state. Go to the channel settings and re-authenticate if needed. Check for any API errors in the Diagnostics tab.

Issue: Rapported conversions still seem too low. CAPI récupérers most but not all lost conversions. Some données loss is permanent under iOS ATT. Focus on trends rather than absolute numbers — if your ROAS trend améliorers after CAPI implementation, it is working correctly.

Questions fréquemment posées

Qu’est-ce que API de Conversions Facebook for Shopify?

API de Conversions Facebook (CAPI) is a server-side tracking method that sends conversion events directly from Shopify's servers to Facebook. Unlike the Facebook Pixel which runs in the visiteur's browser and can be blocked by iOS privacy settings, ad blockers, and cookie restrictions, CAPI sends données server-to-server and cannot be blocked. It récupérers 20-40% of conversion données lost to iOS 14+ privacy changes.

How do I set up API de Conversions Facebook on Shopify?

Install Shopify's Facebook & Instagram ventes channel. Connect your Facebook Business Manager. In the channel's Données Sharing settings, select "Maximum" to enable both Pixel and CAPI. Verify your domain in Facebook Business Manager. Configure your 8 prioritized events under Aggregated Event Measurement. Shopify handles all server-side event sending automatically — no coding required.

Does Facebook CAPI replace the Facebook Pixel?

No. CAPI works alongside the Pixel, not as a replacement. The recommended setup uses both simultaneously. The Pixel captures browser-side events from non-iOS users and provides real-time browsing signals. CAPI captures conversions from iOS users and ad-blocker users that the Pixel misses. Facebook deduplicates matching events using event_id to avoid double-counting.

Why is my Facebook ad ROAS dropping after iOS 14?

iOS 14+ App Tracking Transparency requires apps to ask permission before tracking, and 75-85% of users opt out. Without CAPI, the Facebook Pixel cannot see these users' conversions, causing artificially deflated ROAS numbers. Your ads may be performing better than rapported. Setting up CAPI récupérers the lost données, giving Facebook more accurate numbers to rapport and optimiser against.

Do popups and upsells track through API de Conversions Facebook?

Popup interactions (like email signups from EA Popup Roue de la Fortune) are typically tracked by the Pixel as Lead events. CAPI handles the achat event server-side. When popups collect email addresses, they actually améliorer CAPI performance by providing Facebook with a matching parameter for the eventual achat. Upsell chiffre d’affaires is included in the total achat value captured by CAPI.

Booster Your Facebook ROAS With Better Taux de Conversion

Accurate tracking with CAPI is étape one. Étape two is convertiring more of your Facebook traffic. EA apps augmenter taux de conversion, AOV, and email capture — all of which améliorer your Facebook ad performance. Gratuit to install.

Browse All EA Apps — Gratuit