Troubleshooting

How Pulse decides install health

The install status you see in Pulse is derived on the server from events actually received — never from looking at your HTML:

• Waiting for the first event — Pulse has never received an event for this site. The script may be missing, blocked, or installed somewhere that hasn't been visited yet.
• Active — events are arriving. The panel shows when the last one landed.
• No recent data — events used to arrive, but none for 14 days. Something changed: a redeploy dropped the script, a policy or blocker now stops it, or the site genuinely had no visitors.

The verify panel (Settings → Site → General) polls this status live while you're looking at it, so a successful install confirms within seconds of a page load.

Installed, but nothing arrives

Work down this list — it's ordered by how often each one is the cause:

1. Load your site yourself, in a normal tab. The first event has to come from somewhere. Open your site, then watch the verify panel — it confirms within seconds.
2. The browser you tested with blocks it. Ad blockers, tracking protection, and some private-browsing modes stop analytics scripts — including privacy-friendly ones. Test in a browser profile without extensions before concluding the install is broken.
3. A Content Security Policy blocks the script or its events. Your browser console will say so explicitly (Refused to load … script-src / Refused to connect … connect-src). The fix is two directives — see Content Security Policy.
4. The script runs on a different domain than the site is registered for. A www vs apex mismatch, a staging environment carrying the production snippet, or the snippet pasted into a different project are all common. Check the domain on the site card against the address bar of the page you're testing.
5. Your framework only ran it once. In single-page apps, client-side navigations don't reload the document, so an incorrectly placed snippet counts only the first page. The framework guides carry the correct placement for Next.js, Nuxt, SvelteKit and friends.

The dashboard is empty but the install shows Active

Active means events are arriving now. An empty chart for a date range means no events in that range — check the range picker before the install. Bot traffic is also filtered before it reaches your charts (see Bot filtering), so a page opened only by crawlers can be quieter than you expect.

Still stuck?

Write to us via the contact page with your site's domain and what the verify panel shows — the install status plus the browser console output is usually enough to pin it down in one reply.