> For the complete documentation index, see [llms.txt](https://docs.uxwizz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uxwizz.com/guides/troubleshooting/tracking/no-data-is-being-recorded.md).

# No data is being recorded

{% hint style="info" %}
After a successful installation new sessions and data should be tracked and available immediately in your dashboard (after a refresh).
{% endhint %}

### Problem:

{% hint style="danger" %}
No data is being sent to the dashboard.
{% endhint %}

### Possible causes and solutions

1. The **tracking snippet was not included** on the tracked website (check the source code of the page to make sure it was added).
2. **Wrong dashboard server path setting** (after installation or a domain name change). Go to your dashboard Settings->Tracking and click "Reset" next to the "Server path" setting or manually set it to the URL of your dashboard.
3. Caching issues: if you added the tracking script but it's not visible in the source code, the old page might be cached (see [clearing the cache](#clearing-the-cache) below). You should also clear the cache after changing any settings (such as after fixing the server path).

### The tracker loads, but no session starts

Before changing the server path, check whether tracking is allowed for your test visit:

1. Check the visitor's consent choice. If your site uses the UXWizz consent prompt, `UST.onGDPRAccepted` and `UST.onGDPRDeclined` report the response.
2. Check any custom `UST.onTrackingStarted` callback. Returning `false` stops the session from being created, even though the tracking file loaded.

See [Hooks/callbacks](/api/hooks-callbacks.md#available-callbacks) for these events and when to register them. Use your own test visit and make a deliberate consent choice; keep a visitor's declined choice or opt-out intact.

If tracking is allowed, continue with the Network checks below. A failed request needs HTTP/server diagnosis. If no session request is sent, check the tracking decision first.

{% hint style="warning" %}
The easiest way to debug tracking issues is to open the Network tab in the browser dev tools (F12) and check if, in order:

1. The JS tracking file was loaded.
2. If tracking is allowed, the createClient.php request was successful.
   {% endhint %}

### **Clearing the cache**

Depending on your how your website is built, there are multiple caches that might need to be cleared:

1. **Browser cache** - Refresh using CTRL+SHIFT+R (or use your browser's settings to clear the cache for the tracked website and your dashboard).
2. **CDN cache** (such as Cloudflare) - Go to your CDN and Purge the cache for the tracked website and your dashboard (if behind Cloudflare).
3. **WordPress plugin cache** (if you use plugins like WP Rocket or W3 Total Cache) - Clear the website cache from the plugin settings.
4. **Server cache** - Depending on the web server used, you might have an additional caching layer still serving the old JS tracking file. Open the file URL directly in the browser to see if any setting looks outdated.