Troubleshooting
Fixes for the most common reasons Muro isn't showing what you expect.
Most problems with Muro come down to one of a few causes: the script isn't on the live site, something blocks it, or collection is paused. Pick the page that matches what you're seeing.
First check: is your change live?
If the snippet is in a local branch or an unpublished CMS draft, your live site doesn't have it yet. Deploy or publish, wait a minute, then reload your site.
Quick check
Open your site, open your browser's DevTools, go to the Network tab, type collect in the filter box and reload the page. A working install shows a POST to https://cdn.muroanalytics.com/collect with status 202. Then set your dashboard's time range to Live to see the visit arrive.
Fixes
No events are showing
The script is installed but the dashboard stays empty.
Fix Content Security Policy errors
The console shows "Refused to load" or "Refused to connect".
Events are paused
Trial ended, payment failed, pageview limit reached, or tracking switched off.
Pageviews counted twice
Every page load shows up as two pageviews.
muro is not defined
Calling window.muro.track() throws an error.
Numbers differ from another tool
Muro and Google Analytics, Plausible or your logs don't agree.
Tracking across subdomains
Your site spans www, app, blog or shop subdomains.
Still stuck?
Email support@muroanalytics.com. We reply within a business day. To help us answer on the first try, include:
- Your project ID, from Settings → Project → Tracking script.
- The URL of a page where the snippet is installed.
- What you expected to see, and what you see instead.
- A screenshot of the DevTools Network tab filtered to
collect, showing the request's status and, if you can, its payload. - Any errors from the DevTools Console.
- Your framework or site builder, for example Next.js App Router, Webflow or Shopify.