Facebook Pixel not firing on your ad landing page How to check in 2 minutes.

The 2-minute Facebook Pixel check

You do not need a developer. You need the address your ad sends people to and two minutes.

The no-install way: run the free ClickMend Meta ad page check. Paste the address from your Facebook or Instagram ad. It looks for the Meta Pixel, a real pixel ID, a PageView event, a Lead event, and whether the fbclid click ID makes it through your redirects.

The by-hand way uses Meta's own tools:

• Add Meta's free extension. It is called Meta Ads Data Advisor. It used to be called Meta Pixel Helper. Meta offers it for Google Chrome and Microsoft Edge.
• Turn off your ad blocker for your own site. Meta lists this as a must. An ad blocker hides the pixel from the extension.
• Open the page the ad opens. Use the exact address from the ad, not your home page. Meta says a badge on the extension icon shows the number of pixel events fired on the page. No badge means no Meta Pixel is installed on that page.
• Look for PageView. Meta's base code tracks one PageView each time the page loads. If you see it, the pixel fires on this page.
• Send a test form. Fill it in like a real lead. Watch for a Lead event on the next step.

If there is no pixel at all, it was never installed on this page. Follow Meta's Pixel setup guide or the Business Help Center setup steps.

Test the pixel with Test Events in Events Manager

The extension is the quick look. Meta's own page for it says that for in-depth troubleshooting you should use the test events tool in Events Manager. Meta also warns that the extension may not detect button-click events, depending on how your site is built.

To find the tool, Meta gives this path: Events Manager, then Data Sources, then your pixel, then Test Events. Follow the steps there to open your landing page. Then load it, fill in the form, and send it. Your events should show up in the Test Events window.

Facebook Pixel test events not working?

If nothing shows up, check these before you blame the pixel:

• Ad blocker or privacy tool. If your browser blocks the pixel, no event leaves your computer.
• Wrong pixel. Test Events belongs to one pixel. If the page carries a different pixel ID, your events land somewhere else.
• Cookie banner. If your page waits for consent, click Accept first.
• No base code on that page. Meta says the base code must be on every page where you want to track conversions.

The Facebook Pixel Lead event and the thank-you page

Lead is one of Meta's standard events. Meta's reference describes it as "when a sign up is completed."

Meta says you can fire a standard event when a page loads, or when a visitor does something, such as clicking a button. The simple setup is to fire Lead when the thank-you page loads. That page only shows after the form is sent.

This is why a check of the landing page alone often shows PageView and no Lead. That can be fine. The Lead event lives one page later. Send a test form and check three things:

• The thank-you page has the pixel base code. A thank-you page on another builder or domain often does not.
• Lead fires once. Not zero times, and not twice.
• Pop-up forms still fire it. If the form shows a "thanks" message with no new page, Lead has to fire when the form is sent.

Meta's custom conversions can also count visits to any page with a set piece of text in its address, such as /thank-you. The pixel base code still has to be on that page.

Four things that hold the Meta Pixel back

1. A cookie or consent banner

Meta's pixel has a consent setting. When a site calls it with "revoke," the pixel pauses. It sends nothing until consent is granted. Many cookie banner tools work this way, or they keep the pixel from loading until someone clicks Accept. Test your page twice: once before you accept, once after. If the pixel only fires after Accept, visitors who ignore the banner are not counted.

2. Redirects that strip the fbclid click ID

When someone clicks a Facebook or Instagram ad, Meta adds a click ID called fbclid to your page address. Meta says the pixel stores it in a cookie once it is there. If a redirect drops everything after the question mark, the click ID is gone before the pixel can read it. Meta's support FAQ also notes that link shorteners and vanity URLs can cause trouble when the click ID is added.

Quick test: add ?fbclid=test123 to the end of your ad's address and load it. If the address bar no longer shows it when the page settles, a redirect is stripping it. Point the ad straight at the final page.

3. The pixel is inside Google Tag Manager

Meta says the pixel works in most tag managers, though it still recommends putting the base code right in the page head. Inside Tag Manager, the pixel only fires when its trigger fires, and only after the container is published. Google's preview mode shows which tags fired and which did not. Also check for a second copy of the pixel in the page code. Meta says not to duplicate pixel code on one page.

4. A placeholder or wrong pixel ID

Meta's sample base code has a stand-in where your ID goes, in two places. A copied template can ship with that sample still in, so nothing reaches your pixel. The other version is a real ID that is not yours, such as one left by an old agency. The pixel fires, but the events go to a pixel your ad account does not use. Compare the ID on the page with the one in your Events Manager.

What the ClickMend Meta check can and cannot see

ClickMend scans the page a Google or Meta ad sends people to. For a Meta ad page, the free Meta check looks at:

• Is the Meta Pixel base code on the page, or did it load during our phone test?
• Is the pixel ID real, or a sample that was never replaced?
• Is PageView set up?
• Is a Lead event, or another lead or sale event such as Contact, Schedule or Purchase, on this page?
• Does a test fbclid survive your redirects?

It cannot see server-side Conversions API events. It cannot read your ad account. It cannot see a Lead event that fires only on a later thank-you page. It does not click Accept on a cookie banner. So "no Lead event seen" from ClickMend means check the thank-you page, not that tracking is broken.

The score is ClickMend's own. Meta does not publish a landing page score.

Next, read the Facebook ads landing page guide. For speed, see does the Facebook Pixel slow a landing page and what third-party scripts cost. Running Google Ads to the same page? The free Google Ads page scan checks your Google Ads tag.

Related guides

Frequently asked questions