Tracking not detected

Symptom: Tracking status says Waiting for tracking activity after you visit the deployed site.

Check the deployed page

1. View the deployed page source and confirm the tracker tag from this Website's snippet is present once in the HTML head.
2. Confirm data-domain is the registered root and data-write-key is the current key for that Website.
3. Open a page on that registered root or subdomain. A different root needs to be registered.
4. Check the browser Network tab for the Graytower script and /api/collect request. A strict CSP, consent manager, or blocker can stop either request.
5. Return to Tracking status and select Verify installation.

If Tracking shows a mode mismatch, the deployed script is different from the Website's Visitor identity setting. Copy and deploy the current snippet: /js/script.cookieless.js for cookieless or /js/script.js for first-party identity.

Read a rejected request

The first accepted pageview changes the status. A custom event alone is not the installation signal. If the network request is rejected, inspect its response: 401 indicates an unknown write key and 403 an origin mismatch.