How to Set Up the Meta Pixel and Conversions API Properly
Without working tracking, Meta can't find your buyers. A plain guide to the Meta Pixel and Conversions API, which events to track, and how to check they're working.
If your Facebook and Instagram adverts aren't bringing sales, check your tracking before anything else. In the accounts we audit, it's the most common hidden problem.
Here's what tracking does, how to set it up and how to know it works.
What the Pixel and Conversions API do
The Meta Pixel is a small piece of code on your website or checkout. When someone views a product, adds to cart or buys, it tells Meta.
The Conversions API sends the same information from your server or platform directly to Meta. It's more reliable, because browsers, ad blockers and privacy settings can stop the Pixel from reporting.
Together, they let Meta:
- Show your adverts to people similar to those who bought.
- Report which adverts brought sales.
- Retarget people who visited but didn't buy.
Without them, Meta optimises for whatever it can see, usually clicks, and your adverts drift toward people who click but don't buy.
The events that matter
| Event | When it fires | Why it matters |
|---|---|---|
| PageView | Any page loads | Basic traffic and retargeting |
| ViewContent | A product page loads | Who's interested in what |
| AddToCart | Someone adds a product | Strong buying intent |
| InitiateCheckout | Checkout starts | Who almost bought |
| Purchase | Payment completes | The one Meta optimises for |
| Lead | A form or booking is submitted | For service businesses |
Send the order value and currency with each purchase. That lets Meta optimise for value, not just number of sales, and lets you see return on ad spend.
How to set it up
Step 1: Create the Pixel
In Meta Events Manager, connect a new data source for the web. Name it after your business. You'll get a Pixel ID.
Step 2: Install it
- Shopify, WooCommerce and PayLead have built-in Meta connections. Use them; they usually handle events and the Conversions API for you.
- Custom websites need the Pixel code in the page head, plus event code on product, cart, checkout and thank-you pages. Your developer should also set up the Conversions API from the server.
Step 3: Turn on the Conversions API
Most platforms have a simple setting or a partner connection. If you're on a custom site, your developer can send events through Meta's API. Make sure each event has an event ID so Meta can match browser and server events and avoid counting them twice.
Step 4: Verify your domain
In Business Settings, verify your website domain. It helps with reporting and control over events.
Step 5: Test with a real order
This is the step most people skip. Place a real, small order and check:
- Does the Purchase event appear in Events Manager?
- Does it show the right value in cedis?
- Does it appear once, not twice?
Use the Test Events tool in Events Manager, and the Meta Pixel Helper browser extension, to watch events fire as you click through.
Common problems
- Purchases counted twice. Browser and server events without matching event IDs.
- Purchase firing on page view. The event is on a page anyone can visit, not only after payment.
- Wrong currency or value. Revenue shows as GH₵ 0 or in the wrong currency.
- Events missing after payment. The buyer pays on a payment page and never returns to your thank-you page.
- Two Pixels on one site. Data split across accounts.
What if you sell on WhatsApp?
Many Ghanaian sales finish in a chat, which the Pixel can't see. Options:
- Use click-to-WhatsApp campaigns and optimise for conversations, then track sales separately.
- Send payment links from a checkout that has the Pixel installed, so the purchase is recorded.
- Upload offline sales to Meta.
See how to track sales that close on WhatsApp.
Check it every month
Tracking breaks quietly. A website update, a new checkout or a plugin change can stop events. Once a month, compare purchases in Events Manager with your real orders. If they're far apart, investigate.
Common questions
Do I need a developer?
Not on Shopify, WooCommerce with a good plugin, or PayLead. For custom sites, usually yes.
Is the Conversions API really necessary?
For serious advertisers, yes. It recovers events the browser misses and gives Meta better data to learn from.
Will tracking break privacy rules?
Be clear in your privacy policy that you use tracking for advertising, and follow Ghana's Data Protection Act. Don't send sensitive personal information as event data.
If you'd like it set up and tested for you, see our tracking and attribution service.