Meta Ads Conversion Tracking: A Beginner's Guide to Pixel and CAPI
Many online shops in Bangladesh run Facebook and Instagram ads for months without knowing which ads actually bring orders. They see likes, messages and link clicks, but when sales dip, nobody can say which campaign to cut. Meta ads conversion tracking fixes that by telling Meta, and you, what people do after they click.
Tracking is not only for reports. Meta's delivery system uses conversion data to decide who sees your ads. If it knows which people bought, it can find more people like them. If it only knows who clicked, it finds more clickers.
This guide explains the Meta Pixel, the Conversions API, which events to track, how to test the setup before spending, and the common problems we see with cash on delivery and mobile payment orders.
What Meta ads conversion tracking does
A conversion is any action you care about: a purchase, a submitted form, a booked appointment, a sign-up. Conversion tracking records those actions and links them back to the ad that led there. That gives you three things:
- Reporting: cost per purchase or cost per lead for each campaign, ad set and ad, not just cost per click.
- Optimisation: when you choose a sales or leads objective, Meta shows ads to people more likely to complete that action.
- Audiences: you can retarget people who viewed a product but did not buy, or exclude recent buyers from offers they no longer need.
Without tracking, a campaign that gets cheap clicks from people who never buy can look like your best performer.
The Meta Pixel: tracking in the browser
The Meta Pixel is a small piece of code that runs in the visitor's browser on your website. When someone loads a page or takes an action, it sends an event to Meta.
To set it up, open Events Manager in your Meta business account, choose to connect a new web data source and create a dataset (the newer name for a pixel). You then have three main ways to install it:
- Partner integration: platforms such as WordPress with WooCommerce or Shopify have official Meta integrations that add the Pixel and standard events with little or no code.
- Google Tag Manager: useful if you already manage other tags there and want control over exactly when each event fires.
- Manual code: a developer adds the base code to every page and event code to specific actions, such as the order confirmation page.
For most small shops, the partner integration is the quickest and least error-prone route. A custom-built store needs events added by hand, which is easiest to plan during e-commerce website development rather than after launch. Meta's Meta Pixel documentation covers the details for each method.
The Conversions API: why the Pixel alone is not enough
Browser tracking misses a share of events. Ad blockers, browser privacy settings, iPhone tracking choices, slow connections and people closing the page early all stop some Pixel events from reaching Meta. On mobile data, a thank-you page that loads slowly may never fire its Purchase event.
The Conversions API (often called CAPI) sends events from your server instead of the visitor's browser. Your website or store system tells Meta directly that an order was placed. Because it does not rely on the browser, it catches many of the events the Pixel misses.
Meta recommends using both together. The important detail is deduplication: when the same purchase is sent by the Pixel and by the server, both events must carry the same event name and the same event ID, so Meta counts it once. Without this, your reports can show roughly double the real number of purchases.
Ways to add CAPI include the built-in options in the WooCommerce and Shopify integrations, Meta's Conversions API Gateway, or a direct integration written by a developer. The Conversions API documentation explains the options and the customer information fields you can send.
Sending hashed customer details such as phone number and email with server events helps Meta match the event to a real account. Events Manager shows this as an Event Match Quality score. Phone numbers are especially useful for Bangladeshi shops, since many customers order without giving an email.
Which events to track
Meta has a list of standard events. You do not need all of them. Track the steps that matter for your business:
| Event | When it should fire | Typical use |
|---|---|---|
| ViewContent | A product or service page loads | Retargeting people who looked at a product |
| AddToCart | Someone adds an item to the cart | Retargeting and spotting checkout drop-off |
| InitiateCheckout | The checkout page opens | Measuring how many start but do not finish |
| Purchase | An order is successfully placed, with value and currency | Optimising sales campaigns and measuring return on ad spend |
| Lead | A form is submitted, such as a quote request or admission enquiry | Service businesses, coaching centres, real estate |
| Contact | Someone taps a call or WhatsApp button | Businesses that close sales by phone |
For Purchase, always send the order value and the currency code, BDT if you price in taka. A purchase without a value tells Meta an order happened but not whether it was a 300 taka item or a 30,000 taka one.
If you sell mainly through Messenger or WhatsApp rather than a website, a messages objective tracks conversations instead. That can work well, but conversations are not sales, so keep your own record of which chats turned into orders.
Testing your setup before you spend
Meta ads conversion tracking only helps if the data is accurate, so never launch a sales campaign on tracking you have not tested. A broken Purchase event means Meta optimises on bad data, and you only notice after the budget is gone.
- Use Test Events in Events Manager. Open your site through the test tool, browse a product, add to cart and place a real test order. Each event should appear within a few seconds.
- Check both sources. If you use Pixel and CAPI, the Purchase event should show from the browser and the server, marked as deduplicated.
- Check the values. Make sure the value matches the order total and the currency is correct.
- Install the Meta Pixel Helper. This Chrome extension shows which events fire on each page and flags errors.
- Reload the thank-you page. If refreshing fires a second Purchase, your numbers will be inflated. Fire the event once per order ID.
- Verify your domain in your business settings, so you control which events from your domain are used for ads.
Choosing the right event to optimise for
Meta's system needs enough conversions to learn. As a rule of thumb, an ad set should get around 50 of its optimisation events within a week to leave the learning phase. A small shop with a modest daily budget may get only a handful of purchases a week.
In that case, you have options. You can combine ad sets so each has more budget and more conversions, or optimise for an earlier step such as AddToCart or InitiateCheckout while you build volume, then move to Purchase. Whatever you choose, judge campaigns on real sales and cost per purchase, not on the earlier events.
Common problems and how to fix them
Reported purchases do not match real orders
Some gap is normal. Meta credits a sale to an ad based on your attribution setting, commonly within 7 days of a click or 1 day of a view, and it may model some conversions it cannot observe directly. Your store counts every order regardless of source. Compare trends over a few weeks rather than expecting exact matches.
Cash on delivery orders that never complete
With cash on delivery, an order on the website is not yet a sale. Fake orders, wrong numbers and returns can inflate your Purchase count and teach Meta to find people who order but do not pay. Confirm orders by phone, track your confirmation and delivery rates, and consider sending a separate event or offline update for confirmed or delivered orders so you can see the real cost per sale.
Payments through bKash or Nagad gateways
When customers pay through a mobile wallet gateway, they leave your site and are sent back afterwards. If they close the app before returning, the thank-you page never loads and the Pixel misses the purchase. A server-side Purchase event sent when the payment is confirmed solves this.
Events firing twice or on the wrong page
This usually happens when a theme, a plugin and a manually added code snippet all install the Pixel. Check the page source or Pixel Helper, keep one installation method and remove the rest.
If results stay poor after tracking is fixed, the issue may be the offer, creative or audience instead. Our guide on why Meta ads are not performing covers those causes.
FAQ
Do I need a website to use Meta conversion tracking?
For website events like Purchase and Lead, yes. Without a website you can still use Meta's instant forms for leads or a messages objective for chats, but you lose much of the purchase data that helps optimisation.
Is the Pixel free?
Yes. The Pixel and the Conversions API are free to use. Costs come only from developer time or hosting if you need a custom setup or the CAPI Gateway.
How long before tracking improves results?
Reporting improves immediately once events fire correctly. Delivery usually improves over a few weeks, as Meta collects enough conversion data to learn who is likely to buy.
Does Google Ads use the same tracking?
No, Google Ads has its own tags and setup. If you advertise on both, read our guide on Google Ads conversion tracking as well.
Need help setting up Meta ads tracking?
If your Pixel, Conversions API or events are not set up properly, Nexteio can install and test them, connect your store or forms, and make sure purchases are counted once with the right value. We can also run the campaigns once the data is clean. See our Facebook ads service, or contact us with your website and ad account details.