Checkout is a sandbox
On standard Shopify plans you cannot run your own JavaScript inside checkout. Browser-side purchase pixels depend on pages you do not fully control — server-side delivery removes that dependency.
Platform Guide · Shopify
Server-Side Tracking for Shopify Stores in Bangladesh
If Shopify reports more orders than Meta shows as purchases, or your Events Manager match quality stays weak, the problem is usually the signal path — not your ads. Server-side tracking routes Shopify events through your own domain first, so ad-blockers, Safari ITP, and checkout page restrictions stop eating your conversion data.
Why Shopify tracking breaks
The four gaps that make Shopify and Meta disagree
Ad-blockers on the storefront
Pixel requests to Meta, Google, and TikTok are sent from the browser to known third-party endpoints. A significant share of visitors block them, so ViewContent and AddToCart events never leave the browser.
Safari's 7-day cookie limit
ITP expires JavaScript-set cookies after seven days on iOS. A shopper who clicks a Meta ad today and buys next week can look like a brand-new visitor — attribution gone.
Click IDs stripped on landing
fbclid, gclid, and ttclid parameters can be stripped by extensions or privacy settings before your scripts run, so the ad platform never learns that its click converted.
What a reliable Shopify setup needs
The basics are not optional
What clean Shopify tracking should include
- A first-party tracking subdomain on your own domain
- Browser + server events deduplicated by shared event ID
- Click IDs and Meta cookies preserved from landing to checkout
- Purchase events that work even inside the locked checkout
How BonicBD is designed to help
- First-party delivery through
tracking.yourstore.com - Click ID Restorer for
fbclid/gclid/ttclid - Cookie Keeper — up to 365-day identity where browsers allow
- Conversion ledger to reconcile Shopify orders vs platform reports
Typical rollout
What a BonicBD Shopify setup usually looks like
1
Audit the current signals
We compare Shopify orders against Meta and GA4 to find which events are missing or duplicated.
2
Point your tracking subdomain
One CNAME such as tracking.yourstore.com to connect.bonicbd.com. SSL provisions automatically.
3
Install three snippets
Paste the generated snippets into theme.liquid — no app install, no theme rebuild, no developer required.
4
Verify in the dashboard
Confirm purchases, click IDs, and match quality from the live event stream before scaling spend.
Setup walkthrough
How server-side tracking actually runs on Shopify
The full path — from storefront snippet to Meta CAPI — compressed into the steps a Bangladesh Shopify store actually goes through.
Step 1 — Keep the Pixel, add the first-party path
Your existing Meta Pixel keeps firing. BonicBD adds a parallel server-side route, so browser and server events reinforce each other through deduplication instead of competing.
- Existing Pixel untouched
- Same
event_idshared on both channels - No downtime during migration
Step 2 — CNAME your tracking subdomain
Create a GTM server container, paste the container config into your BonicBD dashboard, and point a CNAME like tracking.yourstore.com to connect.bonicbd.com.
- CNAME →
connect.bonicbd.com - Free SSL auto-provisioned
- First-party endpoint on your domain
Step 3 — Paste the snippets into your theme
Three generated snippets go into theme.liquid head and body — or a header/footer app if you prefer. Order status page scripts or order webhooks carry the Purchase event, so locked checkout pages never block it.
- No Shopify app subscription required
- Purchase works despite checkout limits
- COD confirmation events supported
Step 4 — Validate before you scale
Use Meta Test Events and the BonicBD conversion ledger to confirm each Purchase arrives once with clean identifiers. Most stores see match quality improve within the first days.
- No duplicate Purchase events
- Event Match Quality improves
- Ledger reconciles against Shopify orders
Comparing platforms first? Read Shopify vs WooCommerce server-side tracking for Bangladesh, or see the WooCommerce version of this guide.
Shopify tracking FAQ
Short answers before you reach out
Yes. Shopify limits what custom JavaScript can do on checkout pages, but storefront snippets plus a server container cover the gaps — and purchase events can be delivered server-side, so checkout restrictions never block them.
It gives you more control. Shopify's native channel sends CAPI events, but with limited control over deduplication, event payloads, and multi-platform routing. A server-side GTM setup keeps dedup under your control and feeds Meta, GA4, and TikTok from one pipeline.
On standard Shopify plans, custom scripts cannot run inside checkout. The purchase signal is instead carried by order status page scripts or server-side order webhooks into your server container — so the conversion event does not depend on checkout JavaScript at all.
Yes. Your tracking subdomain is a CNAME on your own root domain, so first-party cookies apply across the whole store — including checkout — instead of expiring after Safari's 7-day JavaScript cookie limit where browser rules allow.
Yes. Most COD orders never reach an online thank-you page, so the Purchase event should fire from your order-confirmation step server-side — which a first-party server-side path is built to carry.
Most Shopify stores are live within 24 hours. The technical part is one CNAME record plus three generated snippets in your theme — the BonicBD team configures the server container and validates events with you.
Related guides
Keep researching the same buying path
Want us to review your Shopify tracking?
We can look at your current signal path, identify where purchases go missing, and tell you whether BonicBD is a fit before you switch.