Browser pixels miss many purchases. What server-side tracking is, why it matters for Meta, GA4 and TikTok ads, and how to use it on Multipurc in plain language.
If you run Facebook or Instagram ads for your store, you've probably seen this: the ads manager reports fewer purchases than you actually received. Or the "best" ad by Meta's numbers isn't the one that brought real orders. A big reason is incomplete tracking, and server-side tracking is designed to fix much of it.
This guide explains the idea in plain language and how to approach it on Multipurc.
The problem with browser-only tracking
A traditional pixel (Meta Pixel, Google tag, TikTok pixel) runs in the shopper's browser. When the customer reaches the "order complete" page, the pixel sends a "Purchase" event. That can fail because:
- Ad blockers and privacy settings block the pixel.
- iPhone and browser privacy features limit tracking.
- Slow mobile connections drop the request before it's sent.
- The customer closes the page quickly after ordering.
When purchases go missing, the ad platform learns from incomplete data. It may optimise toward the wrong people, and your cost per order rises.
What server-side tracking does
With server-side tracking, your store's server records the event (for example, an order being placed) and sends it directly to the ad or analytics platform. It doesn't depend only on the shopper's browser, so fewer events are lost.
Most setups use both: the browser pixel and server events, with the platform de-duplicating them.
Server-Side Tracking on Multipurc
Multipurc's Server-Side Tracking plugin, per the plugins page, captures store events in your database and sends them server-side to Meta, Google Analytics 4 and TikTok.
Plan availability: at the time of writing, the pricing page lists it on Pro and Elite. Check the pricing page for current details.
What you'll need before setup
- Meta: a Meta Business account, your Pixel (dataset) ID, and a Conversions API access token generated in Meta Events Manager.
- Google Analytics 4: a GA4 property, its Measurement ID and a Measurement Protocol API secret created in GA4 admin.
- TikTok: a TikTok Ads account, pixel ID and Events API access token.
Each platform's interface changes often, so follow the platform's own current help pages to generate these. Keep tokens private and enter them only in your store admin.
Setup outline
- Open Integrations in your store admin and find Server-Side Tracking.
- Read the plugin's How use guide for the current fields and steps.
- Click Configure and enter the IDs and tokens for the platforms you use.
- Save, then place a test order.
- In Meta Events Manager (and the GA4/TikTok equivalents), check that the events arrive. Platforms usually show test or recent events within minutes.
Which events matter most
For a typical Bangladeshi store, focus on the events that describe the buying journey:
- View content: someone viewed a product
- Add to cart
- Initiate checkout
- Purchase: the most important one for ad optimisation
With accurate purchase events, you can run ads optimised for purchases rather than clicks or messages.
A note on Cash on Delivery
In Bangladesh, an order placed isn't always an order paid. Some COD orders are refused or turn out fake. The platform sees "Purchase" when the order is placed. Keep that in mind when you judge campaigns:
- Compare ad-reported purchases with your delivered orders in Multipurc's Orders and Reports.
- If one campaign brings many orders that later return, it may be attracting low-intent buyers. Look at delivered revenue, not just reported purchases.
Privacy and honesty
- Mention in your privacy policy page (CMS → Pages) that you use analytics and advertising tools.
- Only send what's needed for measurement.
- Never share customer data outside these purposes.
Reading results without the ad manager
Even without ads, Multipurc's own analytics and reports (traffic, sales, products, customers) show what's working. The Learning Center has guides on reading the sales report, the products report and analytics. Use them alongside platform data.
Common mistakes
- Wrong pixel ID (often from an old or test pixel)
- Duplicate purchase events inflating results, so check de-duplication in Events Manager
- Judging campaigns only by reported purchases without checking returns
- Changing many ad settings at once right after enabling tracking, which makes it hard to see what improved
Summary
Browser pixels miss sales; server-side tracking recovers much of that signal so your ads learn from real orders. If you're on Pro or Elite and spend on ads, connect Meta (and GA4 or TikTok if you use them), verify events with a test order, and judge campaigns by delivered orders, not just reported purchases.