Meta Pixel, Events Manager and Conversions API: How to Set Up and Fix Your Tracking (2026)

The Meta pixel is code on your website that sends what visitors do to Meta from their browser. The Conversions API sends the same events from your server, so they still arrive when a browser blocks the pixel. Events Manager is where you see, test and fix both. Use them together, give each event a shared event ID so Meta counts it once, and check everything with the Meta Pixel Helper and Test events.

Last updated: 12 October 2026.

I've managed $35M+ in Meta ad spend across 50+ brands, and when an account underperforms, broken tracking is one of the first things I find. I like to think of tracking as your digital receipt system. Just like a shop owner can see who bought what and when, tracking shows you what happens after someone sees or clicks your ad, so you're not spending money in the dark.

It matters for a second reason that most people miss. I describe the Meta algorithm as a silent super employee, the best media buyer in the world working for you around the clock, except that it can't talk. Your tracking is how you talk to it. Your conversion event is your targeting, because Meta studies the people who complete the event you optimize for and finds more people like them. Every event that's missing, duplicated or wrong teaches the algorithm the wrong lesson.

This guide covers what each tool does, how to set them up, how to check them, and the problems I fix most often. If you're brand new to Meta ads, start with my complete beginner's guide to running Facebook ads and come back here for the tracking part.

What Is the Meta Pixel?

The Meta pixel is a small piece of code on your website that works like a digital notepad, writing down what visitors do on your site. When someone lands on a page, it records the visit, and when they take an action you care about, it sends an event to Meta.

Here's what the pixel picks up about each visit:

• Browser and device, like Chrome on an iPhone, which in most accounts means mobile.
• URLs, meaning the pages people view and where they came from.
• General location, like the city or country, based on the IP address.
• Cookie data, which tells Meta whether someone has visited before and makes retargeting possible.
• Timestamps, showing when people interact with your site.
• Events, the specific actions you track, like Lead or Purchase.

Meta then compares this activity with what it knows from Facebook and Instagram. If someone clicked your ad, visited your site and then bought something, Meta links that sale to the ad, which is how you see which ads drive real results.

Standard events, custom events and custom conversions

Meta gives you 17 standard events with fixed names, such as ViewContent, AddToCart, InitiateCheckout, Purchase, Lead, CompleteRegistration, Contact, Schedule and Subscribe. Use them wherever you can, because Meta understands them across every account and can optimize for them straight away.

What Is the Conversions API (CAPI)?

Since Apple's iOS 14 changes, people can opt out of tracking on their devices, and browsers and ad blockers stop a share of pixel events from ever reaching Meta. The Conversions API was Meta's answer. While the pixel tracks what happens in the browser, the Conversions API sends events directly from your server or from the platform you run your business on, like your Shopify store. That way purchases, signups and form submissions still reach Meta.

By using the pixel and the Conversions API together, you're covering all your bases. The pixel captures browser information, and the Conversions API fills the gaps with server data, which gives Meta a much clearer picture of what your ads actually achieve.

Advanced matching and Event Match Quality

Advanced matching sends hashed customer details, like an email address or a phone number, along with your events. Hashing encodes the data so the raw details aren't shared, and it helps Meta match the action on your website to the person who saw your ad.

Meta rates how well this works with Event Match Quality, a score from 0 to 10 for each event in Events Manager. The score rises when your events include details like email, phone number and Meta's click and browser IDs, and it's one of the quickest ways to see whether your Conversions API setup is sending enough information.

What Is Meta Events Manager?

Events Manager is the control room for your tracking. Your pixel and your Conversions API events live together in a dataset, and from there you can see every event, how often it fires and whether it comes from the browser, the server or both.

The parts I use most are these:

• Overview, with every event, its volume, its source and its Event Match Quality.
• Test events, which shows events from your own test visit in real time.
• Diagnostics, where Meta flags problems like missing parameters or duplicate events.
• Custom conversions, where you build the rules that tell Meta which results matter most.
• Settings, where you switch on automatic advanced matching and set up the Conversions API.

Meta has also removed the old requirement to rank eight events for iOS measurement and to verify your domain before you can optimize for website events. Verifying your domain in Business Settings is still worth doing, because it confirms you own the site your ads link to.

How to Set Up the Meta Pixel and Conversions API, Step by Step

Step 1: Create your dataset

In Events Manager, connect a new data source and choose Web. Meta creates a dataset with a pixel ID that both your pixel and your Conversions API events will use.

Step 2: Install the pixel

Choose the simplest route your website allows.

1. Partner integration. Shopify, WooCommerce, Wix and many other platforms connect to Meta through an official integration, which installs the pixel and the events for you. For a Shopify store, I explain the setup in my guide to Facebook ads for Shopify.
2. Google Tag Manager. If you already manage tags there, add the pixel base code and your events as tags.
3. Manual code. Paste the base code into the head of every page and add event code where each action happens, which usually needs a developer.

Step 3: Choose the right events for your business

Track the moments that matter for your business model, and pass the details Meta needs with each one.

Make sure each event fires at the right moment. A Lead event belongs on the thank you page or on a successful form submission, never on the page where the form first loads. Otherwise every visitor counts as a lead, and Meta learns to find visitors instead of leads.

Step 4: Set up the Conversions API

Again, take the simplest route available.

1. Partner integration. If your platform offers it, this is the easiest way, and on Shopify it's part of the data sharing setting in the Facebook & Instagram app.
2. Conversions API Gateway. A hosted option you can set up from Events Manager without writing code.
3. Server side Google Tag Manager. A good fit if you already run a server container.
4. Direct integration. Your developer sends events from your server to Meta's API, which gives you the most control.

Step 5: Deduplicate your browser and server events

When the pixel and the Conversions API both send the same purchase, Meta needs to know it's one purchase. Give each event the same event name and the same event ID in both the browser and the server version, and Meta keeps one and discards the duplicate. Most partner integrations handle this for you, but it's the first thing I check in a custom setup.

Step 6: Switch on automatic advanced matching

In your dataset settings, turn on automatic advanced matching so the pixel can send hashed customer details from your forms, and include the same details in your Conversions API events.

Step 7: Test before you spend

Visit your own site with the Meta Pixel Helper open, then check Test events in Events Manager while you complete a test lead or purchase. Only start spending once every key event shows up correctly from both the browser and the server.

How to Use the Meta Pixel Helper

The Meta Pixel Helper is a free Chrome extension from Meta. Open any page on your site, click the extension and it shows which pixel IDs are on the page, which events fired and whether it found any problems.

Use it to check these things on every key page:

• The right pixel ID. Agencies and old setups often leave a second pixel behind, which splits your data.
• The right events on the right pages. ViewContent on product pages, AddToCart when you add something to the cart, and Lead or Purchase only after a successful submission or order.
• No duplicates. The same event firing twice on one action usually means two installations, like a plugin and a manual code snippet.
• Parameters. Click an event to see whether value, currency and product IDs are being passed.

The Pixel Helper only sees browser events. Your Conversions API events never pass through the browser, so check those in Test events and in the Events Manager overview.

How to Check Your Tracking in Events Manager

Here's the routine I follow when I audit an account.

1. Run a test. Open Test events, follow the instructions to send browser and server events from your own visit, and complete a real lead or a test order.
2. Check the sources. In the overview, each key event should show activity from both the browser and the server, with the duplicates removed rather than counted twice.
3. Compare with your own records. Purchases and revenue in Meta should be in the same range as your shop or CRM for the same days, keeping in mind that Meta only counts conversions it can attribute to your ads.
4. Read Diagnostics. Fix anything Meta flags, especially missing parameters and duplicate events.
5. Look at Event Match Quality. If a purchase or lead event scores low, add more customer information to it, like email and phone.

Remember that Meta's default attribution setting is 7 days after a click and 1 day after a view, so its numbers will never match your shop exactly. In my experience, you'll use that default in almost every account when you start.

Custom Conversions: Tell Meta Which Results Matter Most

Custom conversions let you segment your standard events into the specific results you care about, and then optimize for those. You can build them from URL rules, like visits to a specific category page, or from event rules, like purchases above a certain value.

These are the ones I use most:

• High value customers. A custom conversion for orders over $200 tells Meta to find customers who spend more, instead of just customers.
• New customers. Add a parameter to your purchase event that marks first time buyers, and optimize for those when acquisition is your goal.
• Subscriptions. Separate subscription signups from one time purchases, because people willing to commit behave differently.
• Qualified leads. On a landing page, fire a custom conversion only when the answers show the right company size or budget. For Meta's Instant Forms, the equivalent is the conversion leads goal, which I explain in my Facebook lead ads guide.

There's one catch. A custom conversion still needs enough volume for Meta to learn, around 30 to 50 events a week, so start with a broader rule and narrow it as your data grows.

Common Tracking Problems and How to Fix Them

If your tracking looks fine and results still drop, the cause is usually elsewhere, so work through my checklist for Facebook ads not working or the full Facebook ads audit.

A Note on Privacy and Consent

Tracking has to respect the law where your customers live, like GDPR in Europe and CCPA in California. Tell people clearly how you use their data in your privacy policy, ask for consent where it's required, and make sure both the pixel and the Conversions API follow the choice someone makes in your cookie banner. Being transparent also improves data quality, because people who understand what happens with their details are more likely to share accurate ones.

Frequently Asked Questions About the Meta Pixel and Conversions API

Get the Tracking Right First

Every other improvement in your account, from creative to structure to budget, depends on Meta seeing the right results. Spend an hour checking your pixel, your Conversions API and your events before you change anything else, because no amount of good creative can make up for an algorithm that's learning from the wrong signals.

If you'd like a second pair of eyes on your setup, a Breakthrough Session is the quickest way to find out what's broken. If you spend $10,000+ a month on Meta, see how I work as a Facebook ads consultant.