Meta Pixel and
Conversions API

Why the Meta Pixel alone isn't enough anymore

For years, the Meta Pixel did the job: a snippet of code on your site reported visits, leads and purchases back to Facebook and Instagram. Then browsers began restricting third-party cookies, Apple added tracking prompts on iPhones, and ad blockers became common. Today a noticeable share of pixel events never reaches Meta at all.

That hurts in two ways. Reports in Ads Manager undercount your results, so good campaigns look weak. More importantly, Meta's delivery system learns from conversions. When it sees fewer of them, it has less information about who your buyers are, and it gets worse at finding more of them. Costs per lead tend to rise as a result.

What the Conversions API adds

The Conversions API (CAPI) sends the same events from a server instead of the browser. Because it doesn't depend on the visitor's browser, it isn't affected by most blocking. It can also send events that happen away from the website, such as a lead marked qualified in your CRM or a sale closed by phone.

The two work best together. The pixel catches browser activity with rich context; CAPI fills the gaps and adds business outcomes. Each event carries a shared event ID so Meta can recognize when both report the same action and count it once. Without that, you get the opposite problem: every lead counted twice.

Ways to send server events

There are several routes, and the right one depends on your systems:

• From a server-side Tag Manager container. One server receives website events and forwards them to Meta, Google and others. Best when you want one setup for every platform; see server-side tracking.
• From your website's back end. A custom site or CMS sends events directly when a form is submitted or an order completes. Clean and reliable when the site is built for it.
• From your CRM. Lead status changes and sales are sent as they happen, so Meta learns which leads turned into customers.
• Built-in integrations. Some store platforms offer one-click connections; they work, but need checking for duplicates and missing parameters.

On sites I build myself, server events can be sent straight from the code, which avoids extra tools and monthly fees.

Match quality and privacy

To link a server event to a person on Facebook or Instagram, Meta needs identifiers such as an email or phone number. These are hashed before sending, meaning they're converted into a code that Meta can match but not read as plain text. Including more identifiers usually improves Meta's event match quality score.

Hashing doesn't remove privacy obligations. Under PIPEDA, and more strictly under Quebec's Law 25, you need to tell visitors what you share with advertising platforms and get consent where required. I configure events to respect the consent banner and recommend reviewing your privacy policy; my article on what a website privacy policy needs in Canada covers the basics.

Checking it works

After setup I use Meta's Events Manager to confirm that each event arrives from both sources, is deduplicated, carries the right values and reaches a reasonable match quality. I also compare a week of Meta-reported leads with your actual lead list. The goal isn't a perfect match, which is impossible, but a much smaller gap than before.

Who needs it

If you spend a meaningful budget on Meta ads, especially for an online store or lead generation, CAPI is usually worth it. If Meta is a small test channel, the pixel in the standard $650 analytics setup may be enough for now; we can add CAPI when the budget grows.