Facebook Pixel checker

Enter your store's address. A real Chrome opens it like a shopper would and reports every Meta Pixel event it sees, whether it fires twice, whether it carries the event id the Conversions API needs, and whether an ad blocker would stop it.

  • Free
  • No sign-up

Free, no account. Six scans per 10 minutes from one connection. We don't store the address or the page.

How it works

1

What it checks for Meta

Pixel ids, every event sent (PageView, ViewContent on a product page, and more), duplicates per page load, the eid that deduplicates against the Conversions API, the _fbp cookie's lifetime on Safari, and where requests go.

2

Server-side setups

A Conversions API call goes server to server and never passes the browser. The checker reports its traces, such as an _fbp cookie set by your own server.

3

Safe by design

A fresh private browser for every check, public addresses only, and nothing stored. It presses only a consent banner's accept button.

My Pixel works in the Meta Pixel Helper. Why does the checker flag it?

The Helper shows that events fire in your browser. The checker also measures what loses them: ad blockers that stop facebook.com, Safari deleting _fbp after 7 days, and missing event ids that make browser and server copies double count.

Two PageViews were found. Is that bad?

Yes, if both are for the same pixel on one page load: Meta counts both. A theme snippet and a plugin often both install the Pixel.

Let Trakero do this for every order

Trakero captures click ids, hashes customer data and sends each purchase once to Meta, TikTok, GA4 and more from your server, so ad blockers and Safari can't lose it.

Start free

Tracking rules change. We'll tell you.

A short email when Meta, Google or TikTok change a tracking rule that affects stores, and when we add a free tool. A few a year. Unsubscribe in one click.

We use your address only for these emails. Privacy policy.