CAPI Shield is a free Make.com scenario that takes each paid Shopify order from a webhook and sends it to Meta's Conversions API as a Purchase event, so iOS, Safari and ad blockers cannot stop it. This page is the setup. If your Meta results dropped and you do not yet know why, start with the ROAS guide.
Questions this guide answers
What is the Shopify CAPI?
The Shopify CAPI refers to server-side Conversions API implementation for Shopify: sending purchase events from Shopify's servers directly to Meta CAPI, Google Enhanced Conversions, or TikTok Events API. It bypasses iOS privacy restrictions and ad blockers that block browser pixel tracking, covering purchase events that would otherwise be missed.
What is Shopify server-side tracking?
Server-side tracking sends Shopify conversion events directly from your server to ad platforms, bypassing the browser entirely. iOS restrictions, ad blockers, and cookie expiry cannot interfere. CAPI Shield implements this free via Make.com webhooks: the webhook fires from Shopify's backend the moment an order is paid, completely independent of browser behaviour.
How to set up Shopify server-side tracking free?
Use CAPI Shield: a free Make.com scenario that routes Shopify order webhooks to Meta Conversions API. Sign up for Make.com free, create a scenario with a Webhooks trigger, add the Meta Conversions API request, create a Shopify Order Payment webhook pointing to your Make.com URL, and test with a sample order. Takes 6 minutes, no code required, free forever on Make.com's free tier.
What is Google Enhanced Conversions and how does it work with Shopify?
Google Enhanced Conversions is Google's server-side conversion tracking system. It supplements your standard Google Ads conversion tags by sending hashed first-party customer data (email, phone, name) alongside each conversion event. Google uses this to match conversions to Google accounts with greater accuracy, improving Smart Bidding and Performance Max optimisation even when cookies and pixels are blocked by iOS or ad blockers. CAPI Shield's Google branch is not a working route to it as shipped: it uploads a click conversion keyed on a Google click ID, and Shopify's order data has no field for one. Google is also moving this upload method, offline click conversion import, out of the Google Ads API and into its Data Manager API, and Make's Google Ads module now warns that uploads may fail for developer tokens that have not recently sent click conversions. Its two consent fields must be set to match your own consent setup.
What is Meta CAPI and how does it work with Shopify?
Meta Conversions API (CAPI) is a server-to-server connection that sends Shopify purchase events directly to Meta without going through the browser. CAPI Shield sets this up free using Make.com, sending hashed email, phone, name, IP and user-agent with every event: the match-key set Meta scores Event Match Quality against, and a larger one than the browser pixel carries.
How much conversion data am I losing without server-side tracking?
We do not publish a number, because the honest answer is specific to your store: the loss is driven by how much of your traffic is mobile and iOS, and how many of those visitors decline tracking. Measure yours instead. The Shopify vs Meta Attribution Gap Calculator turns your Ads Manager conversion count and your Shopify order count into your own gap; the Meta EMQ Score Estimator scores the match quality of what you are currently sending; and the Shopify iOS Attribution Gap Benchmark publishes the sourced figures behind the mechanism. After CAPI Shield deployment most stores see an immediate increase in reported conversions in Meta Events Manager within 24–48 hours.
Does CAPI Shield replace my Meta Pixel?
No. CAPI Shield works alongside your existing Meta Pixel, not instead of it. The pixel still captures upper-funnel events like ViewContent and AddToCart. CAPI Shield adds server-side Purchase events on top. Both fire simultaneously and Meta deduplicates them automatically using the event_id included in every server event.
What is the difference between CAPI Shield and Elevar or Northbeam?
Elevar's Core plan is $225/month, and Northbeam lists its Starter plan at $1,500 with every plan quoted through a sales call. CAPI Shield uses Make.com to achieve the same server-side event forwarding for free. The core technical outcome, server-side purchase events reaching Meta CAPI, is identical. Elevar and Northbeam add analytics dashboards on top. If you only need conversion recovery, CAPI Shield is the free equivalent.
Will CAPI Shield improve my ROAS?
Indirectly, yes. CAPI Shield gives Meta complete purchase data. Advantage+ Shopping uses conversion signals to optimise delivery. Most stores see measurable ROAS improvement within 14–21 days as the algorithm relearns with full data.
What is Event Match Quality and why does it matter?
Event Match Quality (EMQ) is Meta's 0–10 score for how well server-side events are matched to Meta user accounts. Scores above 7.0 indicate strong matching. CAPI Shield sends hashed email, phone, name, IP and user-agent with every event. More match keys give Meta more to match on, which is what the score measures. We have not sampled EMQ across stores, so we do not publish a typical score: the EMQ estimator projects a range from your own parameter set.
Is CAPI Shield GDPR compliant?
The data flows through your own Make.com workspace. CAPI Shield hashes all personally identifiable information (email, phone, name) before transmission using SHA-256, as required by Meta's Conversions API specification. Ensure your store's privacy policy covers server-side tracking data sharing.
How long does CAPI Shield setup take?
Most stores are fully live within 6 minutes. The Make.com scenario takes 3–4 minutes to configure. The Shopify webhook takes under 2 minutes. Testing takes 1–2 minutes. No developer, no code, no infrastructure required.
Why is Shopify's built-in CAPI not enough?
Shopify's native CAPI is still browser-triggered: the thank-you page Web Pixel must execute before the server event fires. If a browser blocks the Web Pixel, the server event may not fire. CAPI Shield uses a server-to-server webhook that fires from Shopify's backend the moment payment is confirmed, regardless of browser behaviour, and it sends a larger match-key set than the native integration does. We have not benchmarked the two side by side, so we put no scores on either.
Does this work with TikTok Ads as well?
Yes. The same Make.com scenario can route events to Meta CAPI and TikTok Events API from one webhook. Most stores start with Meta, then add TikTok as a second branch if they advertise there: using the same webhook trigger, no additional Shopify setup required.
Which Graph API version does CAPI Shield use?
The Meta request names a Graph API version in its URL. Meta retires each version about two years after release, and requests to a retired version fail. Check the version in your scenario's URL against Meta's Graph API changelog and update it before it expires, then send one test order to confirm events still arrive.
What happens if I want to remove CAPI Shield?
Delete the Make.com scenario and the Shopify webhook. Nothing is installed on your Shopify store. Data stops flowing immediately. No residue, no lock-in, no cancellation fees.
The full guide, with every step, source and date: Meta CAPI for Shopify — CAPI Shield, Free Server-Side Setup
Originally published on Stack Architect by Luke Sandelands. Figures there carry the date they were last checked; this copy does not, so prefer the original.
Top comments (0)