The Meta Pixel is what tells your ads who bought and who didn’t. If it works incorrectly, the ads learn from the wrong data and burn your budget. Here is, in plain words, why you need the Conversions API, what is most often broken and how to check your pixel in 10 minutes. The examples come from audits we have done.
What the Pixel and the Conversions API are
- The Pixel is code on your site that runs in the visitor’s browser. It sends events to Meta: product views, add to cart, checkout started, purchase.
- The Conversions API sends the same events from a server instead of the browser. Ad blockers and browser settings can’t block it.
They work best together. Each event travels two ways, and Meta uses a shared event ID to merge the two copies into one. That way nothing gets lost and nothing gets counted twice.
Why you need the Conversions API if you have the Pixel
The browser pixel often doesn’t manage to send an event, or can’t:
- the visitor uses an ad blocker;
- the browser or phone limits tracking;
- the visitor quickly moves to the payment page or closes the tab.
We saw this when setting up the Conversions API for a lamp store. When a buyer went straight from the cart to the payment page, the browser’s checkout event got lost, while the server event arrived. Without the Conversions API, Meta would simply never have known about that action.
What is most often broken
1. Purchases aren’t counted when payment goes through a redirect
A florist in the US had 98 checkouts started in a month, but only 13 purchases in the ad account. Some customers paid by being redirected to a payment provider’s site, and the purchase event didn’t fire. The ads looked worse than they really were, and the algorithm learned from incomplete data.
2. Events are counted twice
Often a site has the platform’s built-in pixel plus another one added manually or through a different plugin. As a result, every view or purchase is counted twice. In the lamp store, product views were doubled exactly this way. We removed the built-in pixel, moved everything to Google Tag Manager and gave each event its own ID. After that, each purchase is recorded once.
3. Different campaigns count different events
At the same florist, one campaign counted purchases as one event and the others as another. You can’t compare such campaigns, and some purchases may not have made it into optimization.
4. Ads optimize for something other than purchases
In one account a campaign spent several months optimizing for checkout started instead of purchase. Meta brought people who happily started checking out but didn’t pay. Before switching a campaign to purchase, make sure the purchase event actually fires correctly.
5. The form lives on another site
A psychology center collected leads through Google Forms. The pixel on the site only saw the click on the button leading to the form, not the submission itself. So the ads optimized for people who clicked the button, not for those who finished. The fix: move the form onto the site, use Meta lead forms, or send leads through the Conversions API.
6. Purchases without a value
The purchase event is there, but without the value and currency. Then you can’t calculate ROAS in the ad account, and Meta can’t look for buyers with bigger orders.
7. Low match quality
Meta rates how well it can match an event to a specific person. At the US florist this score was 6.1 out of 10 because email and phone weren’t being sent with events. For a store without customer accounts, 6 is a normal level, but passing contact details from the order form raises it.
How to check your pixel in 10 minutes
- Open Events Manager → Overview. Check that product views, add to cart, checkout and purchase are coming in.
- Look at the event source. If a server appears next to the pixel, the Conversions API is working. Check that deduplication is happening.
- Place a test order. In the Test Events tab, check that the purchase arrives once, with the correct value and currency. Cancel the test order afterwards.
- Compare with your store. Compare the number of purchases in Events Manager for a week with the number of orders in your CMS or CRM. A big gap is a reason to dig in.
- Check diagnostics. Meta highlights errors and warnings itself.
How we set it up
- The pixel through Google Tag Manager, with a unique ID for each event.
- The Conversions API, where the method depends on your platform. On Shopify, for example, it connects through the official Meta integration and no separate server is needed. If the platform has no such integration, like Weblium, we connect the Conversions API through a separate service: a server-side Google Tag Manager container on stape. For a small store the free plan is enough, and the paid plan costs about $20 a month.
- Deduplication of browser and server events.
- A test order and a check of every event.
- Reconciliation with the CRM to count real sales, not ad account numbers.
We don’t launch sales campaigns without this step: the algorithm learns only from the data it receives. More about how we work with Meta on our Facebook and Instagram ads page. Want your pixel checked together with your ads? Order a free ad account audit: in 2–3 days we review your accounts, events and CRM reconciliation.
FAQ
Does a small store need the Conversions API?
Yes. The fewer purchases you have, the more each one matters: if some of ten weekly purchases get lost, the algorithm has almost nothing to learn from.
Does the Conversions API replace the Pixel?
No, they work best together. The pixel sends data quickly from the browser, and the server backs it up when the browser can’t.
How much does it cost?
The Conversions API itself is free in Meta. On platforms with an official integration, like Shopify, there are no extra costs. If a separate server is needed, the free plan is often enough for a small store.