Browse and cart signals survive.
When a browser tag is stripped, its view and cart events are gone with it. First-party collection keeps those moments available, so a funnel report is not left with purchases and nothing before them.
You make the sale.
We carry the signal.
Connect your Shopify store and marketing platforms. After setup, PixelRelay sends eligible events automatically, with a delivery record you can check.
14-day free trial on paid plans.
A purchase on your storeOrder #1042
The starting point.
Straight from Shopify.
Prepare. Check. Send.
Meta
Google Ads
Klaviyo
A short setup.
Not a new daily job.
For a standard Shopify store, there are no GTM containers to build or theme files to edit. You connect the accounts. We manage the relay.
Install the app.
Add PixelRelay from the Shopify App Store and approve access to your store.
Connect your platforms.
Authorize each destination and complete its account-specific settings.
Verify a purchase.
Check the order in PixelRelay and the destination's testing tools before relying on the setup.
Running Hydrogen or a custom storefront? See the guided implementation path.
Every event captured.
Not just the order.
The purchase is the last moment in a journey, not the only one worth sending. PixelRelay collects the browse, cart, and checkout moments as well — so the platforms optimising your spend see the whole funnel, not only the receipt at the end.
Store events
- Product viewed
- Added to cart
- Checkout started
- Purchase
Prepare · check · send
Connected destinations
- Meta CAPI
- Google Ads
- TikTok
- GA4
Eligible sends depend on consent, supported events, destination configuration, and plan.
Captured is not the same as sent.
Collection is the first step, not the last. Consent choices, destination support, and plan level all decide whether a collected moment becomes an outgoing send — and PixelRelay records which it was, either way.
Optimisation needs more than sales.
Ad platforms build audiences and bidding signals from upper-funnel events too. Sending only purchases gives them the smallest possible amount to learn from.
Each platform wants it under a different name.
A single add-to-cart is AddToCart to Meta, add_to_cart to GA4, and AddToCart again to TikTok — different casing, different payloads, different rules about what may accompany it. Translating one moment into each platform's own vocabulary is the work PixelRelay does after it collects the event.
Swipe through four store moments. Each one becomes three platform-ready names.
Product viewed
1 of 4product_viewed- Meta CAPI
- ViewContent
- GA4
- view_item
- TikTok
- ViewContent
Added to cart
2 of 4product_added_to_cart- Meta CAPI
- AddToCart
- GA4
- add_to_cart
- TikTok
- AddToCart
Checkout started
3 of 4checkout_started- Meta CAPI
- InitiateCheckout
- GA4
- begin_checkout
- TikTok
- InitiateCheckout
Purchase
4 of 4checkout_completed- Meta CAPI
- Purchase
- GA4
- purchase
- TikTok
- CompletePayment
Standard events only. Supported events, fields, and destinations vary by plan and consent.
Names shown are each platform's documented standard events. Which of them a given store can send depends on consent, destination configuration, and plan. See what each destination supports.
One purchase.
Two useful sources.
The order tells us what sold. Available storefront context helps describe the journey that led to it.
The purchase itself.
Shopify sends the order directly to PixelRelay's server. This path does not depend on a browser pixel firing.
An ad blocker cannot stop that server-to-server request. That does not make every storefront event or outgoing send guaranteed.
The context around it.
First-party collection adds available journey and ad-click signals. Browse, cart, and checkout events use storefront collection, not order webhooks.
Consent and browser restrictions still matter. No digital fingerprinting.
Blocking is about
the domain.
Content blockers work from lists of hosts. That single fact decides whether a storefront event is ever collected — and it is why where a script is served from matters more than whether a tool calls itself server-side.
Describes where a script is served from, not any other product's internals. First-party collection reduces one specific failure; it does not exempt a store from consent requirements or browser storage limits. Read the privacy approach.
The next steps
happen automatically.
No manual forwarding after each sale. PixelRelay prepares eligible events for your connected destinations, checks them, and records the outcome.
One Shopify purchase
Order #1042The sale
is real.Keep its signal moving.
is real.Keep its signal moving.
Eligibility and destination requirements apply.
One order.
Two different answers.
Pick a real Shopify order. PixelRelay can tell you what happened to it on the way out. What a platform then does with it is a separate question — and keeping the two apart is what makes either answer useful.
Did it arrive?
Review the destination outcome recorded against that order and investigate anything that needs attention. Retryable failures are retried within capped limits; unresolved ones stay visible rather than disappearing from view.
Did it get credit?
That answer belongs to the platform. A destination response is not a promise of report appearance, ad credit, or improved ROAS. Account settings, attribution rules, plan allowances, and event eligibility still apply.
Understand the difference ↗Do I need to remove my existing Shopify channel apps?
Not necessarily. Keep the channel features you use, such as catalogs and selling tools. Review overlapping conversion sends before enabling a second sender. See the native-app guide.
Will PixelRelay automatically deduplicate any other pixel?
No blanket guarantee. Matching identifiers and the destination's rules matter. Verify overlapping browser and server events, or choose one sender for the same conversion.
Does server-side tracking bypass consent?
No. PixelRelay applies consent-aware handling to customer data and delivery. Merchants remain responsible for their notices, legal basis, and platform requirements. Read the privacy approach.
Are browse and cart events sent to every platform?
No. Each destination supports its own event set, and plan level affects which events are available. Check the destination's requirements and your plan before assuming a given event will be sent. Compare current plans.
What should I check before going live?
Confirm account connections, review existing conversion senders, and validate an order in PixelRelay and the destination's tools. Open the installation guide.
Are all features included in every plan?
No. Order allowances, store counts, subscription events and custom events depend on your plan. Hydrogen is included on every plan from $199 a month. Compare current plans.
Your next sale. Already on its way.
Connect your platforms. Verify your setup. Get back to selling.
14-day free trial on paid plans.