How Can I Check If My Meta Pixel Is Working?

A Meta Pixel is working when Meta Events Manager receives PageView and the conversion event you tested, while Meta Pixel Helper detects the expected Pixel ID without a critical error.

Use both tools:

PageView appears in Events Manager after you visit your website.
The expected conversion event appears after you complete an action, such as Lead, AddToCart, InitiateCheckout or Purchase.
Meta Pixel Helper detects the right Pixel ID and shows no critical errors.

Pixel Helper confirms that your browser is sending events. Events Manager confirms that Meta is receiving them.

1. Check Your Meta Pixel in Events Manager

Open Meta Events Manager.
Select the relevant data source. Meta may call this a Pixel or Dataset.
Open Test Events.
Enter your website URL, or open your website in a separate browser tab.
Visit a page where the Pixel is installed.
Look for a real-time PageView event.
Complete the action you want to track, such as submitting a form or completing a test checkout.

Meta's Test Events tool displays incoming browser and server events while you test your setup.

Events You Should See

Test action	Expected event
Load a page	`PageView`
View a product	`ViewContent`
Add a product to the cart	`AddToCart`
Start checkout	`InitiateCheckout`
Submit a lead form	`Lead`
Complete an order	`Purchase`

Check the event name and its parameters. For ecommerce events, those parameters may include product IDs, value and currency.

A PageView event alone does not prove that the full conversion setup works. Test the customer journey and confirm that the event tied to the business goal appears.

2. Use Meta Pixel Helper in Chrome

Install the Meta Pixel Helper Chrome extension and visit your website. The extension reports detected Pixel events, warnings, errors and implementation details.

Check the following:

The Pixel ID matches the data source selected in Events Manager.
PageView fires when the page loads.
The expected conversion event appears after you complete the test action.
The extension does not show a warning or error that affects the event.
The same event does not fire more than once.

If Pixel Helper shows "No pixels found," the Pixel is not loading in that browser session or is not installed on that page.

3. Confirm That the Conversion Event Fires

A base Pixel can send PageView while a conversion event remains missing or misconfigured.

Common examples:

PageView fires but Lead does not: the form submission trigger may be missing.
AddToCart fires but Purchase does not: the purchase event may be missing from the order confirmation page.
Purchase fires twice: the event may be installed through both a plugin and Google Tag Manager.
The event appears with the wrong value: the value or currency parameter may be configured incorrectly.

For an ecommerce site, test the full path from product page to cart, checkout and test order. Then compare each expected event in Test Events.

4. Compare the Pixel IDs

A Pixel can send events to the wrong Meta data source and still appear to work.

Compare the Pixel ID in:

Meta Events Manager
Your website code
Google Tag Manager
Your ecommerce platform or marketing plugin
Meta Pixel Helper

The IDs must match exactly. If Pixel Helper detects a different ID, your website is sending events to another Pixel.

5. Check the Browser Request

Chrome Developer Tools can show whether the browser sends a request to Meta.

Right-click your website and select Inspect.
Open the Network tab.
Reload the page.
Search for facebook, fbevents or tr.
Find a request containing your Pixel ID.
Complete the conversion and check whether another request is sent.

This check helps when Google Tag Manager reports that a tag fired but Pixel Helper does not show the event.

6. Check Browser and Server Events Separately

If you use both the Meta Pixel and Meta Conversions API, Events Manager can show:

Browser events sent by the Pixel
Server events sent by the Conversions API
Browser and server events for the same conversion

A browser event shows that the Pixel fired. A server event shows that the Conversions API sent data. When both systems send the same conversion, they need matching event IDs so Meta can deduplicate the events rather than count one conversion twice. Meta's testing documentation covers browser and server event validation separately.

What Different Results Mean

Result	Likely meaning
Pixel Helper detects nothing	The Pixel is missing, blocked or installed on the wrong page
`PageView` appears but no conversion event	The conversion trigger is missing or misconfigured
Events appear in Pixel Helper but not Test Events	The wrong Pixel or Dataset may be selected, consent may be blocking the event, browser restrictions may apply or Meta may not have processed it yet
Events appear twice	The Pixel may be installed more than once, or browser and server events may lack deduplication
The event appears but its parameters are wrong	The event configuration or dynamic values need review
Events appear in Test Events but not Ads Manager	Ads reporting may take longer, so it is not the best place for immediate implementation testing

The Quickest Reliable Test

Open Events Manager → Test Events.
Open your website in another tab.
Open Meta Pixel Helper.
Confirm the Pixel ID.
Check for PageView.
Complete one test conversion and confirm that the expected event appears once with the right parameters.

If PageView and your main conversion event appear in both tools, the Pixel and that conversion path are working. If only PageView appears, the base Pixel works but the conversion tracking still needs attention.