iOS and ad blockers are eating my Meta conversions.
Sends every paid Shopify order to Meta’s Conversions API from the server, with the customer’s details hashed for matching, so the purchase can reach your ad account even when the browser pixel is blocked. CAPI Shield is the finished Make.com file: import it, add your own credentials, and test it with one order. $9.99 once, no subscription.
30-day money-back guarantee — email within 30 days for a full refund. Refund policy
Build it yourself free →Quoted on server-side vs. app-based checkout tracking in MAKERSPACE, August 2026
Which one is right for you
You advertise on Meta, Ads Manager reports fewer purchases than Shopify, and nothing else (Shopify’s own Facebook & Instagram app included) is already sending purchases to Meta from the server.
You want two or more of the four automations. The kit is one scenario instead of four, so it fits inside Make’s free plan with a slot to spare and uses about a third fewer credits per order.
What the kit includes ↓You want to see and adapt every field that goes to Meta, or you mainly want to understand how server-side events work. The free guide walks through the same request.
Open the free guide →One file, yours to keep
- Blueprint 01_CAPI_Shield.json JSON
Before you start
- Meta Business access with permission to generate a Conversions API token for your pixel (Meta now calls it a dataset) in Events Manager.
- A Make.com account, and Shopify admin access that reaches Settings → Notifications.
- A decision about Shopify’s own Meta connection. If the Facebook & Instagram app is on Maximum data sharing, Shopify is already sending server events, and running both without matching event IDs counts some purchases twice.
- A privacy policy that tells customers their order details are shared with advertising platforms.
Set up in 3 steps
No developer, no agency, no configuration screens. Three steps.
In Make.com: Create a new scenario → Import Blueprint → upload Blueprint 01_CAPI_Shield.json. The router that splits each purchase to Meta and to Google Ads comes with it.
Make.com · one clickThe blueprint ships with placeholders where your secrets go: your Meta pixel ID and Conversions API access token. Paste yours in: nothing is shared, nothing is proxied through us. Then delete the Google Ads route: as shipped it cannot match orders.
Meta Events ManagerAdd an Order payment webhook in Shopify Admin, then place a test order. Meta Events Manager should show a server event arriving with a match quality score against the hashed email, phone, name, IP and user-agent the blueprint sends.
Shopify Admin · Events ManagerSetup, click by click
-
Import the file into a new scenario
Save Blueprint 01_CAPI_Shield.json from the Drive folder, then in Make start a new scenario and choose Import Blueprint from the three-dot menu in the editor. You should see one webhook, a step that prepares and hashes the customer fields, and a router with a Meta branch and a Google branch.
-
Generate the Meta token
In Events Manager, select your dataset, open its Settings tab and generate a Conversions API access token. Copy it together with the dataset ID shown on the same screen. Treat the token like a password: whoever holds it can send events in your store’s name.
-
Fill in the Meta branch
Open the Meta request step and replace the two placeholders, dataset ID and token, with yours. Leave the request body as it is; the field names and the hashing are what Meta checks each event against.
-
Delete the Google route
Google attributes this kind of upload by the click ID an ad visit leaves behind, and the order Shopify hands to Make does not carry one, so as shipped the Google branch finds no match for most orders. Right-click the Google step and delete it, so each order spends credits on the Meta branch alone. Keep it only if you are rebuilding it, and set its two consent fields, which ship as Unspecified, to match your own consent setup.
-
Point Shopify at the webhook and switch on
Copy the address from the webhook step. In Shopify Admin, under Settings → Notifications → Webhooks, create a webhook on Order payment in JSON with that address, save it, and turn the scenario on.
-
Confirm it in Test Events
Open Test Events in Events Manager, then place an order: a cheap real one you refund, or one through Shopify’s test gateway. A Purchase should appear from the server. If your browser pixel fires as well, the pair should read as one deduplicated event, not two.
What it replaces, and what it does not do
Elevar, Stape, Littledata and Triple Whale each do more than deliver purchases to Meta: hosted server containers, full-funnel events, attribution dashboards, a support team. If the purchase signal is what you pay them for, that is the part CAPI Shield ships as a file. What it will not do: send ViewContent or AddToCart from the server, model multi-touch attribution, give you a reporting screen, or match orders in Google Ads. Your browser pixel keeps covering the top of the funnel; this covers the order. If the dashboards are what you use, keep paying for them.
When it breaks, and how you will know
Every automation fails sometimes. These are the ways this one does, what causes each, and where to look.
Make shows successful runs, but Meta shows no server events.
WhyThe Meta step is set to carry on past an error, so a rejected request still ends as a green run in Make’s history. The usual rejection is a mistyped dataset ID, a token issued for a different business, or a Graph API version in the URL that Meta has retired.
CheckOpen a run, click the Meta step and read the response body. Meta answers events_received: 1 when it accepted the event; anything else comes with a message naming the problem.
Purchases in Ads Manager jump to roughly double.
WhyTwo server-side senders are reporting the same order (this scenario plus Shopify’s own Meta integration or another tracking app) with event IDs that do not match.
CheckEvents Manager’s Overview lists the sources feeding each event and whether they are being deduplicated. Switch one server sender off, or make both send the same event ID.
Event Match Quality stays low.
WhyThe score is calculated across many events, so one test order tells you very little. A score that stays low usually means most checkouts do not collect a phone number, which leaves email carrying the match on its own.
CheckWait for a few days of real orders, then open the score’s breakdown in Events Manager. It lists which customer parameters are missing and how often.
Events stop arriving months after setup.
WhyThe token was revoked (for example, the Conversions API system user was removed during a clean-up of Business Settings) or Meta retired the Graph API version named in the request URL.
CheckRead the Meta step’s response in the latest run. For a token error, generate a new token in Events Manager and paste it in; for a version error, move the URL to a current version from Meta’s changelog. Send one order through to confirm.
Same 30-day money-back guarantee. See everything in the kit
CAPI Shield, in detail
Where does the hashing happen?
Does this replace my Meta pixel?
Does it send to Google Ads as well?
What happens when Meta retires the Graph API version it uses?
Can it run alongside Shopify’s Facebook & Instagram app?
Do I need Google Ads for it to work?
CAPI Shield — Meta Conversions API purchase events, server-side.
Blueprint 01, import-ready. $9.99 once, no subscription, files yours to keep.