Setting up Shopify server-side tracking means connecting a Shopify orders/paid webhook to a free Make.com scenario: the webhook fires when an order is paid, Make.com hashes the customer data with SHA-256, then posts the event to Meta Conversions API, Google Enhanced Conversions, and TikTok Events API. A full three-platform build takes about 18 minutes, no code required.
Questions this guide answers
What is Shopify server-side tracking and how does it work?
Shopify server-side tracking sends purchase events directly from your server to ad platforms (Meta, Google, TikTok) without going through the customer’s browser. When a Shopify order is paid, a webhook fires to Make.com which routes the event to each platform’s API endpoint: bypassing iOS restrictions, ad blockers, and cookie limitations. It works alongside your existing browser pixel, not instead of it.
Do I need to remove my browser pixel when setting up server-side tracking?
No: keep your browser pixel running alongside server-side tracking. The pixel captures upper-funnel events (ViewContent, AddToCart, InitiateCheckout) that server webhooks don’t cover since they only fire on confirmed payment. Set a matching event_id in both your pixel and server events so each platform deduplicates and you see one conversion, not two.
How much of my lost Shopify conversion data will server-side tracking recover?
We publish no recovery percentage, and no honest one exists as an industry figure: what server-side tracking recovers is whatever your browser pixel was losing, which is set by your own mobile/iOS traffic mix and consent rate. Measure it as Additional Conversions Reported in Meta Events Manager, or with the attribution gap calculator, and see why the 20–40% estimate was retracted. Meta reported in April 2026 that advertisers running the Conversions API for web events saw an average 17.8% lower cost per result versus those without it; that is Meta's figure across its advertisers, not a measurement of your store.
Is server-side tracking GDPR compliant?
The data flows through your own Make.com workspace: you control what is sent and can delete the scenario at any time. All personally identifiable information (email, phone) is SHA-256 hashed before transmission as required by each platform’s API specification. Ensure your store privacy policy discloses server-side conversion data sharing with advertising platforms. For GDPR-specific advice consult a legal professional.
How long before I see results after setting up server-side tracking?
Server events start flowing immediately after your first paid order. More conversions will appear in your ad platform reporting within 24–48 hours. Meaningful CPA and ROAS improvement typically takes 7–14 days as ad platform algorithms recalibrate delivery optimisation using the more complete conversion signal.
How often does Make.com’s free tier actually fail or rate-limit?
The Make.com free plan limit is 1,000 credits/month, refreshing on the 1st of each month. One Shopify order = 4 credits (webhook trigger + Meta + Google + TikTok), so the free tier handles ~250 orders/month before hitting the cap. Make.com does not “fail” mid-month: it pauses your scenario and emails you. Real failure modes are different: a temporary Meta API outage, an expired access token, or a malformed payload. These are caught in Make.com’s execution log under each scenario, and re-runs are free.
Will server-side tracking keep working as iOS tightens privacy further?
Yes. Server-side tracking is specifically designed to be immune to iOS browser-level restrictions because the event originates from Shopify’s server, not the customer’s iPhone. Every iOS release since 17 has extended Link Tracking Protection and tightened Safari’s Intelligent Tracking Prevention: both of which only affect browser pixels. CAPI, Google Enhanced Conversions, and TikTok Events API will continue to function exactly as documented. If anything, server-side tracking becomes more valuable with each iOS release.
Do I still need server-side tracking if I’m using Shopify’s native Customer Events / Web Pixels?
Yes. Shopify’s Web Pixels framework is still browser-based: it loads in a sandboxed iframe in the customer’s browser and is subject to the same ad blocker and ITP restrictions as a regular pixel. It improves reliability slightly versus a raw Meta Pixel install, but does not match the recovery rate of a true server-side webhook firing from Shopify’s backend on confirmed payment. Run Web Pixels for upper-funnel events (PageView, AddToCart) and the Make.com webhook method for the Purchase event.
What is the difference between Meta CAPI and Shopify’s native data sharing?
Shopify’s native Maximum data sharing setting enables their own CAPI integration, but it is still partially browser-triggered: if the thank-you page pixel fails to execute, the server event may not fire. The Make.com webhook method fires directly from Shopify’s backend on payment confirmation with zero browser dependency, making it more reliable.
Can I set up Shopify server-side tracking without a developer?
Yes. The Make.com webhook setup requires no code. You configure a Shopify webhook in Settings, build an HTTP module in Make.com’s visual drag-and-drop interface, and paste your API credentials. Most store owners complete the setup in under 20 minutes. No developer, no agency, no Shopify app installation required.
Does server-side tracking work with Shopify’s native Maximum data sharing?
Yes: the Make.com webhook method works independently of and alongside Shopify’s native data sharing. You do not need to disable native CAPI. Running both adds redundancy: if one delivery method has a transient failure, the other ensures the event still reaches the platform. Use matching event_id values in both so platforms deduplicate correctly.
How much does Shopify server-side tracking cost?
The Make.com webhook method costs $0/month for Shopify stores under approximately 250 orders per month, since each order uses 4 Make.com credits (the webhook trigger plus one each for Meta, Google and TikTok) and the free tier covers 1,000 credits monthly. Above that, the Make.com Core plan at $9/month covers 10,000 credits: enough for roughly 2,500 orders/month at 4 credits each (make.com/en/pricing, read 25 September 2026). Managed alternatives like Elevar (from $225/month) and Triple Whale (priced by store revenue) achieve the same tracking quality at significantly higher cost. The premium pays for managed onboarding and dashboards, not for superior API access.
What Event Match Quality (EMQ) score is good for Meta CAPI on Shopify?
Meta scores Event Match Quality from 1 to 10. The score rises with the number of match keys an event carries. The Make.com webhook method sends hashed email, phone, zip, IP, user agent, fbc and fbp. Scores of 9–10 are excellent but typically require logged-in customer data with full address fields. Anything below 5 indicates missing match keys: investigate email format (lowercase + trim before SHA-256), phone format (E.164 digits-only before SHA-256), and the external_id field (Shopify customer.id, hashed).
Why is my TikTok event match quality low even with server-side tracking?
The single most common cause is sending the event name “Purchase” instead of CompletePayment. TikTok’s Events API requires CompletePayment as the event name for purchase events: sending “Purchase” (which works for Meta) results in low Event Match Score and prevents purchase-campaign optimisation. Other common causes: missing hashed email, missing IP address (you must map order.client_details.browser_ip from the Shopify webhook payload, not the Make.com runtime IP), missing TikTok Click ID (ttclid) for paid traffic, and missing user agent. Send all four high-impact signals (email, phone, IP/UA, external_id): that is the full set TikTok calculates the score from. We publish no figure for what it scores; read yours in TikTok Events Manager.
Is Shopify server-side tracking free?
Yes: the tracking itself is free to implement. The Make.com webhook method in this guide costs $0/month for stores under ~250 orders/month, because each order uses 4 Make.com credits and the free tier covers 1,000. Above that, Make.com Core is $9/month for 10,000 credits. The platform APIs (Meta CAPI, Google Enhanced Conversions, TikTok Events API) are all free to use. You only pay if you choose a managed tool: Elevar runs from $225/month and Triple Whale prices by store revenue, but they charge for dashboards and managed onboarding, not for better tracking access. The same events reach the same endpoints either way. See the free vs paid comparison for the full breakdown.
Shopify server-side tracking vs Elevar: what’s the difference?
Both send the same server-side events to the same destinations (Meta CAPI, Google, TikTok): the difference is who builds and maintains the pipeline. Elevar is a managed service from $225/month: it provisions a server-side GTM container, supplies a pre-built Shopify data layer, monitors delivery with alerts, and handles refunds and order edits automatically. The free Make.com webhook method delivers the same events and the same Event Match Quality ceiling, but you build the scenario yourself in ~18 minutes and maintain it. Choose Make.com for zero cost and full control; choose Elevar if managed monitoring, automatic edge-case handling, and a reporting dashboard justify the monthly fee at your ad spend. For most stores under 1,000 orders/month, the Make.com method delivers the tracking quality without the recurring cost.
Do I need server-side GTM (sGTM) for Shopify server-side tracking?
No. Server-side Google Tag Manager is one way to do server-side tracking, but it requires provisioning and paying for a Google Cloud tagging server and configuring containers: overkill for most Shopify stores. The Make.com webhook method skips GTM entirely: Shopify fires an order webhook directly to Make.com, which POSTs to each platform’s API. You get the same server-to-server delivery with no server to host or maintain. sGTM earns its complexity only for large stores with dedicated analytics engineers needing custom tag logic across many destinations; for everyone else, the webhook method is simpler, free, and equally effective for conversion tracking.
The full guide, with every step, source and date: Shopify Server-Side Tracking Setup — Step by Step
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)