Every decision you make in Facebook ads rests on one number: how many results the campaign delivered. If that number is wrong, everything built on it is wrong too — cost per result, ROAS, which campaign to scale and which to pause. Worse, the algorithm itself learns from those numbers. If it never sees your real purchases, it goes looking for the wrong people.
This article explains in plain terms what the Meta Pixel and Conversions API are, how to confirm they're working, and the common problems that make a winning campaign look like a failure.
What are the Pixel and Conversions API?
| Meta Pixel | Conversions API | |
|---|---|---|
| Where it runs | In the visitor's browser, via code on your site | From your site's or store's server directly to Meta |
| What it sends | Page views, add to cart, purchases… | The same events, from the server side |
| Weak spot | Affected by ad blockers and privacy limits in browsers and phones | Needs technical setup or a ready-made integration from your store platform |
Ideally both run together: the Pixel in the browser and Conversions API from the server, with each event carrying the same Event ID so a purchase isn't counted twice. That's called deduplication.
Checking your tracking in 5 steps
- Open Events Manager and select the dataset (pixel) linked to the account. Make sure key events like Purchase and Lead have received data in recent days.
- Use the Test events tool in Events Manager: open your site, complete a test purchase or sign-up, and watch the event appear in real time.
- Install the Meta Pixel Helper Chrome extension and browse your pages to see which events the pixel fires on each one.
- Check each event's source: Events Manager shows whether an event arrived from the browser, the server or both, and whether deduplication is working.
- Compare with reality: purchases in Events Manager over a week versus orders in your store for the same week. They won't match exactly, but a big gap means a problem.
Common tracking problems and their signs
| Problem | Sign |
|---|---|
| Pixel missing from the thank-you page | Visits and add-to-carts, but almost no purchases |
| Purchase event firing twice | More purchases in Ads Manager than real orders |
| Purchase value missing or in the wrong currency | ROAS of zero or a nonsensical figure |
| A website or store theme change | A sudden drop in events from the day of the update |
| Checkout on an external domain | The customer pays on the payment gateway's page and never returns to the thank-you page |
Event Match Quality
When your site sends an event, it can also send details that help Meta identify who performed it — such as email or phone number, hashed. The more complete these are, the more accurately Meta can match the event to the person who saw the ad. Events Manager shows a match-quality rating per event, and improving it usually means sending available customer details through Conversions API, in line with your privacy policy and user consent.
Ways to set up Conversions API
| Method | Suits | Notes |
|---|---|---|
| A built-in integration from your store platform | Most stores on well-known platforms | Easiest and safest; usually enabled in the platform's settings |
| A partner integration or plugin | Sites on popular content management systems | Make sure the plugin is up to date and trustworthy |
| Conversions API Gateway | Those wanting a Meta solution without full development | Needs setup on a cloud service |
| Direct development | Custom sites and large systems | Full flexibility, but needs a developer and ongoing maintenance |
Whichever method you use, check three things: that the purchase event sends the correct value and currency, that each event carries an Event ID matching the same event from the pixel, and that personal data is sent hashed and in line with user consent.
A quick checklist for the purchase event
- Does it fire only once per order, even if the customer reloads the thank-you page?
- Is the value sent the actual order value, not a fixed number?
- Does the currency match the store's currency?
- Does it work with every payment method, including cash on delivery and external gateways?
- Does it work on mobile as well as desktop?
These five questions catch most of the tracking errors that push Ads Manager ROAS far from reality.
It's worth running through the checklist whenever you onboard a new client, change payment providers or launch a new checkout flow — tracking problems are much cheaper to catch on day one than after a month of misleading numbers.
When to suspect tracking rather than the campaign
- A sudden drop in results across every campaign on the same day.
- Your store records orders from ads, but Ads Manager shows far fewer.
- Click-through rate and visits look normal, but results are zero.
- The change followed a site update, a new payment gateway or a new thank-you page.
In those cases don't touch the campaigns before checking tracking — you could pause a winner because of a wrong number. For other reasons a campaign spends without results, read Facebook Campaign Spending With No Results? How to Stop the Bleed Early.
Habits that protect tracking accuracy
- Test after every site update: one test purchase after any change to the theme or checkout pages.
- Use your store platform's integration: most major store platforms offer a ready connection to the Pixel and Conversions API, which is safer than hand-written code.
- Review Events Manager weekly: a quick look at event counts and any warnings.
- Watch for spend without results: a campaign spending but recording nothing may be the first sign of broken tracking.
Raqeeb Ads alerts you when a campaign spends more than twice its average cost per result with no results — an alert that often exposes a tracking failure the same day, before days of data and budget are lost. You can also compare results day by day in the Campaign Analyzer to spot a sudden drop across every campaign at once.
A free tool that helps here: The UTM builder writes the tracking link, or the dynamic parameters you add to your ads once.