Savrena receives Shopify order data server-side — including COD and off-site checkout events your pixel never sees — forwards eligible events to Meta CAPI, Google Ads, and GA4, then shows you the exact payload it sent, reconciled against your real orders.
Keep your existing pixels on. We deduplicate instead of asking you to switch them off.
The gap
Browser tracking assumes the shopper finishes checkout on your storefront with scripts running. In Indian ecommerce that assumption breaks constantly — and nothing tells you when it does. The events simply never arrive, so your ad platforms optimise on whatever is left.
Shiprocket/Fastrr, GoKwik and similar providers complete the order outside your storefront. The confirmation page your pixel waits for never loads, so the purchase is never reported.
Cash on delivery is a huge share of Indian orders and often settles outside the standard checkout flow. Prepaid-only tracking quietly under-reports your best campaigns.
A blocked script fires nothing. There is no error and no gap in any report — just quieter campaigns, worse ROAS, and no way to tell it apart from bad creative.
Express and wallet flows drop gclid, fbclid and cookies along the way. The order arrives with nothing to match it to the ad click that caused it.
Proof, not promises
Every send is recorded: the exact JSON we posted, the platform's response, and which identifiers it actually carried. Open any order and read it. No dashboard arithmetic to take on faith.
// the exact body Savrena posted { "event_name": "Purchase", "event_id": "ord_1042", // shared with the browser event — platform collapses both into one "event_time": 1785312044, "action_source": "website", "user_data": { "em": "a4f1c2…", // SHA-256, hashed in the browser "ph": "9e07b3…", // normalised to E.164 first "fbc": "fb.1.1785…", "client_ip_address": "49.36.…" }, "custom_data": { "currency": "INR", "value": 2499.00, "num_items": 2 } }
Illustrative of the receipt format. Your own receipts are real payloads from your own orders.
Reconciliation
The Truth Report counts your actual orders and asks a blunt question of each one: did the browser see it, did the server see it, or did nobody see it? A gap becomes a number you can act on instead of a silence.
| Source | Purchases | Share | What it means |
|---|---|---|---|
| Browser and server | — | deduped | Seen twice, counted once. The healthy case. |
| Server only | — | recovered | Orders your pixel missed entirely. Off-site checkout, COD, blocked scripts. |
| Browser only | — | investigate | Reached the platform but never became a Shopify order. |
| Neither | — | gap | Real revenue no platform ever heard about. |
Your numbers fill in from your own store. We don't ship someone else's.
Match quality
Platforms match conversions to people using the identifiers you attach. Savrena measures coverage per identifier, per destination — so a falling score points at the field to fix rather than at a score to worry about.
Example view. Low coverage is a fixable configuration problem, and the dashboard says which one.
How it works
Capture once — from the browser, from Shopify's servers, and from your checkout provider — then fan out with consistent identity and deduplication.
Built for how India actually checks out
Most server-side tools are designed around a prepaid, on-Shopify checkout and treat everything else as a support ticket. That is backwards for the stores we serve.
Orders that complete on Shiprocket/Fastrr or a similar provider are captured directly from the provider, then matched back to the shopper's original session.
A COD order confirmed days after the ad click still recovers its click IDs and campaign, because identity is stored server-side rather than in a cookie that already expired.
Returned and cancelled orders are forwarded as refunds, so platforms optimise on revenue you actually kept.
The storefront pixel runs inside Shopify's sandbox, off the main thread, and loads no advertising scripts by default. Most of your traffic is on a phone on mobile data — it should stay fast.
Why Savrena
| Browser pixel alone | Savrena | |
|---|---|---|
| Off-site / COD orders | Missed | Captured server-side |
| Blocked or failed scripts | Silent loss | Server copy still sends |
| Proof of what was sent | None | Full payload + response, per order |
| Reconciliation vs Shopify | None | Truth Report |
| Duplicate protection | Manual | Shared event ID, automatic |
| Keep existing pixels | n/a | Yes — deduplicated, not replaced |
| Custom events & attribution | n/a | Included, not a paid add-on |
FAQ
The ones most vendors leave you to discover after signing up.
Savrena merges matching browser and server signals before delivery. Deduplication with an independent sender depends on the destination: Meta requires matching event names and IDs. Another app may use different IDs, so automatic deduplication across every pixel or third-party checkout is not guaranteed.
Review which integration owns each event before changing an existing pixel. Use one page-view and commerce sender per GA4 property. For Meta, confirm that independent browser and server senders use compatible event IDs. Test the configuration and verify the destination reports before changing live tracking.
That's the case it was built for. The order is captured from the checkout provider's webhook and matched back to the shopper's browsing session, so the purchase reaches your ad platforms even though no confirmation page ever loaded on your storefront.
Yes. A COD order is captured when Shopify records it, with its click IDs and campaign recovered from the earlier session — even if that click was days before the order.
No. The browser pixel runs inside Shopify's sandbox, off the main thread, and loads no advertising scripts by default. The heavy work happens on our servers.
Open any order and read the payload we sent to each destination, with the platform's response. Then compare delivered conversions against your Shopify orders in the Truth Report. Both are in the dashboard from day one — you are not asked to trust a summary number.
Email and phone are hashed in the browser before they're sent — plain contact details never enter the identity graph from the pixel. Retention is configurable, every delivery is auditable, and the full detail is in our privacy policy.
They rarely will, and any vendor promising an exact match is overselling. Platforms apply their own attribution windows, modelling and deduplication after we deliver. What we can prove is what left our side and when — which is the part that's normally invisible.
Connect the store, add the pixel, connect a destination. The first payload is inspectable within minutes, and you can verify it before pointing any budget at it.
Yes. Stores are grouped under an organisation with shared access, so agencies and multi-store owners work from one console instead of logging in and out.
Connect a store and read the first payload within minutes. If it isn't sending what you expected, you'll know before you spend another rupee on ads.