No events are showing

You've added the snippet but the dashboard shows nothing. The quickest way to find the cause is to watch what your browser sends. This page walks you through it and covers each cause in turn.

Check what your browser sends

What you see tells you where to look next.

No request at all

The script isn't running on the page. Work through these:

1. Is the snippet on the live page? View the page source (right-click → View page source) and search for muroanalytics. If it isn't there, the change isn't deployed or published, or it's on a different template from the page you're testing.
2. Did the script load? Clear the filter and search for muro.js. If the request shows as blocked or failed, it's usually an ad blocker, a network filter or your Content Security Policy.
3. Check the Console. A "Refused to load the script" or "Refused to connect" error means your CSP is blocking Muro. See Fix Content Security Policy errors.
4. Is data-project-id set? Without it, the script does nothing. Copy the snippet again from Settings → Project → Tracking script if you're unsure.
5. Is your page a single-page app? The first load should still send a request. If only later navigations are missing, see Single-page apps.

Request present, but nothing in the dashboard

Check the request's status code.

Accepted but not showing

• Your time range doesn't include now. Set the dashboard time range to Live, which refreshes every 30 seconds, then reload your site in another tab. Events take a few seconds to process.
• You're looking at a different project. Check the project switcher in the top navigation.
• Your trial ended, or a payment failed. Muro still answers 202, but new events aren't stored until you're on an active plan. Look for a red banner at the top of the dashboard and see Events are paused.
• You're over your pageview limit. For up to an hour after you reach it, requests can still return 202 without being stored. See Pageview limits.

Paused project

If Settings → Project → Tracking active is off, Muro rejects events for that project with 404. On Overview, the project shows Paused. Turn the switch back on. It can take a minute or two to take effect.

Wrong project ID

Compare the project_id in the request's Payload with the ID in Settings → Project → Tracking script.

• A 422 whose response mentions project_id usually means the snippet still says YOUR_PROJECT_ID.
• A 404 with a real-looking ID means it belongs to a deleted project or a typo. Copy the snippet again with Copy script.

Muro reads the first <script> tag on the page that has a data-project-id attribute. If another tool on your page also uses data-project-id, place Muro's tag before it.

Ad blockers and privacy extensions

Some ad blockers and privacy extensions block analytics scripts, including Muro. Visitors using them aren't counted, and there's no setting to change that. If you test with one turned on, you'll see nothing. Test with it off.

Corporate networks and firewalls

Some company, school and public networks, VPNs and DNS filters block analytics domains entirely. If Muro works on your phone's mobile data but not on the office Wi-Fi, that's the cause. It only affects visitors on those networks.

Visitor clocks

Muro rejects events stamped more than 10 minutes in the future or more than 24 hours in the past. If a test device's clock is badly wrong, its events return 422. Set the device clock to update automatically.

Verify it works

1. The Network tab shows a POST to https://cdn.muroanalytics.com/collect with status 202.
2. With the dashboard on Live, your visit appears within a minute or so.
3. If you've just set up the project, the onboarding check or the Shopify checklist changes to "Data received!" or turns green.

If you're still stuck, email support@muroanalytics.com with your project ID, the page URL and a screenshot of the collect request.

Next steps