Facebook Pixel and Conversions API for your online store in Bangladesh

Almost every online store in Bangladesh runs Facebook ads. Far fewer have a working pixel, and fewer still send purchase events from the server. The difference shows up in the ad account: a store with good tracking tells Meta exactly which visitors bought, and Meta finds more people like them. A store without it is paying for clicks and guessing.

This guide covers what the Meta Pixel actually does for a shop, the handful of events that matter, why the Conversions API (CAPI) became necessary, and how to set both up on your store — with or without a developer. We keep to what you can verify in your own Events Manager; there are no benchmark figures here because they vary by store and change constantly.

What the pixel does, in plain terms

The Meta Pixel is a small script on your website that tells Meta what visitors do: which pages they view, what they add to the cart, when they start checkout, and when they buy. Meta uses that information for three things that directly affect your ad spend:

• Optimisation. When you run a campaign optimised for Purchase, Meta shows the ad to people it predicts will buy — but it can only learn that if it sees your purchases. No purchase events, no learning.
• Retargeting. You can show an ad to everyone who added to cart in the last seven days and did not buy. That audience only exists if the pixel recorded the add-to-cart.
• Measurement. Ads Manager reports how many purchases each campaign produced, so you can turn off the ones that do not pay for themselves.

A store running ads without a pixel is not just losing data; it is paying Meta to optimise for the wrong thing.

The six events that matter for a store

Meta supports many standard events. For an ecommerce store, six cover almost everything:

Event	Fires when	Why it matters
PageView	Any page loads	Baseline; builds the "visited my site" audience
ViewContent	A product page loads	Product-interest audiences; catalogue ads
AddToCart	Customer adds an item	Strongest retargeting audience
InitiateCheckout	Checkout page opens	Abandoned-checkout audiences
Purchase	Order is placed	The event you optimise and measure on
Lead	A form is submitted (e.g. a call-back request)	Optional; for stores that sell by phone

Each event can carry values — the product, the price, the currency — and Purchase should always carry the order value in BDT so Ads Manager can report revenue, not just counts. Get these six right and there is rarely a reason to add more.

Why the pixel alone is no longer enough

For years the pixel did the whole job from the browser. Two things changed that. Apple's App Tracking Transparency and later privacy changes mean many iPhone users' activity is not reported by the browser pixel. And ad blockers, strict browser tracking protection and slow connections mean a portion of events simply never leave the visitor's device.

The Conversions API fixes this by sending events from your server, not the browser. When an order is placed, your store's server tells Meta directly: this purchase happened, here is the order value, here is a hashed version of the customer's phone or email for matching. That event arrives whether or not the browser pixel fired.

Meta's recommended setup is both: the pixel in the browser and CAPI from the server, with the same event ID on each so Meta can deduplicate and count each purchase once. In practice, most stores only need CAPI for Purchase — it is the event that carries money and the one most worth protecting; the browsing events are fine from the pixel alone.

Where to find your Pixel ID and access token

Both come from Meta Events Manager (business.facebook.com → Events Manager):

1. Pixel ID. Select your data source (the pixel), and the ID — a long number — is shown under its name and in Settings. If you have never created one, Connect data sources → Web → Meta Pixel creates it.
2. Conversions API access token. In the same pixel's Settings, scroll to Conversions API and use Generate access token. Copy it once and store it safely; it is a credential, not a public ID.
3. Test event code (optional). Under Test events, Meta shows a short code you can use to see events arrive in real time while setting up, without polluting your live data.

Make sure the pixel belongs to the same Business Manager as your ad account, or campaigns cannot optimise on its events.

Installing it on your store

Custom-built site. A developer adds the base pixel code to every page, fires each event with the right parameters at the right moment, and builds a server-side CAPI call when an order is created — plus the deduplication IDs, plus updates when Meta changes the API version. It is a real project, and the server-side part is where most implementations are skipped or break.

WooCommerce. Meta's official plugin and several third-party ones handle the pixel; CAPI support varies by plugin and version, and the usual plugin-maintenance caveats apply.

Shopify. The Facebook & Instagram channel installs the pixel and supports CAPI, but Shopify itself is a poor fit for Bangladesh for the reasons we cover in Shopify in Bangladesh.

Eazifiy. On Eazifiy the pixel and CAPI are part of the platform. Under Integrations in the admin you open the Facebook Pixel card and paste:

• Your Meta Pixel ID — and optionally a second Pixel ID, for stores that run ads from two ad accounts or share a pixel with an agency.
• Your Conversions API access token for each pixel. With it in place, every Purchase is also sent server-side from Eazifiy's backend, with a matching event ID so Meta counts it once.
• A test event code while you are verifying.
• Your TikTok Pixel ID, Google Analytics measurement ID and Google Tag Manager container ID in the same place if you use them.

The six events above fire automatically with product, value and currency filled in — no code, no tag-by-tag setup. A per-event switch lets you turn any event off entirely, for both pixels and for CAPI alike, if your ad strategy does not need it. Pixels are available on the Lite and Premium plans; the Starter plan does not include them.

Verifying that it works

Never assume a pixel is working because the script is on the page. Check it:

1. Test events. Open Events Manager → your pixel → Test events, enter the test code on your store's pixel settings, then browse your own storefront: open a product, add to cart, start checkout, and place a test order. Each event should appear within seconds, and the purchase should show both a Browser and a Server entry that Meta reports as deduplicated.
2. Meta Pixel Helper. The free Chrome extension shows which events fire on the page you are viewing and flags common mistakes such as a missing currency.
3. Overview after 24 hours. In Overview, event counts should roughly track your real orders. If purchases in Events Manager are far below purchases in your admin, CAPI is not sending or the token is wrong.
4. Event Match Quality. Meta scores how well your server events can be matched to real people. Sending a hashed phone number and email with each purchase — which the server-side call does — is what raises it.

Remove the test event code when you are done, or your live events keep landing in the test view.

Frequently asked questions

Do I need a Business Manager account? It is strongly recommended. The pixel, the ad account and the Facebook page should all live in one Business Manager so events, audiences and campaigns connect properly.

Can I use one pixel on my Facebook page shop and my website? The pixel belongs to the website. Your Facebook page's own activity is tracked by Meta already; the pixel is what adds your website's behaviour to it.

Is the Conversions API only for Purchase? It can send any event, but Purchase is the one that matters most and the one Eazifiy sends server-side by default. Browsing events from the pixel alone are usually sufficient.

What about Google Ads and TikTok? TikTok has its own pixel and Google uses Analytics or Tag Manager; on Eazifiy their IDs go in the same settings screen, and the same six events fire to each.

Will the pixel slow my site down? A well-implemented pixel loads after the page content. On Eazifiy the tracking scripts are loaded after the page has painted, so they do not delay what the customer sees.

Ready to stop guessing which ads work? Pixels and the Conversions API are included on the Lite and Premium plans, and the first 2 months are ৳200 a month on any plan — see pricing or the full feature list.