How to set up your Meta Pixel and run Facebook ads
Updated on 21 Jul 2026 · 8 min read
1. What a Pixel actually does
If you boost a post and someone buys your product, Facebook has no idea the sale happened. It only knows somebody clicked. So it keeps showing your ad to people who click a lot — not people who buy.
A Meta Pixel closes that loop. It quietly tells Facebook “this exact person just paid you ৳850”, and Facebook then goes hunting for more people like them. Same budget, more sales.
Once you paste your ID, SupportKori fires these four events for you automatically. You do not have to write any code:
| Event | Fires when |
|---|---|
| PageView | Someone opens your profile, your store, or any product / course page. |
| ViewContent | Someone opens a specific product or course page. |
| InitiateCheckout | Someone taps Buy Now and gets sent to bKash / Nagad / card. |
| Purchase | The payment actually succeeds — with the real amount they paid. |
The Purchase amount is the real amount paid, after any coupon discount, in the currency the buyer actually used (৳ BDT or $ USD).
2. Find your Pixel ID
Your Pixel lives in Meta Events Manager, not in your Facebook page settings. You need a Facebook account that can access a Business Portfolio (previously called Business Manager) — the free one is fine.
- The browser URL says
/app/instead of/dataset/ - The right-hand panel is labelled App ID, not Dataset ID
- There is a Facebook SDK tab — web pixels don’t have one
- The icon is a phone 📱 rather than a globe 🌐
- 1
Open business.facebook.com/events_manager2 on a laptop. (It is painful on a phone.)
- 2
Look at the Data sources list on the left. If you already have a pixel, it is there — skip to step 5.
- 3
No pixel yet? Click Connect data sources → choose Web → Connect.
- 4
Give it a name (your brand name is fine). Untick the Conversions API checkbox if you see one — read it carefully, it applies to “all new and existing datasets”, so it quietly changes pixels you already have. You don’t need it: SupportKori sends events from the browser.
- 5
When it asks how you want to connect — Partner Integration, Conversions API, Manual — close that step and skip it. SupportKori installs the code for you. You only need the ID. “Categories” is optional; leave it blank.
- 6
Click your new dataset. The ID is the long number shown right under its name — 15 or 16 digits. Copy it.
You are looking for this number:
My Brand Pixel
Dataset ID / Pixel ID
Meta renames things often — you may see it called a Dataset ID instead of Pixel ID. It is the same number. Just make sure it is only digits, with no letters and no spaces.
3. Paste it into SupportKori
- 1
Go to your SupportKori Dashboard.
- 2
Open My Shop (or Courses — either one works, it is the same setting).
- 3
Click the Meta Pixel button.
- 4
Paste the number and hit Save Pixel ID.
That is the entire installation. It goes live instantly across your profile, your store, and every product and course page you own.
4. Check that it actually works
Do not skip this. Spending money on ads with a broken pixel is the single most common way creators waste their budget.
The 60-second check
- 1
In Chrome, install the free Meta Pixel Helper extension.
- 2
Open your own public page — supportkori.com/yourusername. Not the dashboard.
- 3
Click the extension icon. You should see your Pixel ID with a PageView event.
- 4
Now open one of your products. You should also see ViewContent.
You will see two pixels listed — yours and SupportKori’s own. That is normal and correct. Your events go only to your pixel; ours go only to ours. They do not mix.
“No activity received” does not mean it’s broken
A brand-new dataset shows No activity was received and No websites found for a while even when everything is wired up correctly. Events Manager’s Overview tab lags — Meta says up to 30 minutes, and a fresh dataset is often slower. Do not start changing settings because of it.
Trust Pixel Helper or the Network tab for the immediate answer, and let Events Manager catch up in its own time.
Confirming a real sale
Purchase only fires on a genuinely completed payment, so you cannot fake it. Make one small real purchase from yourself — set a product to ৳20, buy it, and watch what the pixel reports.
If you want to watch the events in DevTools, tick Preserve log in the Network tab first. Checkout redirects you to the payment gateway and back, and each redirect wipes the log — without it, InitiateCheckout is invisible and it looks like it never fired.
Test the coupon case specifically. Put a 50% coupon on a ৳40 product, buy it for ৳20, and confirm the Purchase event reports 20 — the amount actually paid, not the ৳40 list price. This is the number Meta optimises your ads against, so an inflated one quietly ruins your ROAS.
A correct Purchase looks like this:
ev=Purchase cd[value] = 20 ← what they paid, not the list price cd[currency] = BDT cd[content_name] = Your Product id = your pixel ID only
Your dashboard also records the sale, so you can always cross-check the pixel’s number against what you actually earned.
5. Run your first ad
Now that the pixel reports sales, stop boosting posts. Boosted posts optimise for likes. Go to Ads Manager and build a proper sales campaign.
The settings below are the short version. For a full walkthrough — budgets, audiences, creative, and how to read your results afterwards — see How to run a Facebook ad that actually sells your product.
| Setting | Choose this |
|---|---|
| Objective | Sales |
| Conversion location | Website |
| Pixel / Dataset | The one you just connected |
| Conversion event | Purchase |
| Website URL | supportkori.com/yourusername/extras/your-product |
| Budget | Start small — ৳300–500/day for 4–5 days |
Send traffic to the product, not the profile
Link straight to the product page you want to sell. Every extra tap between the ad and the Buy button costs you buyers. Use your profile link only when you are running a brand or follower campaign.
Two audiences worth building
In Ads Manager → Audiences → Create Custom Audience → Website:
- Retargeting: people who fired ViewContent in the last 30 days but not Purchase. These are your warmest buyers — they already wanted it.
- Lookalike: once you have roughly 50+ purchases, build a 1% Lookalike from your Purchase audience. This is where the pixel really starts paying you back.
Let it learn. Meta needs roughly 50 conversions a week before it gets good. Do not edit the budget or audience every day — each edit restarts the learning phase and burns your money over again.
6. Common problems
I saved my ID but absolutely nothing happens
Nine times out of ten you saved a Facebook App ID instead of a web Pixel ID. They look identical — both are ~15 digits — and there is no error message, it simply does nothing. Go back to Events Manager and confirm the URL contains /dataset/ and the panel says Dataset ID. See step 2 above.
I can’t find “Pixels” anywhere
Meta renamed them. Look for Datasets in the left sidebar — that is the same thing. You may also need to switch from your personal profile to your Business Portfolio using the account switcher at the top right before Datasets appears at all.
Should I test with my real pixel?
Better not to. Create a second dataset called something like “TEST”, put that ID in SupportKori while you check everything works, then swap in your real one. A fake test Purchase on a brand-new pixel skews exactly the data Meta uses to learn what a real buyer looks like, and you cannot delete events once they land.
Purchase shows the full price, not the discounted one
It shouldn’t — we read the real paid amount from your order record, so coupons are accounted for. If you genuinely see the list price on a discounted sale, that’s a bug worth reporting to us with the order ID.
Pixel Helper shows nothing
You are almost certainly on a dashboard page. The pixel only runs on your public pages — your profile, store, product and course pages. Also check the ID you saved has no stray spaces.
Events Manager says “No activity yet”
Give it 20–30 minutes. Also make sure you actually visited your public page after saving the ID — the pixel has nothing to report until a real visitor loads a page.
Purchase never fires
Purchase fires on the success page after payment completes. If a buyer closes the browser at the bKash screen and never returns, there is no Purchase to record — that is expected. It should still appear as an InitiateCheckout.
Facebook reports fewer sales than SupportKori
Normal, and not a bug. Ad blockers, iOS privacy settings and people buying on a different device all cause under-reporting. Your SupportKori dashboard is always the source of truth for what you actually earned — treat Facebook’s number as a directional signal for optimising ads, not as your accounting.
Should I verify the domain supportkori.com?
You cannot, and you do not need to. Domain verification is only possible for the business that owns the domain, which is us. Your pixel and your Purchase optimisation work fine without it.
Can I use one pixel for two SupportKori accounts?
Yes, but the data will be mixed together in one place and you will not be able to tell the two apart. If you want clean numbers per brand, create a separate pixel for each.
Did this article help you set up?