Setting Up the Meta Pixel: Why Your Numbers Are Wrong and How to Fix Your Tracking
Daniel Huber, MBAFounder of Plaith

I've been reading again about what problems are out there. And this time it wasn't about bad ads or costs that are too high. It was about something quieter that still affects every euro of your ad budget: numbers that are wrong.
A shop where purchases simply don't show up. A B2B marketer whose pixel gets a mediocre score. A founder who thought he had won 43 users, and in reality it was about 10. If you type set up Meta Pixel into Google, you'll find plenty of guides to installing it. But what goes wrong in the cases below usually happens after the installation. So this article covers both: setting it up correctly and checking that it really works.
Why the Pixel Decides What Happens to Your Budget
The Meta Pixel is a piece of code on your website. It tells Meta what visitors do after the click: viewed a page, added to cart, bought, submitted a form. Meta uses these signals to do two things:
- It reports results to you. You then decide which ad keeps running and which one you stop.
- It learns who to show your ads to. If you optimize for purchases, Meta looks for people who are likely to buy, based on your past buyers.
If the signals are wrong, both decisions are wrong. You stop good ads, keep bad ones, and Meta looks for the wrong people. That's exactly what the following cases show.
Case 1: The Shopify Shop Where No Purchases Show Up
In r/shopify, a shop owner describes that no AddToCart and no Purchase events arrive in Meta Events Manager (to the original post). That's exactly the two events you optimize a shop on. According to his post, there is also still old pixel code in the theme.
That's a common pattern. At some point many shops copied the pixel into the theme by hand and later set up the official connection through Shopify as well. Then two systems run side by side, or the old code points to a pixel nobody uses anymore.
The lesson: Before you set up the pixel again, clean up. There should be a single, deliberately set up connection through which your shop sends data to Meta. The pixel and the Conversions API may send together, as long as the event name and event ID match.
Case 2: 7 Leads in the First Week, but the Pixel Only Gets a 6.1
In the second case from r/FacebookAds, someone who runs the entire marketing alone at a new B2B company writes (to the original post). The budget is $10 a day, and 7 leads came in during the first week. Actually a good start. But the pixel has a score of 6.1, and the question is: What do I need to improve?
This refers to the event match quality. It shows how well Meta can match an event on your site to a real person. The more matching customer data is sent along, such as an email address or phone number in encrypted form (a so-called hash), the better the matching works. For leads from forms, this is often the weak point: The form is submitted, but all Meta receives is "somebody sent something".
The lesson: A pixel that fires is not yet a pixel that works well. Especially with a small budget, every clean signal counts double.
Case 3: 43 Users in Ads Manager, About 10 in Reality
The third case comes from Indie Hackers (to the original post). A founder writes that he spent around 330 on Facebook Ads for his small SaaS product. He thought he had won 43 users. In the end it was about 10. Meta counted more leads than there were actual quiz completions.
This can happen when the event is triggered in the wrong place. For example already when a quiz is started or a button is clicked, instead of only on the thank-you page after the real completion. Meta then believes the campaign delivers more than four times as many results, and happily keeps optimizing for the wrong clicks.
The lesson: Always compare Meta's numbers with your own. Shop orders, CRM entries, real sign-ups. If the gap is large, the problem is often the event, not the ad.
And a fourth, short case from X: An e-commerce seller asks how to get conversions to show up faster in Ads Manager (to the original post). The delay makes his decisions hard. More on that further down.
Setting Up the Meta Pixel: Step by Step
Meta changes its interfaces regularly, so I describe the steps, not every click.
- Create the pixel in Events Manager. In your Meta Business account, create a pixel under data sources (at Meta this is now often called a dataset) and connect it to your ad account. One pixel per website is enough in most cases.
- Choose one way to install it. Either through an official integration of your shop or website system, through Google Tag Manager, or with code in the header of the page. What matters: only one of these ways, not two at the same time.
- Define the right events. For a shop: page view, product viewed, add to cart, checkout started, purchase. For service providers: page view and lead, triggered only after the form has been successfully submitted.
- Add the Conversions API. The Conversions API sends events directly from your server to Meta, not just from the browser. That helps when browsers or ad blockers slow the pixel down. So that events aren't counted twice, the browser event and the server event need the same event ID and the same event name. Meta then merges them into one event.
- Send customer data along. If you have a legal basis for it, usually consent through your cookie banner, you can transmit it with the event, such as the email from a purchase or a form. That improves the event match quality. So control the pixel and the Conversions API through the same consent.
- Test. With the Test Events function in Events Manager and Meta's browser extension (formerly Meta Pixel Helper, now part of Meta Ads Data Advisor) you check that every event arrives exactly once and in the right place. The extension shows what your browser sends, Events Manager shows what actually arrives at Meta. Events that your server sends are only visible in Test Events.
- Clarify data protection. In the EU, and so also in Germany, you usually need consent through your cookie banner for the pixel, and the pixel may only load after the visitor agrees. On top of that comes your privacy policy. Get advice if you're unsure.
Setting Up the Shopify Meta Pixel: What to Watch For
Case 1 applies especially to Shopify shops. If you want to set up the Shopify Meta Pixel, the best way is to use the official Meta connection through the Facebook & Instagram app in the Shopify admin. There you also choose how much data is shared; from the higher levels (Enhanced and Maximum), the app uses the server connection in addition to the browser. This is also a data protection question: Adjust your cookie banner and privacy policy beforehand.
Then the most important step: Look in the theme for old, manually inserted pixel code and for tracking apps that also send pixel events. Remove everything that's duplicated. Then make a test purchase and check in Events Manager that add to cart and purchase arrive exactly once.
Meta Pixel Not Tracking Purchases: The 5-Minute Check
If you currently feel that your numbers are wrong, go through this list:
- Is anything arriving at all? Open Events Manager and look at the latest activity per event.
- Does it arrive twice? Two installation methods, or a missing event ID on browser and server.
- Does it arrive in the right place? Lead and purchase only after the real completion, not on the click.
- Does the total add up? Compare Meta's numbers from last week with your orders or sign-ups.
- Is the quality good enough? Look at the event match quality and check which customer data is missing.
Why Conversions Show Up Late
Back to the seller from X. Conversions don't always show up immediately in Ads Manager. Data can arrive with a delay, and Meta credits a result to the ad someone came through, even if the purchase happens days later. How far back Meta looks is determined by the attribution window you've set. The numbers from yesterday and today are therefore often not yet complete.
What helps: Don't make decisions based on the current day, but on a period of several days. Set up the Conversions API cleanly. And use your own order data as a cross-check. More about drops that are really measurement problems is in Facebook Ads Not Working Anymore. And if the pixel measures cleanly but still nobody buys, read Improving Your Landing Page Conversion Rate.
What You Get Out of It
Maybe you know this: In the morning you look at Ads Manager, see a number and don't know whether to be happy. Because it doesn't match your orders. Because you don't know whether Meta is telling you the truth right now.
When your tracking is right, you decide for yourself again instead of guessing.
Here's what you can achieve with it:
- Budget you can use more precisely. You can stop the ads that really don't sell and give more to the ones that do.
- A campaign that can learn the right thing. Meta then looks for people who resemble your real customers, not the ones who just clicked a button.
- More calm when you look at the numbers. No more mornings with the feeling that something is off, without knowing what.
Whether your ads end up running profitably depends on your offer, your market and your creatives. Nobody can promise you that. But without clean data, you won't even know.
What This Looks Like at Plaith
Plaith helps self-employed people and small businesses win customers through Meta Ads. At Plaith, 6 specialists, combining people and AI, take care of videos, ad messaging and campaign management, from €26 a day plus a one-time setup. For us, managing campaigns also means being able to trust the numbers that decisions are based on.
If you're not sure whether your pixel is measuring correctly, or you want to hand off the whole campaign management, book a call with René. No sales pressure, and if it isn't a fit, we'll tell you honestly.
Frequently Asked Questions
How do I set up the Meta Pixel?
Create a pixel in Meta Events Manager, connect it to your ad account and install it through exactly one route: official integration, Google Tag Manager or code. Then define the most important events and check them with Test Events.
Why isn't my Meta Pixel tracking purchases?
Common causes are old or duplicate pixel code, an event in the wrong place, missing consent in the cookie banner, or ad blockers. The Conversions API and a test purchase help with the search.
Do I need the Conversions API?
For shops and lead campaigns it makes a lot of sense, because it transmits events even when the browser blocks the pixel. A shared event ID and the same event name are important so that nothing is counted twice.

