No Data Yet
If the dashboard board shows zero for every metric, no accepted beacons have been recorded for the selected domain in the selected date range. Work through this checklist in order to find and fix the cause.
Step one: confirm the script is on the page
Open a page on your site in a browser and view the page source. Search for the StatelessID script tag — it will contain a reference to the asset.js file hosted on statelessid.com. If the tag is not in the source, the script has not been installed on that page. Return to the Setup page in your dashboard to get the snippet and paste it into your site's HTML, ideally in the <head> section or just before the closing </body> tag.
If you are using a CMS, theme, or page builder, the snippet must be placed in a location that appears in the rendered HTML output of every page you want to track. Pasting it into a page editor that renders it as visible text rather than HTML will not work. Look for a theme header/footer editor, a custom HTML widget, or a plugin that allows injecting scripts into the page head.
After installing the snippet, load the page, wait 10 seconds, and reload the dashboard board. If the Live metric tile increments by one, the script is installed and working.
Step two: verify the site key
In the page source, find the script tag and locate the site key — it is the alphanumeric string embedded in the script URL or in a data attribute of the tag, depending on the snippet version. Go to your dashboard Settings page and confirm the site key shown there matches the one in your page source exactly. A single wrong character causes every beacon to be silently rejected.
If they do not match, copy the snippet from the Setup or Settings page and replace the existing snippet on your site. Do not try to manually correct the key character by character — copy the full snippet fresh.
Step three: check the hostname match
Go to your domain Settings page in the dashboard and note the hostname registered. Open a browser tab on your site and look at the address bar. The hostname in the address bar must match the hostname in Settings exactly. If Settings shows example.com and the address bar shows www.example.com, the beacons will be rejected as a domain mismatch.
To fix a hostname mismatch, either update the registered hostname in Settings to match the actual domain (with or without www, as your site uses), or configure your site to redirect to the form that matches the registered hostname.
Step four: check the Content Security Policy
If your site uses a Content Security Policy (CSP) header, it must include the StatelessID collector in the connect-src directive. Without this, the browser will block the beacon silently. Open the browser developer tools Network tab, visit a page, and look for the beacon request. If it is blocked by CSP, you will see a console error mentioning CSP and the request will not appear in the Network tab at all.
Add the StatelessID collect URL to your connect-src directive. The exact value to add is in the Install section of the Help Center under the Content Security Policy article. A wildcard *.statelessid.com in connect-src also works.
Step five: check the date range
If the board shows data for some ranges but zero for the one you are viewing, the selected date range may be a period before the script was installed. Switch to "today" or "last 7 days" and confirm that the board shows visits for those windows.
Also confirm that the UTC date on the board matches your expectations. If you installed the script at 11 PM your local time and the UTC date was already the next day, the visit will appear on the next calendar day on the board. The Today tile is always the current UTC date, not your local date.
Step six: check filter drops
Expand the collapsible drawer on the board and check the filter-impact panel. If bot drops, country drops, or event-limit drops are non-zero and counted visits is zero, the script is sending beacons but every beacon is being dropped at a filter stage. A high bot-drop count on a fresh install usually means your own testing was detected as a bot — clear it by testing from a real browser session rather than from automated tools.
If the country-drop count is non-zero and you are testing from a country outside your configured allowlist, the beacons are being dropped before counting. Either add your country to the allowlist in Filters or temporarily disable the allowlist while testing.
Troubleshooting
If you have worked through all six steps and the board still shows zero, open the browser developer tools Console tab while on a page with the script and look for any errors mentioning the StatelessID URL. A failed network request or a CSP violation will appear as a red error in the console. Note the error message and check the errors article for the corresponding code.
If the network request appears in the Network tab and returns a 200 status, but the board still shows zero after several minutes, confirm that the site key in the request matches the one in your dashboard Settings. Use the browser's request details view to check the exact key value sent.