Each free channel app does one job well: it connects your store to its own platform. Run four of them and you have four integrations, four sets of settings, four definitions of a conversion — and no single place that says which orders reached which platform. PixelRelay is one install that relays the whole funnel server-side to all of them, and keeps the ledger.
The free apps are good tools, each scoped to its own platform. What no single-platform app can do is describe your business across all of them.
Product views, add-to-carts, cart views, checkout starts and purchases — defined once, relayed server-side to every platform you’ve connected. Change a rule once instead of in four admin screens.
gclid, gbraid and wbraid for iOS, fbclid and ttclid — captured first-party with a 365-day window, so one order can carry the proof of click each platform needs.
Live delivery status per order, per platform, checkable against your Shopify admin — with the reason when one didn’t relay. No platform dashboard can tell you what it never received.
Failed sends retried automatically and capped, surfaced if they still can’t be delivered. Threshold alerts when events go quiet for four hours or delivery drops under 80% across a day.
PixelRelay recognises sales an existing sender already reported and doesn’t send them again — so adding a relay doesn’t double your numbers while you decide which source is canonical.
We’re not going to tell you what another app does under the hood; we don’t run it and it changes. Here’s what PixelRelay does, and the question that settles each row for your own store.
| PixelRelay | Check in your own admin | |
|---|---|---|
| Event coverage | The whole funnel — views, carts, checkouts, purchases — relayed server-side | Which of those five arrive on each platform today, and which are marked server-side? |
| Destinations | One install, one spec, 11+ destinations | How many tracking apps are on your store, and how many would you edit to change one rule? |
| Ad-click receipts | gclid, gbraid, wbraid, fbclid and ttclid on one first-party cookie | Pull a converting order — can you see its click on every platform at once? |
| Per-order delivery | Live status per order, per platform, with the reason when one didn’t relay | Can you name an order from yesterday that didn’t reach a platform? |
| Retries & alerts | Automatic capped retries, plus threshold breakage alerts | If tracking broke this morning, what would tell you, and when? |
| Counted once | Recognises what another sender already reported | What stops the same sale counting twice today? |
Genuinely: if you run one platform, spend is modest, and nobody is reconciling dashboards against Shopify, the free channel app for that platform is a sensible place to be. Consolidating would be solving a problem you don’t have yet.
It changes when several platforms are all claiming the same orders, when upper-funnel events start driving audiences and learning, or when someone asks which orders a dashboard is missing and there’s no way to answer.
Each free app has its own specifics — what it installs, what it misses, and how to run it alongside a server-side relay without double counting.
The whole funnel relayed server-side to Meta in its own event vocabulary — plus every other platform you run, from one install.
Read the full comparison GoogleFull-funnel GA4 events server-side, gclid plus gbraid and wbraid for iOS, and a per-order ledger for when dashboards disagree.
Read the full comparison TikTokThe middle of the funnel is where short-form traffic lives — relayed server-side to TikTok Events with ttclid captured first-party.
Read the full comparison KlaviyoThe same server-side browse and cart stream your ad platforms get, so flows and audiences describe the same shoppers.
Read the full comparisonInstall the Shopify app from the App Store and start relaying orders server-side today.
// install from the Shopify App Store. That’s the whole setup.
delivery status you can check against Shopify.Failed sends retry automatically and surface in your dashboard.