Oct 19, 2026
Written by
Ivanna Holubovska
Shopify tracking gets harder every year. Browser restrictions and ad blockers create gaps in conversion data, leading to missed events and underreported results, even when campaigns look healthy in your analytics.
Meta Conversions API (CAPI) fixes this by sending event data directly from your server, bypassing browser limitations entirely and giving Meta the signal quality it needs to optimize your ads.
There are two main ways to connect Facebook CAPI with Shopify:
This guide explains how to set up Meta CAPI using both methods and how to verify that events are being sent correctly.
Key benefits of implementing Meta CAPI for Shopify:
| Stape + GTM (manual) | Setup Wizard | Native Shopify | |
|---|---|---|---|
| Setup time | Standard | Fast | Fast |
| Technical skill | GTM knowledge required | Minimal | Minimal |
| Event data control | Full | Full | Limited by Shopify |
| Custom events | Yes | Yes | No |
| Event Match Quality | High | High | Moderate (7–8 / 10) |
2. Add and configure Stape's Conversion Tracking app for Shopify
Here's a step-by-step guide about server-side tagging for Shopify, where you can find more information about the implementation.
3. Send data to the server Google Tag Manager container. There are three most popular ways to do that:
4. Configure Facebook CAPI inside server Google Tag Manager.
Facebook tags by Stape have two behaviors: Inherit from the client and Override. If you select the inherit option, the FB CAPI tag will listen to the event data and try to parse and map all data it can identify and send to the meta. If you select override, then you must manually specify all the parameters. Below are examples of configuring FB CAPI for each of these tag behaviors.
1. Open the web and server GTM containers debugger and click through your site. In the server GTM container, you should see events fired by the Facebook Conversions API tag.

2. You can test this event inside the Facebook testing tool as well.

Once your Meta CAPI setup is live, don't skip verification. Shopify's sandboxed checkout means tags can appear to work in GTM preview while failing silently in production – causing missed or duplicate events in Meta. For a step-by-step validation process, read: Debugging Shopify tracking with web and server GTM: a complete guide.
The Setup Wizard simplifies implementation into four steps, from identifying your website platform to generating and importing your tracking setup into Google Tag Manager.
1. Scan your website. The Setup Wizard automatically identifies that your website is built on Shopify and tailors the next steps to your store for a smooth tracking setup. Once the scan is complete, click Next.
2. Choose your platforms. In the list of data destinations, select Meta as the platform you want to configure tracking for and click Next.
3. Add your platform IDs. Enter the required platform and conversion IDs from your accounts. Once the values are added, click Next.
4. Generate and import your setup. Generate your tracking setup and automatically import it into your web and server GTM containers.
Need help configuring the Setup Wizard?
Follow our Setup Wizard configuration guide for detailed instructions on generating and importing your tracking setup.
1. In your Shopify admin, go to Settings → Sales Channels, and get the Facebook & Instagram app from the Shopify App Store. Install it.

2. Open the installed app and click Get Started. This will allow you to link your store with your Facebook account.

3. Connect the existing entities or create new ones.

4. When you create the new catalog, set Share Preference to Standard, Enhanced, or Maximum, depending on your needs and privacy policy requirements. After you save this setting, click Create New near the chosen data set.

5. Finish configuration, accept terms, and send it all for review, which may take several minutes.
1. Check browser-side Meta Pixel events. Install Meta Ads Data Advisor, formerly Meta Pixel Helper, and open your Shopify storefront in Chrome. Temporarily disable ad blockers and, if required, accept marketing cookies before testing. Open the extension, confirm that the Pixel ID matches the pixel connected in Shopify, and perform these actions:
PageView.ViewContent.AddToCart.InitiateCheckout.Purchase.
Review detected events for warnings, unexpected duplicates, and accurate product identifiers, values, and currencies where applicable.
2. Check event delivery in Meta Events Manager. Open Meta Events Manager, select your store's data source, and confirm that its Pixel ID matches the one checked in Step 1.

Use Test Events where supported, but note that server events appear there only if the integration sends a test event code. Review the event overview and Diagnostics as well, allowing time for processed data to appear. Start by checking server-side Purchase delivery; do not assume that every browser event also has a server counterpart.
3. Verify purchases and deduplication. Complete a purchase through your storefront checkout and record its time, value, and currency to help identify it in Events Manager. Confirm that the purchase parameters are correct and that browser and server events are received when both are expected. Corresponding browser and server events should share the same event name and event ID for deduplication, while separate purchases should have different IDs. Review deduplication information and Diagnostics, and investigate additional tracking installations if duplicate events appear.

4. Review customer matching and data quality. Review Event Match Quality once enough server-event data is available, and use Meta's recommendations to investigate missing or incorrectly formatted customer information. No single score proves that tracking works correctly, so check event delivery, parameters, and deduplication separately.
1. In this thread, a user setting up the Facebook Conversions API for Shopify couldn't get their purchase event to trigger, even after adding custom code to the checkout page. In the full thread, the issue was traced to an incorrect trigger in Google Tag Manager – the user had set it to fire on "gtm.js" instead of "purchase." After switching the trigger to the correct event name, the purchase event fired properly and the Facebook Conversions API for Shopify setup worked as intended.
2. A Shopify store using Facebook Conversion API for Shopify via Stape faced failed purchase events in server-side GTM and no test events showing in Meta. The issue was not Stape itself, but an incomplete setup: events were reaching the server, but Facebook wasn't receiving browser-side data. The fix was to use hybrid tracking — set up both the Facebook Pixel in the web GTM container and the Facebook CAPI tag in the server container. Facebook then automatically deduplicates events, server-side errors disappeared, and events showed correctly in Meta Event Manager.
Overall, Shopify users have various options when it comes to integrating Facebook's conversion API. We've discussed each possibility thoroughly and explored how to deploy the Facebook conversion API for Shopify using the Stape Conversion Tracking app.
Take the time to review your business needs and use cases before determining which integration is best for you. Then, whether you choose a manual solution or rely on automation, implementing the Meta Conversions API will give your company additional insights into customer behaviors, help optimize campaigns, and deliver more engaging experiences for your customers.
To get started quickly and achieve the best results, we recommend trying the Conversion Tracking app, which provides an easy-to-use implementation option.
Want to start on the server side?
Try for freeOct 19, 2026
Aug 27, 2026
Sep 15, 2026
Solutions
Easily add GTM to Shopify & improve tracking! The Stape Conversion Tracking app offers Cookie Keeper, dataLayer events, webhooks, and custom domain support.
Oct 28, 2026
Comments