Getting started
Add one script to your site and watch the first event land.
Add the script
Add a site in the dashboard and it gives you a tag with that site’s token already in it. The token identifies which site the events belong to; it is safe in page source, because it can only ever write events to that one site and never read anything back.
Put it in the <head>. `defer` means it never blocks rendering, and the file is around two kilobytes.
<script defer src="https://asuito.com/px.js" data-token="YOUR_SITE_TOKEN"></script>If your site has a Content-Security-Policy
This is the single most common reason a correct tag records nothing. A CSP that does not name this host blocks the script silently — the browser refuses it, the page looks fine, and the dashboard stays empty.
Add `asuito.com` to both `script-src` and `connect-src`. The first lets the file load; the second lets it post the event. Adding only the first is the failure that looks most like success.
script-src 'self' https://asuito.com;
connect-src 'self' https://asuito.com;Confirm it works
Load a page on your own site, then open the dashboard. The first event usually appears within a couple of seconds.
If nothing arrives, use view-source rather than the element inspector. The inspector shows the DOM after scripts have run, so a tag that a CSP blocked still appears there; view-source shows what the server actually sent.
No cookie banner required
The tracker is cookieless by default. It sets nothing on the visitor’s device and stores no identifier that persists across days, which is what makes it exempt from consent requirements in most jurisdictions — this is a description of the default, not legal advice.
If you switch a site to identified mode in settings, that changes, and you become responsible for the consent that mode requires.