---
title: "Free Meta Pixel checker (Facebook Pixel)"
description: "Test whether your Meta (Facebook), TikTok and OpenAI pixels really work: consent, duplicates, event IDs, click IDs, server-side signals. Free, no sign-up."
url: "https://ispixelworking.com"
---

# Is your Meta Pixel actually working?

**Ads optimize on what your pixels report.** We open your page from the EU like a real visitor, accept cookies, tap the main buttons, and show what your page sends to Meta, TikTok and OpenAI, when it sends it, and how to fix what's wrong.

**Check a page:** paste the page your ads point to into the form on https://ispixelworking.com/, or open https://ispixelworking.com/check?url=<page address> in a browser. The check starts once Cloudflare Turnstile confirms a person is there, and the report opens in about a minute. Free, no sign-up; our browser never sends tracking data to Meta or Google.

## How it works

1. **Paste a page.** Usually the landing page your ads point to.
2. **We visit it twice.** Before consent, then arriving from an ad: cookies accepted, main buttons clicked.
3. **Fix what's broken.** Each problem links to a step-by-step guide, or we can fix it for you.

## What the free check looks at

### Cookie consent

Does the pixel wait for consent, and does it start once cookies are accepted? We operate the banner the way a visitor does.

- Meta Pixel fires before cookie consent
- Meta Pixel does not fire after consent
- Cookie banner could not be operated automatically
- 28 consent tools recognized

### Pixel health

Duplicates inflate results and confuse optimization. Missing event IDs break deduplication with server events.

- Meta blocks this pixel on this website
- Duplicate Meta events
- Meta events have no event ID
- More than one Meta Pixel
- Event names on every button

### Ad click attribution

We arrive with test ad click IDs and check that your site keeps them, so Meta, TikTok and OpenAI can credit the ad.

- Click ID from Meta ads is not stored
- Click ID lost in redirects
- Click ID saved by your site code in a non-standard format
- Two different browser IDs (_fbp)

### Server-side signals

We look for signs of Conversions API and server-side Tag Manager. We report what we see, never whether it works.

- CAPI tools
- First-party Tag Manager
- Tracking relays on your domain
- Site-generated event IDs

## Monitoring (opens soon, from $19 a month, [pricing](https://ispixelworking.com/pricing))

### Mobile

Most ad traffic is mobile. Phone layouts often have different buttons and a different cookie banner.

- Mobile buttons are tracked differently from desktop
- Mobile cookie banner
- Mobile buttons
- Click ID on mobile

### Alerts when tracking breaks

Your pages are re-checked on a schedule. A site update that breaks the pixel reaches you by email, not through a bad week of ads.

- Daily re-checks
- Alert on new problems
- Email when it's fixed
- Weekly digest

### Uptime

A landing page that is down wastes every click you pay for. We check that it answers, and how fast.

- Down and recovered alerts
- Response time
- SSL certificate expiry

### Page speed

Slow landing pages lose visitors before the pixel even loads: you pay for clicks that never become page views.

- Core Web Vitals from real users
- Daily mobile speed test
- Speed trend per page

### Form tests (coming soon)

We submit a test lead on your form and check that the conversion event fires. Needs a one-line tag on your site.

- Lead event after submit
- Thank-you page tracking

## Questions

### How do I check if my Meta Pixel is working?

Paste the page your ads point to into the form above. A real browser in the EU opens it twice: once without touching the cookie banner, once arriving from a Meta ad, accepting cookies and clicking the main buttons. The report shows every standard event and custom event your page sends to Meta, when it sends it, and what is wrong, so you can troubleshoot the setup. Meta's own tools, the Meta Ads Data Advisor Chrome extension (formerly Meta Pixel Helper) and the Test events tool, show what fires in your browser; this check adds the consent and ad-click side. TikTok and OpenAI pixels on the page are checked the same way, each with its own grade. Step by step: [how to check if your Meta Pixel is working](https://ispixelworking.com/blog/check-meta-pixel-working).

### How can I check whether a website has a Meta Pixel installed?

Paste its address above: the report says whether a Meta Pixel loaded, which pixel IDs it uses and which events it sent. To look yourself, open the page with your browser's developer tools on the Network tab and filter for `facebook.com/tr`: every request there is a pixel event, and its `id` value is the pixel ID.

### Where do I find my Meta Pixel ID?

In Meta Events Manager, under Data sources, select your pixel (Meta now also calls it a dataset); the ID is shown with its name. On your site, the same number appears in the pixel code (`fbq('init', '...')`) and as the `id` value in requests to `facebook.com/tr`.

### Is the Meta Pixel the same as the Facebook Pixel?

Yes. Facebook renamed it the Meta Pixel in 2022. It is the same code (fbevents.js), the same events and the same Events Manager, so everything here applies if your setup still calls it the Facebook Pixel.

### Why does my pixel fire before cookie consent?

Usually the pixel is pasted straight into the site's head or theme, or a Google Tag Manager tag fires on all pages without waiting for consent. Some built-in cookie banners only hide themselves and do not hold the pixel back. See [how to wire the pixel to your consent setup](https://ispixelworking.com/guides/meta.fires_before_consent/generic).

### Why does my Meta Pixel send nothing after visitors accept cookies?

The consent tool may never release the pixel, consent mode may stay revoked, or the tag trigger waits for an event that never happens. Ad delivery then optimizes on almost no data. See [the fix guide](https://ispixelworking.com/guides/meta.not_firing_after_consent/generic).

### What are fbclid and the _fbc cookie, and why do they matter?

When someone clicks a Meta ad, the link gets an fbclid parameter. The pixel saves it in the _fbc cookie and sends it with later events, which is how Meta matches a conversion to the ad click. Redirects that drop URL parameters or blocked cookies lose it. See [how to keep the click ID](https://ispixelworking.com/guides/meta.fbc_not_set/generic).

### What causes duplicate Meta Pixel events?

Two copies of the pixel (for example a theme setting plus a plugin, or a hard-coded snippet plus Tag Manager) or two pixel IDs on one page. Duplicates inflate conversions and confuse optimization. See [how to find and remove the extra copy](https://ispixelworking.com/guides/meta.duplicate_pixel/generic).

### Do I need event IDs if I use the Conversions API?

Yes. When the same event comes from the browser and from your server, Meta uses the event ID to count it once. Without it, events are double counted or dropped. See [how to add event IDs](https://ispixelworking.com/guides/meta.missing_event_id/generic).

### Can ad blockers stop my Meta Pixel?

Yes. Ad blockers and some browser privacy features block requests to Meta, so a share of real visitors never reach Events Manager whatever your setup. Our check runs in a normal browser without a blocker, so it shows whether the pixel works when nothing gets in its way. The Conversions API, which sends events from your server, recovers part of what blockers stop.

### Does it work with Shopify, WordPress, Webflow and Framer?

Yes. The check looks at the page the way a visitor's browser does, so it works for any site: Shopify, WordPress and WooCommerce, Webflow, Framer, Wix or custom code, with or without Google Tag Manager. The report names the platform it detected and links the matching fix guide where we have one.

### Does the check send data to my ad account?

No. We stop every request to Meta, TikTok, OpenAI, Google and other ad platforms before it leaves our browser, so your ad accounts receive no test data. We never fill in or submit forms and never click buy or checkout buttons. [How the check works](https://ispixelworking.com/methodology).

### Is it free?

Yes. The check is free and needs no sign-up. Monitoring, which re-runs the check on your landing pages every day and emails you when tracking breaks, opens soon and will cost from $19 a month: see [pricing](https://ispixelworking.com/pricing).

## More

- [How the check works](https://ispixelworking.com/methodology): the visits, scoring, and what a browser can't see
- [Fix guides](https://ispixelworking.com/guides): step-by-step fixes for each problem
- [Pricing](https://ispixelworking.com/pricing): the free check and the monitoring plans
- [Blog](https://ispixelworking.com/blog): research and practical notes on Meta Pixel, consent and ad tracking
- [Our checker, for site owners](https://ispixelworking.com/bot): what our browser does on your site and how to opt out
- [For AI agents](https://ispixelworking.com/ai-agents): connect Claude, ChatGPT or Cursor to our MCP server
- [About](https://ispixelworking.com/about) · [Contact](https://ispixelworking.com/contact) · [Privacy](https://ispixelworking.com/privacy) · [Terms](https://ispixelworking.com/terms)
