See which marketing pixels fire and what data they send as you browse.
Users
7
store count
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
total ratings
Store rank
#223K
#186K among extensions
Version
0.1.6
updated 29 Sep 2026
Users
monthly, 1 months
Latest, 16 Oct 2026:7 usersMove the mouse over the chart for any month
Ratings count
monthly, 1 months
Latest, 16 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About Pixel Inspector by PixelMonitor
See what your website sends to advertising and analytics platforms while you browse it.
When you open the side panel, Pixel Inspector automatically records the journey in the current tab and connects each page visit, click, and form submission to the marketing requests observed afterward. Events are organized by vendor and destination ID, so you can quickly find the pixel you care about and inspect its full payload.
Use Pixel Inspector to:
- Identify supported advertising and analytics requests generated during the journey.
- Connect each request to the visitor action that happened before it.
- Inspect vendor-required fields, website-specific custom fields, and other request fields in one readable view.
- Search by action, vendor, event, destination ID, field name, or field value.
- Keep a separate inspection session for each browser tab.
- Export an HTML pixel report or structured JSON file.
Inspection starts automatically when the panel opens or you switch to a website tab while it is open. It records page addresses, clicked-element labels, form submissions, and recognized marketing request payloads, which may include personal identifiers and purchase details. Recording continues in that tab across navigation and after closing the panel until you Pause, close the tab, or reach the session limit. Clear removes the results and immediately starts a fresh recording. Use Pause to stop capture. Data stays in Chrome session storage for the inspected tab and is not uploaded to PixelMonitor. Pixel Inspector observes browser requests only; it cannot verify server-side events, platform attribution, or final receipt by a vendor.