A checklist for when your first visit doesn't appear: the line, local addresses, your own ignore setting, script combiners, browser extensions and domains.

First, give it a minute

A visit takes about a minute to reach your dashboard. If it’s been less than that, wait and look again. The Install page and your stats page refresh by themselves.

Then work through these checks in order. Most problems are one of the first four.

1. Is the line really on the page?

Open your live site, view the page source (right-click, View Page Source), and search for crustat. You should find the line with data-site and your site ID.

Not there? Your builder or template may not have saved it, or it’s only on one page. Put it in the shared header or template, see add Crustat to your website.
Cached pages? If your site or host uses a cache, clear it so pages pick up the new line.
Right ID? The data-site value must match the Site ID under Site settings → Install. A line copied from another site sends visits to that site instead.

2. Are you on a local address?

Nothing is sent from localhost, 127.0.0.1 or [::1]. That’s on purpose, so testing on your own computer stays out of your stats. Test on your live site. A page opened straight from a file on your computer isn’t recorded either.

3. Are you ignoring yourself?

If you turned on Ignore my visits on this browser, or opened your site with #crustat-ignore, that browser sends nothing at all. Try a private window or another browser, or switch it off, see ignore your own visits.

On WordPress, the plugin also leaves out people who can edit the site while they’re signed in. Test signed out, see install Crustat on WordPress.

4. Is a script combiner in the way?

Cloudflare Rocket Loader and some caching or optimization plugins rewrite scripts in a way that stops Crustat from finding its own line, so it can’t tell which site it’s on and sends nothing. Add data-cfasync="false" to the line, or exclude it from the plugin. See Rocket Loader and script combiners.

5. Is something blocking it?

Browser extensions can stop the script in your own browser. Test in a private window or another browser with no extensions.
A Content-Security-Policy on your site can block it for everyone. Allow https://stats.crustat.com in script-src and connect-src.

To check, open your browser’s developer tools, go to the Network tab and reload the page. Look for script.js from stats.crustat.com, then a request called event. If event is there and its status is 204, the visit was sent.

6. Is the page on one of your site’s domains?

Crustat records visits on your site’s domain and all its subdomains. Visits on any other address, like a separate shop domain or a preview address, are recorded but left out of your stats. They show up in the bot visits left out note under your chart, as Copies of your site on other addresses.

If that other address is really yours, add it under Site settings → General → Domains. A newly added domain can take about 5 minutes to start showing up. See add and manage your sites.

7. Are you testing with an automated browser?

Visits from test tools and automated browsers, and from cloud servers, are left out on purpose. Test from a normal browser on a normal connection. See how bots are kept out.

8. Is your workspace active?

If your trial has ended and no plan was chosen, Crustat keeps recording visits but hides your stats until a plan is picked. If the workspace has stopped recording altogether, new visits aren’t saved. See plans, trial and billing.

Still nothing?

Write to hello@crustat.com with your site’s address and what you’ve tried. A real person answers.

Visits aren't showing up