Facebook Pixel Not Working in Google Tag Manager: What to Check

Last checked 6 October 2026 against Meta's documentation. By Muhammed Abdul Kalam. Data loss

Quick fix

Facebook pixel not working in google tag manager usually means the base code tag, a trigger or the publish step is wrong. Check the base code is a Custom HTML tag set to once per page on the All Pages trigger, each event tag has a trigger, then test in Preview mode.

Check the base code tag is Custom HTML, firing once per page on All Pages.
Check each event tag has a trigger with the right condition.
Test in Preview mode and with Meta Ads Data Advisor.
Submit the container so the changes are published.

Can't fix it yourself? Send me the details

What this error means

With Tag Manager the Meta pixel isn't in your site code, so each part is a tag with a trigger. If the base tag doesn't fire on all pages, an event tag has no matching trigger, or the container isn't published, Meta receives nothing.

Why it happens

1Base code tag set up wrongly

The base code is a Custom HTML tag, with the full code copied from Events Manager.

How to tell if this is you: Preview shows the base tag as not fired.

2Wrong or missing trigger

The base code uses All Pages, and event tags need conditions matching the page or action.

How to tell if this is you: An event tag does not fire on the right page.

3Container not published

Changes only go live when you submit the container.

How to tell if this is you: Preview works but the live site does not.

4The pixel is installed twice

Adding the pixel ID in another platform as well can send duplicates.

How to tell if this is you: Events arrive twice.

5Blocked in the browser

Browser settings or privacy tools can stop the pixel in a tag manager.

How to tell if this is you: It works in a clean browser.

How to fix it

Rebuild the base tag

For: Base code tag set up wrongly

Create a Custom HTML tag with the entire base code.
Set it to fire once per page on All Pages.

Fix event triggers

For: Wrong or missing trigger

Give each event tag a trigger with the right condition.
Include variables such as value and currency.

Test and publish

For: Container not published, Blocked in the browser

Use Preview mode to check tags and triggers.
Verify with Meta Ads Data Advisor, then check the pixel is Active in Events Manager.
Submit the container to publish.

Remove duplicates

For: The pixel is installed twice

Remove the pixel ID from other platforms if Tag Manager already sends the events.

How long it takes

Meta doesn't publish a timeline for this.

How to stop it happening again

Always use Preview mode before you publish.
Keep admin access with someone who can publish.
Install the pixel in one place only.

From my desk

The mistake I see most is publishing nothing. The tag works in Preview, the container never gets submitted, and the client thinks tracking is live. Close behind is a missing trigger on the event tags, or a base code tag that doesn't fire on all pages. I always check the container version on the live site.

Muhammed Abdul Kalam

When to get help

You've worked through the checks and the numbers or status still aren't right.
The setup involves a tag manager, Shopify app or developer you cannot reach and nobody can explain it.
Results are suffering during a launch or sale and every day costs real money.

Stuck on this? Send me the details.Tell me what the platform shows and what you've tried so far.

Send me the details

FAQs

What type of tag holds the Meta pixel base code?

A Custom HTML tag.

Which trigger should the base code use?

All Pages, set to fire once per page.

Why does my event tag never fire?

Each tag needs a trigger that decides when it fires, with a condition that matches the page or action.

How do I test before going live?

Use Preview mode, and Meta Ads Data Advisor to verify events reach Meta.

Why do my changes not show on the site?

You need to submit the container to publish the changes.