Advertising
Meta Pixel explained: what it is and why you combine it with CAPI
Copy for AI
The Meta Pixel is a small piece of code you place on your website to measure which actions visitors take, to attribute those actions to your ads on Facebook and Instagram, and to build audiences for remarketing and lookalikes. In short: without the Pixel, Meta has no idea what happens after someone clicks your ad, and you have no idea which euro of ad budget produced a lead.
TL;DR: the Meta Pixel records events (a form filled in, a quote requested, a demo booked) and sends them to your ad account. That shows you which campaigns lead to real conversions, and lets Meta point your budget at people who are likely to convert. But since browsers started restricting cookies and tracking scripts, the Pixel on its own misses more and more data. That is why you connect it to the Conversions API (CAPI), which sends conversions server-side. And in Belgium and the EU the rule is simple: you only track after valid cookie consent. Skip that and you are not just flying blind, you are also taking a GDPR risk.
What exactly does the Meta Pixel do?
According to Meta, the Pixel is a piece of code you place in your website that does three things which matter to B2B advertisers.
First, it measures conversions: the actions on your site that genuinely count. For a webshop that is a purchase, but you are not a webshop. In B2B it is a completed contact form, a downloaded whitepaper, a requested demo or a booked call. The Pixel records that action as an event and links it to the ad the visitor came from.
Second, it feeds audiences. Everyone who visited your site or viewed a particular page can be approached again. That is the basis of remarketing and specifically of retargeting through B2B social ads. Meta also uses that data to build lookalike audiences: people who resemble your best leads.
Third, it delivers insight: which campaign, which ad and which audience actually produce leads, not just clicks. That difference is the whole point. Clicks are cheap, leads that turn into revenue are not. A properly configured Pixel is therefore the foundation under every social ads campaign we run for B2B clients.
How does the Pixel work under the hood?
Technically the Pixel is a JavaScript snippet that sits in the <head> of your site. Whether it fires correctly is easy to check with a browser tool such as the Meta Pixel Helper. On every page view, the base code fires a PageView event. For specific actions you add extra events.
Meta works with a set of standard events. The most useful ones for B2B are:
- Lead: someone leaves their details, for example through a contact form or a whitepaper download.
- CompleteRegistration: someone completes a registration or sign-up, for example for a webinar or an account.
- ViewContent: someone views an important page, such as your services page.
- Contact: someone gets in touch.
You can attach parameters to every event, such as a value or a category. That way you can count not only how many leads come in, but also which ones are worth more. A request for a large project weighs heavier than a newsletter sign-up, and parameters make that distinction visible.
A short historical note, because it helps to understand the logic. Meta used to work with two separate pixels: one for tracking your audience and one for conversions. According to Meta, those were merged into a single Pixel that handles both jobs. That made installation simpler and your site faster, because there is less code on your page. Site speed counts towards your findability through the Core Web Vitals, so it was not a detail.
Want to understand more broadly how event measurement works across Meta, Google Ads and GA4? Then our explainer on event tracking is your starting point. This article sticks to the Meta Pixel specifically.
Why is the Pixel alone no longer enough?
Here is the honest story you do not read everywhere. The Pixel runs in your visitor’s browser. And the browser is exactly the place that has been locked down more and more in recent years.
Browsers like Safari and Firefox block third-party cookies by default and restrict tracking scripts. Ad blockers pile on top of that. The result: part of your conversions never reaches Meta. Your Pixel does not fire, the event does not arrive, and in your reporting it looks as if that ad produced no leads, while it did. Your ROAS then looks worse than reality, and you optimise on the wrong data.
That is a serious problem if you want to steer your social media advertising on results. If you judge ads on incomplete data, you put budget on the wrong campaigns. And in PPC, where every euro has to be weighed against a lead, that is expensive.
What is the Conversions API and why do you connect it?
The solution is called the Conversions API, CAPI for short. Where the Pixel measures from the browser, CAPI sends conversions straight from your server to Meta. That server side sits beyond the reach of ad blockers and cookie restrictions in the browser.
In practice you run both at once, something you can even largely automate. The Pixel catches what it can catch, CAPI fills in what the browser lets slip. Meta merges the two and deduplicates events that arrive through both channels, so you do not double count. The result is a fuller picture of which ads genuinely produce leads.
For a small B2B team that is not a luxury but a necessity. You probably have fewer conversions per month than a webshop, so every missed lead distorts your picture harder. The lower your volume, the more it matters that you measure every conversion. Without Pixel plus CAPI you are partly flying blind, and then you steer your budget on gut feel instead of on data.
What about cookie consent and the GDPR in Belgium?
This is the part you must not skip. The Meta Pixel collects personal data and sets cookies. Under the GDPR and Belgian privacy law, that is only allowed after your visitor has given valid consent for it.
In concrete terms: the Pixel may not fire before someone has actively clicked accept in your cookie banner. No consent, no tracking. A pre-ticked box or a banner where you cannot refuse does not count as valid consent. The Belgian Data Protection Authority has already enforced this strictly on several occasions.
The same goes for CAPI. The fact that data leaves server-side does not release you from the consent obligation. If you send conversion data for someone who did not consent, you are still breaking the rules. The clean approach is a consent management platform that only lets both Pixel and CAPI fire after consent.
Our honest advice: do not see consent as an obstacle but as a given. You lose some data from people who refuse, and that is simply the price of working within the law. Do not try to get around it. The risk of a fine and reputational damage never outweighs a bit of extra measurement data.
Frequently asked questions about the Meta Pixel
Is the Meta Pixel the same as the Facebook Pixel? Yes. Meta renamed the Facebook Pixel to Meta Pixel when the company became Meta. The technology is the same and covers both Facebook and Instagram.
Do I still need the Meta Pixel if I use CAPI? Yes, you use them together. The Pixel captures browser behaviour, CAPI fills in what the browser blocks. Meta deduplicates the events so you do not double count. CAPI alone misses context that the browser does see, and the Pixel alone misses data because of cookie restrictions.
Does the Meta Pixel work for B2B if I do not have a webshop? Certainly. You then measure leads instead of purchases: completed forms, requested demos, downloaded content. With parameters you can even distinguish valuable leads from less valuable ones.
Can I simply place the Pixel on my Belgian website? No. You may only let the Pixel fire after the visitor has given valid cookie consent. Arrange that through a consent management platform, otherwise you breach the GDPR.
How many conversions do I need for it to work? Meta optimises best with sufficient conversion volume. If you have few leads per month, it is all the more important that you measure every conversion, and therefore that Pixel plus CAPI run together.
Ready to steer your ads on real leads?
The Meta Pixel is not a technical garnish, it is the foundation under ads you can steer on revenue instead of on clicks. Set up properly, connected to CAPI and neatly inside the consent rules: then you finally see which budget produces real leads. We help Belgian B2B companies set up exactly that, without noise and without guesswork.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.