First-party tracking. Clearer conversion data.
Server-side GTM on a subdomain you own — so the events your ad budget already paid for actually reach Meta, Google and TikTok. Plans in BDT, help over WhatsApp in Bangla, and a dashboard you can check yourself instead of taking our word for it.
{
"event_name": "purchase",
"event_id": "b4f1c9a2-7d0e",
"action_source": "website",
"value": 2450,
"currency": "BDT",
"match_quality": 8.4
}
The clicks happened. The reports just never heard about them.
Three ordinary things break browser tracking on Bangladeshi storefronts. If your Meta numbers and your order sheet keep disagreeing, it's almost always one of these.
check your own numbers before blaming the ads
-
Ad-blockers eat the request
A meaningful slice of paid traffic — industry estimates put it at 10–30% depending on audience and device — runs an extension that blocks third-party pixel domains. The purchase is real; the event dies in the browser and Meta never learns about it.
-
Safari forgets in seven days
Apple's Intelligent Tracking Prevention expires first-party JavaScript cookies after seven days on Safari and every iOS browser. Retarget anyone on a longer window and they come back as a stranger, with their original click unattributed.
-
Click IDs get stripped before your code runs
Platforms tag landing URLs with
fbclid,gclidandttclidso they can match a click to a sale. Extensions and privacy settings sometimes remove those parameters before your JavaScript executes — and the platform is left with a conversion it can't claim.
How BonicBD is designed to close these gaps
Events travel through a subdomain you own before they go anywhere else, so common ad-blocker patterns no longer match. Cookie Keeper keeps identity alive far longer where the browser allows it. The Click ID Restorer captures click parameters server-side, before anything can strip them.
A first-party infrastructure approach, not a browser-side patch.
Most tracking "fixes" change what happens inside the browser. We changed where the data goes: through a subdomain you own, before any ad platform sees it. The gaps above are mostly architectural, and architecture is the thing you can actually fix.
Your subdomain is the front door
Events hit tracking.yourdomain.com first. Common ad-blocker lists match third-party hosts, not yours — so more of the traffic you already paid for arrives intact.
Identity that outlives the cookie
Click IDs and visitor identity are stored server-side through Cookie Keeper, extending persistence up to 365 days where the browser and consent setup allow it.
You see what leaves the building
GTM forwards to Meta CAPI, GA4, TikTok and more — with enrichment and deduplication you can inspect live, instead of hoping the pixel did its job.
BDT, bKash, no FX surprise
Pay in Taka through bKash, Nagad or bank transfer. Every module is bundled into the plan — no à la carte pricing, no surprise invoice.
Three steps, and the first one is the only one that needs your DNS login
Real setup time depends on DNS propagation, who owns your GTM account, and how many destinations you're wiring up. Most stores are collecting events the same day — the slow part is usually waiting on the DNS record to propagate.
Paste your container config
Create a Server Container in GTM, copy the Container Config string, and paste it into your BonicBD dashboard. No code, no deploy pipeline.
Point one CNAME at us
Add a single CNAME — something like tracking.yourstore.com → connect.bonicbd.com. SSL is issued and renewed for you.
Watch it run, yourself
Live event stream, dispatch health per platform, and a conversion ledger you can reconcile against your own orders — not a PDF we send you once a month.
What we can actually promise about your data
We'd rather be specific than impressive. Here is what the setup does, and where the honest limits are — so you can decide whether it satisfies your own requirements before you sign anything.
Encrypted end to end
Every request to your tracking subdomain travels over TLS, with Let's Encrypt certificates issued and renewed automatically for your hostname.
Your container, your shard
Each client's container runs in its own environment, and event data is written to a per-client database shard. Credentials are scoped to one account.
Consent Mode v2 built in
Consent Mode v2 support and configurable geo defaults are available out of the box. Whether that satisfies your compliance obligation depends on your setup and legal review — we'll tell you what we can't answer.
We see it break before you do
Containers are health-checked continuously and restarted on failure, on BDIX-connected infrastructure. When something significant happens, clients hear it from us first.
Four jobs, done properly
The features page lists all twelve modules. These four are the ones that change your reports — the rest exist so these keep working.
Every event lands on a domain you own
Your storefront talks to tracking.yourdomain.com, not to a third-party host. Browser rules, consent choices and your own tag configuration decide what can be collected — but the request no longer trips the blocklists that catch everyone else.
The same visitor, thirty days later
Cookie Keeper and the Click ID Restorer keep identity and click attribution alive server-side, so a customer who came back three weeks later still shows up as the same person — not as a fresh prospect.
Sent where it needs to go, without duplicates
GTM forwards to Meta CAPI, GA4 and the rest with server-side enrichment and event_id deduplication, so a purchase counted in the browser isn't counted twice at the platform.
A ledger you can reconcile, not a screenshot
Every conversion is recorded with value, currency and attribution window, so you can put it next to your order sheet and see exactly where the two differ — which is the only way to know your tracking is honest.
Compare the trade-offs before you choose
Review setup requirements, billing basis, included capabilities, and support scope side by side. Provider offers change, so verify current terms before buying.
Need a provider-by-provider breakdown?
See the comparison page for scope and practical trade-offs, then review each provider’s current plan details.
Choose the request capacity and support tier you need
Core tracking modules are included. Compare request limits and support tiers to find a plan that fits.
Free trial on every plan · No credit card to test · Annual billing saves 10%
What changed once the events stopped dying in the browser
These are client-reported numbers, not audited ones. Outcomes depend on site type, traffic mix and what the previous setup was doing wrong — so treat them as direction, not a guarantee.
“For months I assumed Meta was inflating its numbers — our WooCommerce orders never matched the ad reports. Turned out the sales were real; the events were just dying in the browser. Both dashboards finally tell the same story.”
Two more, in their own words
“Most of our ad budget goes to Meta for kids' fashion, so finding out how many paid clicks were landing without a click ID was honestly a shock. The dashboard made the leak obvious in one afternoon.”
Md. Abu Hanif · Founder, KidsCover BD — +28% click ID coverage“I run server-side tracking for 25+ clients on these servers. Performance has been steady, and with enrichment I'm getting Event Match Quality up to 8.3 across events.”
Rubel Hasan Rokib · Server-Side Tracking Expert — EMQ up to 8.3Answers to Common Questions
Normally, your visitor’s browser sends tracking events directly to Meta, Google, or TikTok servers. Common ad-blockers recognise those destinations and may block the requests. With server-side tracking, events are sent to a subdomain you control — like tracking.yourdomain.com — and your server forwards them to the ad platforms. Because the initial request goes to your own domain, many common ad-blockers are less likely to intercept it. It does not bypass all forms of tracking prevention, and the final result still depends on browser and consent settings.
Setup time varies with DNS propagation, platform access, and GTM configuration. Follow the documented steps, then validate collection in the dashboard, GTM Preview, and the destination platform. Contact support if you need help troubleshooting.
Yes — BonicBD works across common ecommerce platforms and custom sites. If you can paste the three snippets we generate into your site's <head> and <body> (or use a header/footer plugin), it will usually work. We have step-by-step guides for Shopify, WooCommerce, WordPress, Laravel, custom PHP, and Node.js sites. In most cases, you won't need a plugin, SDK install, or backend code change on your end.
Upgrades are handled in place with no rebuild required. Your tracking domain, GTM container configuration, event history, and settings stay intact while we increase your request quota and container resources and prorate the billing difference. In normal cases, event collection continues through the change. Many clients start on Go or Starter and move up as traffic grows.
For Bangladesh: bKash Merchant Payment, Nagad, Visa/Mastercard, and bank transfer (City Bank PLC). Annual billing is available with a 10% discount. For international clients, we accept bank transfer and can arrange invoice billing on request. All payments are processed through SSL-encrypted gateways.
Yes. Every plan includes a free trial container — you can verify DNS propagation, test GTM configuration, and confirm event flow before paying anything. No credit card required to start testing. You only pay when you're satisfied that data is flowing correctly.
BonicBD is the strongest fit for Bangladesh and South Asia ecommerce teams that want managed server-side GTM, first-party Meta CAPI and GA4 delivery, BDT pricing, local payment options, and Bengali or English engineer support — without maintaining Google Cloud or custom DevOps infrastructure themselves.
Yes — that’s the core positioning. Stape.io is a well-established product, but it’s priced in USD, charges separately for some modules, and offers English-only support during Western business hours. BonicBD provides comparable server-side GTM infrastructure with three practical differences: BDT pricing starting at ৳1,000/month, bKash and local bank payment options, and Bengali-speaking engineers on WhatsApp during Bangladesh business hours. The core capability — first-party tracking domain, reduced ad-blocker interference, Cookie Keeper, and Click ID Restorer — is comparable. The pricing, payment experience, and support model are built for the Bangladesh market.
Last updated: 2026-09-18 · Reviewed by BonicBD’s tracking engineers — Patuakhali, Bangladesh.
Replace Guesswork With Verified Tracking Data.
Set up tracking on a first-party domain with guidance from our team. Every feature included, no surprise add-on fees, and WhatsApp support when you need help.
Questions? Read the setup docs, compare plans, or message us on WhatsApp.