PulsePoint Debugger
by Pulsepoint Inc. more by this developer →
#61,051 of 270,396 by installs on Chrome · #36,122 of 163,941 in productivity
First seen by this census 09/01/2026 — the store does not publish a creation date
Last updated 07/08/2026
Tracked since 09/01/2026
Compare with another extension
Category: productivity / workflow
Languages: English (United States)
Description
Chrome extension for debugging Pulsepoint's Signal pixels.
Alternatives to PulsePoint Debugger
| Name | Users | Rating | |
|---|---|---|---|
Google Analytics Debugger
by Google Analytics
|
600,000 | 4.2 | compare |
Analytics Debugger
|
100,000 | 4.6 | compare |
HttpWatch: HTTP Debugger
by NEUMETRIX LIMITED
|
90,000 | 2.4 | compare |
Adobe Experience Platform Debugger
by Adobe Inc.
|
80,000 | 2.9 | compare |
TagHound - Analytics/GTM/Pixel Debugger
|
50,000 | 4.8 | compare |
Debugger for Google Analytics 4 (GA4)
by James Yoon
|
50,000 | 3.9 | compare |
Debugger for Adobe Analytics
by Tomas Balciunas
|
30,000 | 4.4 | compare |
ObservePoint Debugger
by ObservePoint
|
30,000 | 4.2 | compare |
Pesticide - Advanced CSS Debugger
by Extension Rocks
|
20,000 | 4.9 | compare |
Apex Debugger
|
10,000 | 4.2 | compare |
Growth
Change in installs. This store publishes the count rounded to one or two significant figures, so it does not move when the listing grows - it moves when the rounding rolls over. The figures below are therefore what was actually observed between the two crawls named in "measured over", not scaled to the window, and the percentage is of that same rounding step - so a small listing crossing a bucket shows a very large one. A window needs a full period of history before it reports anything.
| Per | Growth | Growth % | Actual change | Measured over |
|---|---|---|---|---|
| day | Not enough history yet | |||
| week | Not enough history yet | |||
| month | Not enough history yet | |||
| year | Not enough history yet | |||
History
Tracking since 09/01/2026. History accumulates as changes are observed — check back soon.