Ad blockers, iPhone Safari and closed tabs hide real sales from your ads. Trakero sends every order from your own server, counted once, so Meta, Google and TikTok learn from what actually sold.
Free. A real browser checks your pixels, cookies and ad-blocker exposure in about 30 seconds.
1A shopper opens a product page. Her ad blocker stops the Pixel; the same event reaches Trakero through your own domain.
Works with your store and your ad platforms
Why browser tracking misses sales
The shopper paid. The money is in your account. But the pixel in their browser never told Meta or Google, so the ad that brought them gets no credit, and the next ad is aimed worse.
Ad blockers, Brave and many privacy extensions block Meta's, TikTok's and Google's scripts before they load. The purchase happens; the pixel never runs.
Trakero sends the purchase from your server too, so the order reaches Meta and Google whether or not the pixel ran.
On iPhone, Link Tracking Protection strips click ids like fbclid and gclid from links opened in Mail, Messages and Safari Private Browsing, and apps that ask not to be tracked share less. The sale arrives without the click that caused it.
When a click id does arrive, Trakero keeps it for the whole visit and sends it with the order. When it was stripped, the order's hashed phone and email let Meta and Google still match the buyer.
Safari caps cookies written by scripts at 7 days, and at 24 hours when the visitor came from a tracking link. Someone who clicks today and buys next week looks like a brand-new visitor.
With the WooCommerce plugin or the PHP SDK, your own server refreshes the visitor cookie, which Safari does not cut short, so returning buyers are still recognised and credited.
The problem
Pick what your shopper's browser is doing. Watch where the browser Pixel's purchase goes, and where Trakero's does.
A shopper from your Facebook ad places an order.
Illustration of what happens on shoppers’ devices, not a measurement.
Side by side
The same ten orders, tracked by the browser Pixel alone and by the Pixel with Trakero. Sample
Ten sample orders showing the mechanism, not a measured rate. Your numbers depend on your shoppers.
Browser + server is not enough on its own
Adding a server copy to the pixel is the right start. On its own it brings new problems: double counts, silent failures and data the platforms can't match. These are the gaps, and what fills them.
A typical browser + server setup
With Trakero
The pixel and the server each send the purchase, with different ids. Meta counts it twice and your ROAS looks better than it is.
Both copies carry one event id, and a purchase is one per order id, so every platform keeps one.
A send fails because Meta was slow or a token expired. Nobody notices until the numbers drop.
Failed sends retry for hours. Anything still failing shows the reason and what to do, and you are told.
Server events go out with only an IP address, so Meta can match few of them to a person.
Phone numbers (+880 and Bangla digits), email, name and city are cleaned and hashed before they leave, so more events match.
Cash-on-delivery orders are counted when placed, including the ones that get cancelled.
Hold the purchase for 1–48 hours. A cancellation in that time stops it everywhere, pixels included.
To see what happened you open Events Manager, GA4, TikTok and your server logs one by one.
One screen shows every order and what each platform, browser and server, received, skipped or rejected.
Every real sale reaches Meta and Google
from the browser and the server, counted once
The ad systems learn from real buyers
so they find more people like them
Spend goes to what actually sells
fewer taka on ads that only look good
More orders from the same budget
and reports you can trust
The product
Search an order and see each copy that arrived and where it was delivered. When a shopper says they paid, you can check in seconds. Sample store
A customer says they paid? Search the order and see every copy and every delivery.
Browser copy received
14:02:11
Server copy received · merged into the same event
14:02:12
Delivered to Meta CAPI
212 ms · matched on email, phone, fbc
Delivered to Google Analytics 4
184 ms
Delivered to TikTok Events API
236 ms
| Event | Destination | Status | Attempts | Details / Reason |
|---|---|---|---|---|
| Purchase | Meta CAPI | Retrying | 2/8 | Meta returned 503, next try in 2 min |
| Purchase | Meta CAPI | Failed | 1/1 | token expired · Reconnect Meta |
| Purchase | Google Analytics 4 | Delivered | 1/1 | HTTP 200 · 184 ms |
| AddToCart | Meta CAPI | Delivered | 1/1 | HTTP 200 · 198 ms |
| PageView | TikTok Events API | Delivered | 1/1 | HTTP 200 · 236 ms |
| Purchase | Google Ads | Delivered | 1/1 | HTTP 200 · 162 ms |
Deduplication
The order is authoritative. Every copy (browser, server, retry, webhook redelivery) resolves to one logical event, keyed by the order id. That same event_id is sent to Meta, so even Meta's side can't double count.
Send a copy to begin.
Built for Bangladesh
Bengali digits, a trunk 0, dashes, +880. Trakero normalizes it the way Meta and Google each specify, then SHA-256 hashes it before it is stored anywhere. This demo runs the real rules in your browser. Nothing is sent.
{ "em": "–", "ph_digits": "–", "ph_e164": "–" }
Hashes are computed with the Web Crypto API in this tab. Try the same number in different formats: the hash does not change.
Ways to track
Every way comes with every plan, the free one included, and they run together without counting anything twice.
A shopper buys on yourstore.com
The plugin or snippet records the order
Trakero hashes, deduplicates, retries
Meta, TikTok and GA4 count it once
Your pixels, datasets and history stay. Only the system that sends to them changes, one platform at a time.
Read the move guideConnect one platform
Add Meta (or GA4, or TikTok) in Trakero with the same pixel id you use today.
Switch off the old sender
Pause that platform's tag in the old system the same day, so no purchase is sent twice.
Check, then move the next
When Events Manager shows Trakero's events, repeat for the next platform.
Free Cloudflare Workers tracking
Many ads in Bangladesh show how to send Meta events from a free Cloudflare Worker. It can work for a small site. Here is what you take on when you run one yourself, with Cloudflare's own limits.
Set-up
DIY Cloudflare WorkerCopy or write a Worker script, add your tokens as secrets, route your domain to it. Every platform is more code.
TrakeroInstall the WooCommerce plugin, the Shopify app or one snippet. Connect each platform in the dashboard.
Free limit
DIY Cloudflare Worker100,000 requests a day on the Workers Free plan. Every page view and add to cart is a request.
TrakeroA free plan by events a month. Duplicates we drop are never counted.
When the limit runs out
DIY Cloudflare WorkerCloudflare skips the Worker or shows error 1027 until midnight UTC. Those events are not tracked, and nothing tells you.
TrakeroNothing is dropped. Events past your plan are stored and shown; you get a warning at 80%.
Duplicate purchases
DIY Cloudflare WorkerOnly stopped if your script stores every order id and the pixel shares its event id.
TrakeroBuilt in: one purchase per order id, one event id for browser and server.
When Meta or Google fails
DIY Cloudflare WorkerThe request ran once. If it failed, the event is gone unless you build a queue.
TrakeroRetries with backoff; a failed event shows why, with the fix.
Bangladeshi phone numbers
DIY Cloudflare WorkerYou write the cleaning and hashing yourself.
Trakero+880, 01…, Bangla digits and spaces cleaned and SHA-256 hashed for you.
Seeing what happened
DIY Cloudflare WorkerWorker logs show requests, not what each platform did with your order.
TrakeroAn event debugger: every order, every platform, the reply and the reason.
When an API changes
DIY Cloudflare WorkerYou update the script.
TrakeroTrakero updates it; you change nothing.
| DIY Cloudflare Worker | Trakero | |
|---|---|---|
| Set-up | Copy or write a Worker script, add your tokens as secrets, route your domain to it. Every platform is more code. | Install the WooCommerce plugin, the Shopify app or one snippet. Connect each platform in the dashboard. |
| Free limit | 100,000 requests a day on the Workers Free plan. Every page view and add to cart is a request. | A free plan by events a month. Duplicates we drop are never counted. |
| When the limit runs out | Cloudflare skips the Worker or shows error 1027 until midnight UTC. Those events are not tracked, and nothing tells you. | Nothing is dropped. Events past your plan are stored and shown; you get a warning at 80%. |
| Duplicate purchases | Only stopped if your script stores every order id and the pixel shares its event id. | Built in: one purchase per order id, one event id for browser and server. |
| When Meta or Google fails | The request ran once. If it failed, the event is gone unless you build a queue. | Retries with backoff; a failed event shows why, with the fix. |
| Bangladeshi phone numbers | You write the cleaning and hashing yourself. | +880, 01…, Bangla digits and spaces cleaned and SHA-256 hashed for you. |
| Seeing what happened | Worker logs show requests, not what each platform did with your order. | An event debugger: every order, every platform, the reply and the reason. |
| When an API changes | You update the script. | Trakero updates it; you change nothing. |
Cloudflare limits: developers.cloudflare.com/workers/platform/limits (checked 27 Oct 2026)
Setup
Simulation of the real screens, step by step.
Integrations
Events come in from your store and go out to every ad platform, once each.
4.5 KB JavaScript SDK, served from your own domain
POST /v1/events with a secret key, from any backend
Plugin: server-side purchase from the order lifecycle, COD-aware
Typed server SDK with browser attribution from cookies
Reads GA4 ecommerce events from the dataLayer
PHP 7.4+ server SDK, COD order lifecycle
App: order webhooks + Web Pixel (beta until the Shopify App Store listing)
Graph v26.0, event_id dedup with your Pixel
Measurement Protocol, user-provided data, session stitching
Events API 2.0, ttclid + _ttp matching, dedup with your TikTok Pixel
CAPI v3, ScCid + _scid matching, dedup with your Snap Pixel
v5 events, _epik click id, dedup with your Pinterest Tag
Meta (Facebook + Instagram), TikTok, Pinterest, Snap, LinkedIn, X and Microsoft Clarity from one snippet
Conversion rules, li_fat_id + hashed email, dedup with the Insight Tag
twclid + hashed email/phone, conversion_id dedup with the X Pixel
Data Manager API: gclid / gbraid / wbraid and hashed email, phone and address. No developer token
Every event POSTed as JSON to your URL, HMAC-SHA256 signed; private addresses refused
Pricing
Every feature on every plan. Duplicates we drop are never billed.
For a new store finding its feet.
৳0/ mo
$0/ mo
One growing store with steady sales.
৳900/ mo
or ৳9,999 a year, save 7%
$10/ mo
or $100 a year, save 16%
Busy stores and brands with a few sites.
৳2,900/ mo
or ৳29,000 a year, save 16%
$29/ mo
or $290 a year, save 16%
High volume, many stores, agencies.
৳5,900/ mo
or ৳60,000 a year, save 15%
$59/ mo
or $590 a year, save 16%
Duplicates we drop are never billed. Pay in taka with bKash, Nagad, Rocket, Upay, Pathao Pay or bank transfer; your plan starts when the payment is verified.
Dollar prices are for stores outside Bangladesh, set on their own and never converted from taka. Duplicates we drop are never billed. Your plan starts when the payment is verified.
Compare prices
| Service | Free each month | Paid plan near 500K | Price a month |
|---|---|---|---|
TrakeroYou are here | 20,000 events | 500,000 events | ৳900 500,000 events |
| PixelFly | 15,000 events | 500,000 events | ৳1,200 500,000 events ৳900 a month if you pay a year ahead |
| Servero | 20,000 requests | 600,000 requests | $17 600,000 requests |
| Stape | 10,000 requests | 500,000 requests | $20 500,000 requests $17 a month billed yearly |
Monthly prices from each company's own pricing page, checked 24 October 2026. A request in server-side GTM also counts script loads, so the same traffic uses more requests than events.
Free tools
Check, build and debug your tracking in the browser. Nothing you paste leaves the page.
A short email when Meta, Google or TikTok change a tracking rule that affects stores, and when we add a free tool. A few a year. Unsubscribe in one click.
We use your address only for these emails. Privacy policy.
FAQ
Not covered here? Write to us and a person who builds Trakero answers.
No. Keep the Pixel and add Trakero. Both send the same event_id, so Meta keeps one copy and fills gaps from the other. Match quality goes up and nothing is double counted.
Trakero respects consent: when a shopper denies ads consent, no ad cookies are set and no event is sent to ad platforms. It moves measurement onto your own domain and server, which is how Meta and Google recommend sending conversions. It is not designed to evade privacy choices.
Email, phone, name and address are normalized and SHA-256 hashed inside our ingestion service before anything is queued or stored. Raw values never reach our database or logs. Destination tokens are encrypted with AES-256-GCM and can never be read back, even by us in the dashboard.
Your store keeps sending and we keep accepting. Deliveries retry with backoff for about six hours. If your Meta token expires, sending pauses and the events wait. They do not burn their retries. Reconnect, and they go out.
You decide. Send the purchase when the order is placed, confirmed or delivered. The order id makes it count once whichever moment you choose, and a later refund or cancel is linked to the same order.
Stores: WooCommerce through our plugin, any website through the JavaScript SDK, any backend through the server API or the PHP, Node and .NET SDKs, and Google Tag Manager. Shopify is in beta. Destinations: Meta, Google Analytics 4, Google Ads, TikTok, Snapchat, Pinterest, LinkedIn and X, each through its server API, plus browser pixels from one snippet.
Three reasons cover most of it. Ad blockers and privacy browsers stop the pixel from loading. iPhones remove click ids such as fbclid from links opened in Mail, Messages and private browsing. And Safari deletes cookies written by scripts after 7 days, so a shopper who buys a week after clicking looks new. Trakero also sends each purchase from your server, with the same event id and hashed contact details, so Meta still gets it and can match the buyer.
It is the right base, not the whole job. Without a shared event id the same purchase is counted twice; without retries a failed send is lost; without clean, hashed phone numbers Meta can match few server events; and you still have to check every platform separately. Trakero handles all four and shows each order's journey on one screen.
For a small site sending only to Meta, it can work. The Workers Free plan allows 100,000 requests a day; when they run out the Worker is skipped until midnight UTC and those events are lost. Deduplication, retries, phone hashing and a log of what Meta received are yours to build. Trakero has them built in.
It is Trakero, at trakero.com. People sometimes type Trackero or Trakaro; it is the same product: server-side tracking for ecommerce stores, built in Bangladesh.
Create a free account, connect your store and watch a test order arrive in Meta Events Manager.
Free plan · No card needed · Set up in one afternoon