Why your client-side tracking is broken
Traditional tracking relies on JavaScript pixels running in the user's browser. Meta Pixel, Google Tag, TikTok Pixel — all of these scripts run client-side (in the browser). The problem: more and more factors block these scripts.
iOS 14+ and ATT (App Tracking Transparency)
Since iOS 14.5, Apple asks users to allow tracking, and many say no. Meta then loses visibility on those purchases.
Declined consent makes the conversion invisible to the pixel
Ad blockers
Ad blockers (uBlock Origin, Brave, AdGuard) filter requests to third-party tracking pixels before they even go out.
The pixel request is blocked before it's sent
Browser restrictions (Safari ITP, Firefox ETP)
Safari caps third-party cookies at 7 days (ITP). Meta's 28-day attribution windows are therefore partly ineffective on Safari.
Attribution window cut to 7 days
GDPR and declined consent
In Europe, pixels can only fire after explicit consent. With well-designed cookie banners, 30-50% of users decline.
Without consent, the browser pixel doesn't fire
How server-side tracking works
Server-side tracking moves the sending of conversion events from the browser to your server. Here's the flow:
The result: conversions that were invisible because of iOS or an ad blocker are now sent directly from your server. Meta sees the purchases, can optimize its algorithms, and your ROAS becomes reliable again.
Meta CAPI: the Conversions API explained
The Conversions API (CAPI) is Meta's server-side tracking tool. It lets you send conversion events directly from your server to Meta, alongside the browser pixel. Meta intelligently merges the two sources (deduplication) to avoid duplicates.
Events supported by CAPI:
ProfitPilotPro implements CAPI natively. On plans that include passback (Pro and Agency), a purchase attributed to Meta is sent via CAPI with enriched data: hashed email, hashed phone, IP address, user agent — to maximize the match rate. Purchases without a Meta click signal aren't sent back: inventing an attribution would degrade your own numbers.
What does it actually change?
The gain depends entirely on your audience, your market and the data you already have: we don't publish an average percentage, because we don't measure one. What server-side tracking changes is the nature of what gets sent:
Installing the ProfitPilotPro pixel on Shopify
Setup takes less than 5 minutes and requires no code changes.
1. Connect your store
Install ProfitPilotPro from the Shopify App Store and grant access. Your orders and products start syncing right away.
2. Turn on the extension in your theme
In the Shopify theme editor, open App embeds and turn on ProfitPilotPro Tracking. It's the only step we can't do for you: Shopify leaves turning on extensions to the merchant. The dashboard reminds you as long as it's off.
What about checkout?
It's covered separately by a Web Pixel Extension, which ProfitPilotPro registers on your store when you connect. You'll find it under Settings → Customer events.
Server-side tracking for TikTok Ads and Google Ads
Meta isn't the only one offering a server-side API. TikTok has the TikTok Events API, and Google Ads has Enhanced Conversions. ProfitPilotPro sends every Shopify event to all three platforms at once:
- Meta Conversions API — Purchase, AddToCart, InitiateCheckout, ViewContent, PageView, Lead events
- TikTok Events API — CompletePayment, PlaceAnOrder, AddToCart, ViewContent events
- Google Ads Enhanced Conversions — conversion events with hashed email/phone
Everything is deduplicated with a unique event_id to avoid double counting with the browser pixel. And these recovered conversions feed straight into your true ROAS and your Shopify net profit.
Event Match Quality: why it matters
Meta scores the quality of your CAPI events out of 10 (Event Match Quality). The better Meta can match your event to a Facebook or Instagram account, the better your ads are optimized. To maximize that score, ProfitPilotPro automatically sends:
- Customer email (SHA-256)
- Phone (SHA-256)
- First name, last name, city, zip code, country (SHA-256)
- fbp and fbc (Facebook cookies collected client-side)
- Visitor IP address and user agent
- External ID (Shopify customer ID, hashed)
The more of these fields are filled in, the higher the Event Match Quality Meta gives you. ProfitPilotPro shows your actual EMQ event by event in the dashboard: your own measurement is what counts, not an average promised in advance.
FAQ — Server-side tracking and Meta CAPI
What is server-side tracking on Shopify?+
Server-side tracking sends conversion events (Purchase, AddToCart, PageView) from your server to Meta, TikTok and Google, instead of from the visitor's browser. The result: ad blockers, iOS 14.5+ and Safari ITP restrictions can no longer block tracking.
What is Meta CAPI (Conversions API)?+
Meta's Conversions API is a server-side channel that receives events directly from your server. It complements the browser pixel, and deduplication happens via event_id. On plans that include passback, ProfitPilotPro sends Meta-attributed Purchase events with hashed email and phone (SHA-256).
Does server-side tracking recover conversions lost on iOS?+
It sends the event from the server, so neither Apple's ITP nor an ad blocker can stop it. How much visibility you regain depends on your audience and the data you have: we don't publish an average, because we don't measure one. Your actual match rate is shown in the dashboard.
Is server-side tracking GDPR compliant?+
Yes, as long as user consent is collected before sending (Consent Mode). ProfitPilotPro respects the consent from your cookie banner (Axeptio, Didomi, Cookiebot) and only sends events for users who have accepted.
Should you keep the standard Meta pixel?+
Yes. Best practice is to send every event twice: browser pixel + server-side CAPI. Meta deduplicates using the event_id. If the pixel is blocked (iOS, ad blocker), the server-side version gets through. If the pixel gets through, CAPI acts as a backup and improves matching.
Native Shopify pixel or ProfitPilotPro pixel?+
The native Shopify pixel does send some events through CAPI, but it doesn't deduplicate across channels (TikTok, Google) and doesn't enrich events with server data. ProfitPilotPro brings Meta CAPI + TikTok Events API + Google Enhanced Conversions together in a single pixel.