Flows fire on events. Send Klaviyo all of them.
Klaviyo's own Shopify integration handles the commerce side well. PixelRelay adds the same complete, server-side event stream you're sending your ad platforms — browse, cart and checkout behaviour included — so browse-abandon and cart-abandon flows trigger from the same record everything else is measured on.
This sits alongside your Klaviyo integration, not instead of it.
The revenue flows are the browse and cart ones.
Post-purchase flows fire off an order, which is the easy part. The flows that actually recover revenue — browse abandonment, cart abandonment, back-in-stock nudges — fire off behaviour before the order exists.
PixelRelay relays that behaviour server-side into Klaviyo in its own event vocabulary, from the same capture that feeds your ad platforms — so a shopper who triggers a Meta audience also triggers the flow, instead of one seeing them and the other not.
One authoritative path in. One event spec out.
Order capture is server-to-server: Shopify hands the order straight to our server, so there is no browser script on that path for anything to strip. A first-party script rides alongside it — served from your own store's domain, never a third-party one — purely to attach the ad-click receipts that earn your campaigns credit.
From there it's one set of rules fanned out to every destination you've connected — GA4, Meta, Google Ads, TikTok, Klaviyo, Bing, Reddit, Snapchat, Pinterest, LinkedIn and Segment, plus your own server endpoints. Change a rule once and every platform gets the change. No GTM container, no theme edits, and no digital fingerprinting — first-party signals only.
Know it arrived. Know when it didn’t.
Most tracking setups give you a number in a platform dashboard. The number you actually need is which orders are behind it — and which ones aren’t.
Per-order reconciliation
Live delivery status for every order, per platform, checkable against your Shopify admin — with the reason when one didn’t relay: duplicate, stale order, quota, relay disabled.
Retries that surface
Failed sends are retried automatically, capped, and surfaced in your dashboard if they still can’t be delivered — so a failure becomes a task, not a silence.
Counted once
PixelRelay recognises sales an existing sender already reported and doesn’t send them again. One order stays one conversion, in every dashboard.
Breakage alerts
Threshold-based, not hopeful: events quiet for four hours, or delivery under 80% across a day, and you hear about it — instead of finding out at month end.
Two sources, one profile.
PixelRelay deduplicates against events another source already reported, so a profile doesn't collect the same event twice and a flow doesn't fire twice off it. Worth reviewing which source owns which metric before you point flows at them.
Two sources, no decision
A duplicated metric can trigger a flow twice, or split a segment that should be one audience.
One source per metric
Decide which source owns each metric, and flows trigger once off a record that matches your ad platforms.
What we do — and how to check what you have.
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.
| Capability | PixelRelay | Check in your own admin |
|---|---|---|
| Event coverage | Product views, add-to-carts, cart views, checkout starts and purchases — the whole funnel, relayed server-side | Open your platform’s event dashboard. Which of those five are arriving, and which are marked server-side? |
| Destinations | One install, one event spec, 11+ destinations — including ones with no free channel app | Count the tracking apps on your store. To change one rule, how many places do you change it? |
| Ad-click receipts | gclid, gbraid and wbraid for iOS, fbclid and ttclid — captured on one first-party cookie with a 365-day window | Pull a recent converting order. Can you see which ad click it came from, on every platform at once? |
| Per-order delivery | Live delivery status per order, per platform — with the reason when one didn’t relay | Name an order from yesterday that didn’t reach the platform. Can you? |
| Retries | Automatic and capped on failed sends, surfaced in your dashboard if they still can’t be delivered | When a send fails today, where does that appear? |
| Breakage alerts | Threshold-based — events quiet 4h, or delivery under 80% over 24h | If tracking broke this morning, what would tell you, and how long would it take? |
| Counted once | Recognises sales an existing sender already reported, so one order stays one conversion | If you add a second sender to this dataset, what stops the same sale counting twice? |
| Conversion value | Adjusted for excluded products — gift cards, shipping protection — so you bid on revenue you actually want | Does the value you optimise against include line items you’d rather not bid on? |
| Subscriptions | Recharge subscription starts and renewals relay as conversions | Do renewals show up as conversions in your reporting today? |
| Headless | Works on Hydrogen and headless storefronts | If you moved off the Online Store theme tomorrow, what would still be tracking? |
The right-hand column is deliberately a question, not our description of another app. We don’t run it, and it changes.
When the native integration on its own is enough.
Credit where it’s due: Klaviyo’s Shopify integration is genuinely good at the commerce events, and if your flows are post-purchase — receipts, reviews, winbacks, replenishment — it covers you. Adding anything would be overhead.
It becomes worth consolidating when your browse and cart flows matter to revenue, or when you want the same event definition feeding Klaviyo and your ad platforms so a segment and an audience actually describe the same people.
- Post-purchase flows onlyThe native integration is fineOrders are the trigger, and orders are the part it handles well.
- Browse and cart flows carry revenueConsolidate the measurement layerOne capture feeding flows and ad platforms the same complete behaviour.
Before you change anything.
We describe what PixelRelay does; we don’t describe another app’s internals. Shopify and Klaviyo change their settings and menus periodically — confirm the current labels in your own admin. Last reviewed August 2026.
Stop losing conversions to ad blockers.
Install 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.