Script Health
The script-health indicator on the board tells you whether StatelessID has accepted a beacon from your domain recently. A Live status means a beacon arrived and was accepted. A Quiet status means no beacon has been accepted yet or none has arrived in a significant stretch of time.
Live versus Quiet
The status chip in the top-right corner of the board header shows one of two states. Live means the system has a record of accepting at least one beacon from your domain, and the timestamp of that last accepted beacon is recent. Quiet means either no beacon has ever been accepted, or the most recent accepted beacon was so long ago that it cannot confirm the script is still working.
A Live indicator is reassuring, but it is not a real-time signal. It reflects the most recent stored timestamp, which updates when a beacon is accepted and persists until the next accepted beacon overwrites it. On a low-traffic site, a beacon from hours ago will still show Live.
A Quiet indicator on a site that should have traffic is always worth investigating. The most common causes are a missing script tag, a wrong site key in the snippet, a domain mismatch in your account, or a Content Security Policy (CSP) on your site that blocks the beacon.
What the Live 15-minute tile adds
The Live metric tile on the board shows the number of page view beacons accepted in the last 15 minutes. This is the most current view into recent activity. A non-zero number in this tile is strong evidence that the script is installed and working right now on at least one page of your site.
A zero in the 15-minute tile does not mean the script is broken. It means no beacons arrived in the last 15 minutes. On quiet sites — nights, weekends, or newly launched pages with little traffic — zero is expected. Check the Today tile and the by-day chart to put the 15-minute number in context.
If you want to test the script quickly, open an incognito window, visit a page on your site that has the script tag, and then reload the dashboard board. If the 15-minute tile increments by one, the script is working. If it stays at zero, the script is not sending accepted beacons.
Why a beacon might be rejected
A beacon from your site can be rejected for several reasons, none of which affect the script-health indicator directly — the indicator only tracks accepted beacons. The most common rejection reasons are: the site key does not match any registered domain, the request arrived from a bot or automated agent, the domain in the request does not match the registered hostname, or the per-minute rate limit for that domain was exceeded.
The filter-impact panel on the board separates accepted counts from dropped counts. Quota drops, bot drops, country drops, and event-limit drops are all listed there. If your script is sending beacons but the board shows no accepted visits, look at the filter-impact panel to see if the drops explain the discrepancy.
A CSP header on your site that does not include the StatelessID collector in the connect-src directive will silently block beacons in the browser. The script will not throw a visible error in most browsers; the beacon will simply not arrive. Check your site's CSP headers and the install article for the correct connect-src value.
Checking the site key
The most reliable way to confirm the script is configured correctly is to view the HTML source of a page on your site, find the script tag, and confirm that the site key in the script URL matches the site key shown in your dashboard Settings page. A single transposed character in the key means every beacon is rejected silently.
The site key is a short alphanumeric string appended to the script URL or embedded in a data attribute, depending on the snippet version you installed. It is not a secret — it is in the HTML source of every page that loads the script. If you have lost the snippet, go to the Setup page in your dashboard to retrieve it.
What Quiet does not mean
A Quiet status does not mean your account is inactive or your subscription is paused. It only reflects the absence of a recent accepted beacon. If your site is down for maintenance, Quiet is expected and normal. If you have just registered a new domain and have not yet installed the script, Quiet is the correct state.
Quiet also does not prevent the board from showing historical data. If the board was Live last week and went Quiet this week, the data from last week is still on the board under the corresponding date range. Nothing is deleted when the status changes to Quiet.
Troubleshooting
If the board shows Quiet and you believe the script is installed, open your browser's developer tools Network tab, visit a page on your site, and look for a request to the StatelessID collector URL. If the request is absent, the script tag may not be on that page. If the request is present but returns a non-200 status code, note the code and check the errors article for what it means.
If the request appears in the Network tab and returns 200, but the board still shows Quiet after a few minutes, confirm that the site key in the request matches the one shown in your dashboard Settings. Also confirm that the domain hostname in your account matches the domain you are testing on exactly, including www vs. non-www.