Ask ten advertisers why their Meta ads stopped improving and several will describe the same hidden cause: the website was never told what a good visitor looks like. The Meta Pixel is how it is told. Without it, an ad account is guessing. With it set up properly, Meta can find more people like the ones who bought, show ads to those who looked and stopped, and report what happened after the click.
This guide explains what the pixel is, how it works, which events matter, how to install and test it, how it fits with the Conversions API, and what to keep out of it. Facts come from Meta's own help center and developer documentation, and sources are listed at the end. For the wider picture of running ads, see our guide to Meta ads.
What is the Meta Pixel
Meta describes the Meta Pixel as a piece of code that you put on your website. It lets you measure the effectiveness of your Meta advertising by understanding the actions people take on your site. Meta lists three main uses:
- Show ads to the right people. Find new customers, or people who visited a particular page or took an action on your site.
- Drive more sales. Set up automatic bidding in Ads Manager to reach people more likely to take an action you care about, such as a purchase.
- Measure results. Understand what happens after people see or click your ads.
It is the same tool people used to call the Facebook Pixel. Searches for "meta pixel", "meta pixel helper" and "what is meta pixel" together run into the thousands each month in the US, and most come from advertisers who have been told to install it and want to know what that actually involves.
How the Meta Pixel works
Once installed, the pixel logs an event whenever someone takes an action on your site. An event might be a page view, adding an item to a cart or completing a purchase. Those events appear in Events Manager, where you can see what customers did. In Ads Manager you can then build custom audiences from the events or use them for retargeting.
Meta Pixel standard events
Standard events are predefined actions Meta recognises, so ads can be optimized for them and reports can compare them. Meta's specification lists these 17, each fired with a line such as fbq('track', 'Lead');:
| Event | Use it when | Typical business |
|---|---|---|
| ViewContent | Someone views a product or key page | Ecommerce, services |
| Search | Someone uses site search | Ecommerce, directories |
| AddToCart | An item is added to the cart | Ecommerce |
| AddToWishlist | An item is saved | Ecommerce |
| InitiateCheckout | Checkout starts | Ecommerce |
| AddPaymentInfo | Payment details are added at checkout | Ecommerce |
| Purchase | An order completes (send value and currency) | Ecommerce, bookings |
| Lead | Someone submits a form or enquiry | Lead generation |
| Contact | Someone contacts you by phone, SMS, email or chat | Local and service businesses |
| Schedule | An appointment is booked | Clinics, consultants, trades |
| SubmitApplication | An application is submitted | Education, finance, jobs |
| CompleteRegistration | A registration finishes | Software, events |
| StartTrial | A free trial begins (value, currency and predicted lifetime value can be sent) | Software |
| Subscribe | A paid subscription starts | Software, media |
| FindLocation | Someone looks for a location | Multi site businesses |
| CustomizeProduct | A product is configured | Made to order retail |
| Donate | A donation is made | Non profits |
You do not need all of them. Choose the one or two that mark real business results, then add earlier steps so the system has more signal. For a plumber, that might be Contact and Lead. For a shop, ViewContent, AddToCart, InitiateCheckout and Purchase. Where an event has a value, such as Purchase, send the value and currency so Meta can optimize for revenue and report return on ad spend.
Meta Pixel vs Conversions API
The pixel runs in the visitor's browser, which means it can be blocked by browser settings, ad blockers, consent choices or a page that closes before the event fires. The Conversions API sends events from your server or tag server directly to Meta, so it does not depend on the browser. Meta recommends using both for important events. When both report the same action, you need deduplication so it is not counted twice. Meta's rule is that the event_id must be identical on both events, and each event instance needs its own unique ID. In the pixel, Meta's developer reference says to pass it as a fourth parameter, for example fbq('track', 'Purchase', {value: 49, currency: 'USD'}, {eventID: 'order-1042'}), and to send the same ID from the server.
| Meta Pixel | Conversions API | |
|---|---|---|
| Where it runs | Visitor's browser | Your server or a tag server |
| Strength | Easy to install, rich browser context | Not blocked by the browser, reliable for purchases and leads |
| Weakness | Can be blocked or lost | Needs development or a partner integration |
| Best use | All events, quick start | High value events such as Purchase and Lead |
| Together | Send the same event from both with a matching event ID so duplicates are removed | |
Our Meta Pixel and Conversions API service sets up both with deduplication and checks event quality.
How much data does the browser pixel miss
Nobody can give you a universal figure, because it depends on your audience, consent banner, devices and site. You can, however, test your own account by comparing Meta's conversions with your own order or lead records. The calculator shows how a gap between the two changes cost per result. The percentages are placeholders. Replace them with your own comparison.
Tracking gap calculator
With the example inputs, $3,000 buys 100 real conversions at $30 each. The browser pixel alone reports 70, so Meta sees a cost of $42.86 and has 30 conversions it never learns from. Adding the Conversions API lifts that to 90. The goal is not a perfect match, which is not realistic, but a smaller gap and consistent reporting.
How to set up the Meta Pixel step by step
Menus and names change, so use Meta's current help pages alongside these steps. Meta's pages on setting up and installing the pixel and on best practices for setup are listed in the sources.
- Decide what to measure. Write down the one or two actions that count as success, plus the steps leading to them.
- Create the pixel. In Events Manager, connect a new data source for your website. Meta may call it a pixel or a dataset linked to a pixel, and it belongs to your business portfolio.
- Choose an install method. Meta offers partner integrations (many website platforms and shop builders have one), manual installation of the base code in your site header, and tag managers such as Google Tag Manager. Use only one method so events do not fire twice.
- Add the events. Use the event setup tool, a partner integration or code to fire the standard events at the right moments. Send value and currency where relevant.
- Consider advanced matching. It lets the pixel send hashed customer information such as email when a person provides it, which can improve matching of events to people. Follow privacy law and consent rules.
- Add the Conversions API for your key events, with a shared event ID.
- Test everything (next section) before spending on ads.
- Connect it to ad accounts. Give the right ad accounts and partners access to the dataset, using Meta's sharing controls.
Some platforms have a built in way to add the pixel. Searches for how to add the Meta Pixel to Shopify, WordPress, Squarespace, Wix, GoDaddy or Google Tag Manager follow the same principle: use the official integration where one exists, paste your pixel ID, then test each event. If you handle it through Google Tag Manager, our tracking and analytics service can build and test the setup.
How to find your Meta Pixel ID
The pixel ID is a numeric identifier. To find it, open Events Manager in your Meta business account, choose the data source for your website and read the ID shown beside its name. If you have access to the website, the Meta Pixel Helper extension in Chrome also shows the pixel ID it detects on the page, which is handy for checking that the right pixel is installed. If you manage several clients, label each dataset clearly so you do not paste an ID into the wrong site.
How to check that the Meta Pixel is working
Do not trust that an install worked. Test with these tools:
- Meta Pixel Helper. A Chrome extension that shows which pixels fired on a page, which events, and any errors or warnings. It is the quickest check on your own site.
- Test Events tool. In Events Manager, open it, enter your site address and see events arrive in real time as you click through. It shows browser and server events side by side and whether they deduplicate.
- Diagnostics. Events Manager flags errors, warnings and drops in events so you can fix them before they hurt delivery.
Check each event once: it should fire once, at the right moment, with the correct value and currency. Then place a test order or send a test enquiry and confirm it matches what your own system recorded.
Common Meta Pixel problems and fixes
| Problem | Cause | Fix |
|---|---|---|
| Events fire twice | Pixel installed through both a theme or plugin and a tag manager | Keep one method and remove the other |
| Purchases counted twice | Pixel and Conversions API without a shared event ID | Send the same unique event_id from both |
| No events show | Wrong pixel ID, blocked script, consent banner blocking it | Check the ID, test in a clean browser, review consent set up |
| Purchase has no value | Value and currency not passed | Send both parameters on the event |
| Events fire on the wrong page | Trigger set on a page view not the action | Trigger on the thank you page or the form success event |
| Fewer events than your own records | Browser blocking, consent choices, page closing early | Add the Conversions API, check consent, use the test tools |
Using the Meta Pixel responsibly
Meta's help center is explicit on two points. First, do not share prohibited information. It says this includes health, financial and children's data, and anything else that its terms, policies or applicable law do not allow. It advises regular reviews of your pixel setup, event names, parameters, URLs and any optional features you turn on, and consulting legal counsel if unsure. Page addresses and form field names can reveal sensitive details even when you did not intend to send them, so check what is included in each event. Second, do not place your pixel on websites you do not own without permission.
If you operate in healthcare, finance, education for minors or another sensitive field, get legal advice before installing any tracking, and combine it with a consent management setup that respects local rules. Cookie settings for the pixel are covered in Meta's help center.
Events to track by type of business
| Business type | Key event | Supporting events |
|---|---|---|
| Ecommerce | Purchase (with value) | ViewContent, AddToCart, InitiateCheckout |
| Local services | Lead or Contact | ViewContent, Schedule |
| Professional services | Lead or Schedule | ViewContent, Contact |
| Software | StartTrial or Subscribe | CompleteRegistration, ViewContent |
| Education | SubmitApplication | Lead, ViewContent |
For lead generation, the 2026 LocaliQ Facebook benchmarks give a sense of scale: lead campaigns averaged a click through rate of 2.70%, a cost per click of $1.80, a conversion rate of 8.54% and a cost per lead of $27.39. The pixel is what lets you see your own numbers against those. If you generate leads directly on the platform, see our guide to lead ads, and for retargeting people who visited without acting, our retargeting service.
Can you delete, share or transfer a Meta Pixel
People often search for how to delete or share a pixel. Before deleting anything, check whether active ads, audiences or reports depend on it, because removing the data source cuts off the history. If you only want to stop tracking, you can remove the pixel code from your site. To give an agency or another ad account access, use the sharing controls for datasets and pixels in your business portfolio rather than copying the code. Meta's help center has a page on sharing controls and another on pixel history, which records who changed what. Keep ownership of the dataset in your own business portfolio so you retain the data if you change agencies.
A simple Meta Pixel launch checklist
- Pick one or two business events and write them down.
- Create the pixel in your own business portfolio.
- Install with one method only.
- Add events with value and currency where relevant.
- Add the Conversions API for key events with a shared event ID.
- Test with Pixel Helper and the Test Events tool, then with a real test order or lead.
- Check consent set up and what data each event sends.
- Share the dataset with the right ad accounts and partners.
- Compare Meta's numbers with your own records every month.
If you would like this done and checked for you, our Meta Pixel and Conversions API setup includes testing and a clear event plan, and a Meta ads audit will show whether your current tracking is losing results.
Sources
- Meta Business Help Center: About Meta Pixel. www.facebook.com
- Meta Business Help Center: Specifications for Meta Pixel standard events. www.facebook.com
- Meta Business Help Center: About deduplication for Meta Pixel and Conversions API events. www.facebook.com
- Meta Business Help Center: Set up and install the Meta Pixel. www.facebook.com
- Meta Business Help Center: Best practices for Meta Pixel setup. www.facebook.com
- Meta for Developers: Meta Pixel API reference. developers.facebook.com
- Meta Business Help Center: About prohibited information. www.facebook.com
- LocaliQ: Facebook Advertising Benchmarks (2026). localiq.com