A focused Chrome extension for marketers, advertisers, and developers. Detects Meta Pixel scripts on any website, surfaces pixel IDs and event data in one click, and quietly warns you when a previously working pixel goes stale.
Built around one question: is the pixel actually firing the way it's supposed to? Each feature is here because a real marketer or developer asked for it. Each is configurable from the Options page.
connect.facebook.net, plus tracking requests to the Meta endpoint. Detects multiple pixels on a single page.No accounts to create. No keys to paste. No SDK to integrate. Install, browse, click — done.
We believe extensions should justify their permissions in plain language, not hide them behind boilerplate. Here is the full list and the exact feature each one powers.
| Permission | What it powers |
|---|---|
| host_permissions: <all_urls> | Meta Pixels can be installed on any website. The content script must run on every page to detect them. No remote requests are made by the extension. |
| storage | Saves your settings and the local history of detected pixels. All data stays on your device. |
| alarms | Schedules the once-per-day background staleness check. Runs at most once every 24 hours. |
| tabs | Identifies the active tab so the popup can show pixels for the page you're currently viewing. |
| notifications | One-time install confirmation, plus the optional 7-day stale-pixel warning. Never fires on page visits. |
No. The extension reads Meta Pixel script tags and tracking-request entries directly from pages you visit, processes them locally inside your browser, and stores results in chrome.storage.local — which never leaves your device. There is no server, no analytics, no third-party SDK. You can verify this by inspecting the source code, which is unminified during review and ships open for audit.
Because Meta Pixels can be deployed on any website on the internet — e-commerce stores, news sites, advertiser landing pages, SaaS marketing pages, and so on. The extension cannot know in advance which sites have a pixel installed, so the detector must run on every page you visit. The detector only reads <script> tag URLs and Performance entries; it does not read page content.
No. Pixel Helper is an independent third-party tool, not affiliated with, endorsed by, or connected to Meta Platforms, Inc. or Facebook. "Meta Pixel" and "Facebook" are referenced descriptively as the third-party tracking technology this extension detects.
Pixel Helper is built around persistence and respect for privacy. It tracks which pixels have appeared across sites you've visited and warns you proactively if one stops firing — useful when you're managing pixel deployments across many advertiser sites, agency clients, or your own catalog of landing pages. It also collects zero data and runs entirely offline.
Yes — open the Options page (right-click the toolbar icon → Options) and toggle "Stale pixel warnings" off. You can also disable pixel tracking entirely from the same page. Toggle states are stored locally and respected immediately.
No. The content script is a lightweight detector that runs at document_end and finishes in milliseconds. The service worker stays idle except for the once-per-day alarm and the brief moment a pixel is recorded. There is no continuous polling, no periodic network activity, no heavy DOM observation.
Yes. The extension is free for personal and commercial use. There are no usage limits, no telemetry, and no licensing tier. Use it across as many sites and clients as you like.
Free. No account. No data collection. Add it to Chrome and never wonder if your pixel is firing again.
Add to Chrome — free ↗