Umami Not Tracking Visitors (No Data Showing)

How to fix it

Try these in order — the most common fix is first.

1. 1. Confirm the script is on the page

   Copy steps
   1. Open your site and view the page source
   2. Search for data-website-id and check the ID matches Settings > Websites in Umami
   3. Purge your CMS, CDN and Cloudflare caches and reload in a private window
   Did this fix it? Yes No

2. 2. Check data-domains matches the hostname exactly

   Copy steps
   1. If the script tag has data-domains, compare it with the hostname in the address bar
   2. Add both forms, e.g. data-domains="example.com,www.example.com"
   3. Or remove data-domains to track every host
   Did this fix it? Yes No

3. 3. Watch the request in DevTools

   Copy steps
   1. Open DevTools > Network and reload the page
   2. Find the request to /api/send (or your COLLECT_API_ENDPOINT) and check it returns 200
   3. If it's marked blocked, disable your ad blocker or Brave Shields and try again
   4. If you see a CORS error or 301/302 responses, fix your proxy (next fix)
   Did this fix it? Yes No

4. 4. Fix proxy redirects and CORS (self-hosted)

   Copy steps
   1. If Cloudflare SSL mode is Flexible and Nginx redirects HTTP to HTTPS, switch Cloudflare to Full (strict) to stop the redirect loop
   2. Test the endpoint with curl -i -X OPTIONS https://your-umami/api/send and check for a 200 with CORS headers
   3. Make sure your proxy doesn't strip or override CORS headers on the preflight request
   Did this fix it? Yes No

5. 5. Check consent banners and self-exclusion

   Copy steps
   1. Test with the consent banner disabled; if tracking works, set the correct consent category for the Umami script
   2. In the browser console run localStorage.getItem('umami.disabled'); if it returns 1, run localStorage.removeItem('umami.disabled')
   Did this fix it? Yes No

Symptoms

The dashboard shows zero visitors or nothing in Realtime after adding the tracking code, or tracking stopped after a site or server change.

Why it happens

• Tracking script not in the page, or an old cached page is served
• data-domains set to example.com while the site loads on www.example.com (or the reverse)
• Your own ad blocker, Brave Shields or a privacy extension blocks the script
• A cookie consent banner only loads the script after consent, or in the wrong consent group
• CORS errors or redirect loops when Umami is behind Cloudflare and Nginx
• Wrong data-website-id or data-host-url after moving the Umami instance
• localStorage umami.disabled set in your browser (you excluded yourself)

This guide also covers

• umami not tracking
• umami not working
• umami no data
• umami analytics not showing visitors
• umami realtime not showing

Other Umami errors

• Umami Blocked by Ad Blockers (uBlock Origin, Brave)
• Umami v3 Upgrade: MySQL Not Supported
• Umami Migration Failed (Prisma P3009 / P3018 Error)
• Umami Docker "Unable to Connect to the Database"
• Umami Default Login and Forgot Password Reset
• Umami Shows Wrong Country or "Unknown" Location
• Umami Custom Events Not Showing
• How to Exclude Your Own Visits in Umami