Skip to main content
Troubleshooting

I installed the script but I don't see any visitors

The common causes, and how to fix each one

Written By David

Last updated 9 days ago

You added the Cromojo snippet to your site, but your dashboard still shows no visitors. This is almost always one of the causes below. Work through them in order. Most take less than a minute to check.

Before you start: visit your website once in a normal browser window, then wait a minute. Cromojo only shows a visit after one has happened.

1. Check the snippet is on your live site

Open your website in a browser. Right-click the page and choose View page source. Search the page (Ctrl+F or Cmd+F) for data-site-id.

  • You find it: the snippet is on the page. Go to step 2.

  • You don't find it: the snippet isn't on your live site. Common reasons:

    • You added it to a staging copy, a draft or a theme that isn't active.

    • Your site builder needs you to publish before changes go live (Webflow, Framer, Wix, Squarespace).

    • Your site or host shows an old cached copy of the page. Clear your site's cache, then check again.

2. Check you copied the whole snippet

The snippet has several lines. All of them matter. In the page source, the Cromojo tag should include both of these:

  • data-site-id="..."

  • data-ingest-key="..."

If data-ingest-key is missing, Cromojo ignores every visit and you won't see an error. Copy the snippet again from Settings > Analytics, using the copy icon, and replace the old one.

If you changed your First-party tracking settings after installing, your snippet changed too. Copy the new version and replace the old one.

3. Check your speed or caching plugin isn't changing the script

This is the most common cause on WordPress.

Speed plugins can combine, minify, delay or move your JavaScript files to make your site faster. When they do this to the Cromojo script, the script loses the settings written on its tag (your site ID and key). It then loads but can't send anything.

How to spot it: in the page source from step 1, you find the Cromojo settings, but the src no longer points to Cromojo. Or you don't find the Cromojo tag at all, only a combined file such as siteground-optimizer-combined-js-...js or autoptimize_...js.

The fix: exclude the Cromojo script from these features. Use the address in your snippet's src (for example app.cromojo.com, or your own tracking subdomain such as stats.yourdomain.com).

SiteGround Speed Optimizer

  1. Go to Speed Optimizer > Frontend > JavaScript.

  2. Open Exclude from JavaScript Combination and select the Cromojo script, if it's listed.

  3. Do the same under Exclude from JavaScript Minification and Exclude from Deferral of Render-blocking JS.

Scripts loaded from another domain sometimes don't appear in these lists. In that case, add this code with a snippets plugin (such as Code Snippets or WPCode) or in your theme's functions.php. Replace the address with the one in your snippet's src:

add_filter('sgo_javascript_combine_excluded_external_paths', function ($exclude_list) {
    $exclude_list[] = 'app.cromojo.com';
    return $exclude_list;
});

Then clear the SiteGround cache (Speed Optimizer > Caching > Purge SG Cache).

Other speed plugins

Look for the setting with this name, and add the address from your snippet's src to its exclusion list:

Plugin

Setting to exclude Cromojo from

WP Rocket

File Optimization > Combine JavaScript files and Delay JavaScript execution

LiteSpeed Cache

Page Optimization > JS Settings > JS Combine and JS Delayed Includes

Autoptimize

JS, CSS & HTML > Exclude scripts from Autoptimize

W3 Total Cache

Minify > JS minify settings > Never minify the following JS files

Cloudflare

Speed > Optimization > Rocket Loader: turn it off, or add data-cfasync="false" to the Cromojo tag

After changing a setting, always clear the plugin's cache and your host's cache. Otherwise your visitors keep getting the old page.

4. Check the domain is allowed

For your protection, Cromojo only accepts visits from domains you've listed. Go to Settings > Analytics > Inclusions > Domains and check the domain you are visiting is there. Subdomains of a listed domain are included automatically.

This matters if your checkout, shop or a country site runs on a different domain. See Tracking more than one domain.

5. Check your own browser isn't blocking you

Your site may be working fine while your own visits are blocked:

  • Ad blockers and privacy extensions (uBlock Origin, Ghostery, Privacy Badger) can block analytics scripts.

  • Privacy browsers and settings such as Brave or DuckDuckGo send Do Not Track or Global Privacy Control. Cromojo respects these signals and doesn't count the visit.

  • You may have excluded your own traffic under Settings > Analytics > Exclusions.

Test from a normal browser window with extensions turned off, or from your phone on mobile data.

6. Check your cookie banner or consent tool

If you use a consent tool (Cookiebot, CookieYes, Complianz, OneTrust), it may hold back the Cromojo script until the visitor accepts. Visitors who don't accept are then never counted.

Cromojo is privacy-first and usually doesn't need a cookie banner for basic analytics. If your consent tool blocks it, add the Cromojo script to the tool's "necessary" or "allowed" list, or set it not to be blocked. See Data Privacy & User Consent to decide what is right for your site.

7. Check your Content Security Policy

If your site sends a strict Content Security Policy, the browser can refuse to load or run the script. Allow the address from your snippet's src under both script-src and connect-src. If you use a tracking address on your own domain, allow it under connect-src too.

You can see if this is the problem in your browser's developer console (right-click, Inspect, then Console): look for a red message mentioning "Content Security Policy".

8. Check the dashboard date range

Make sure the date range on your dashboard includes today. Then click Verify Installation under Settings > Analytics. Verify looks for real visits, so it needs at least one first. If it says not detected, wait a minute and click Retry.

Quick check in your browser

If you're comfortable with developer tools, this is the fastest way to find the cause:

  1. Open your website and right-click, then Inspect.

  2. Open the Network tab and reload the page.

  3. Type cromojo (or your tracking subdomain) in the filter box.

What you see tells you where the problem is:

  • No request to load the script: the snippet isn't on the page (step 1), or a plugin moved or combined it (step 3).

  • The script loads, but no request to /api/track follows: a plugin changed the script (step 3), a consent tool is holding it (step 6), or your browser blocks tracking (step 5).

  • A request shows as blocked or failed: an ad blocker (step 5) or a Content Security Policy (step 7).

  • /api/track succeeds but nothing appears: the snippet is missing its key (step 2) or the domain isn't allowed (step 4).

Still stuck?

Email support@cromojo.com with:

  • your website address,

  • the platform you use (WordPress, Shopify, Webflow…),

  • any speed, caching or consent plugins on your site.

We'll take a look.

Related articles