SonarBack to workspace

Your traffic. With clear boundaries.

Install once on a verified website

  1. Create your independent Sonar account.
  2. Verify the matching business email, connect your domain and publish its Sonar verification file.
  3. Open Traffic analytics, choose the verified domain and select Get tracking code.
  4. Add the generated script to the public pages you want measured.
  5. After your website’s analytics-consent control grants permission, call window.SonarAnalytics?.consent(true). On withdrawal, call it with false. The default script does not collect until permission is granted.
  6. For SPA navigation, call window.SonarAnalytics?.pageview() after the route changes, or dispatch the sonar:pageview event. Query/hash-only changes are not collected.
  7. Return to the private analytics view. Choose 1, 7 or 30 UTC days. Visible reports refresh every 30 seconds when enabled.

What is recorded

Public pathname, referrer origin, coarse device class, server time and approximate country/city from Cloudflare IP geolocation. Raw IPs, full browser agents, query strings, fragments and persistent tracking cookies are not stored. Daily visitor estimates use a secret-key HMAC scoped to the site and date, so they are not unique-person counts across a month.

Respect visitor choices

The script respects Do Not Track and Global Privacy Control. Connect it to your existing consent choices and describe this measurement in your privacy notice. Do not install it on pages with identifying pathnames or sensitive information. Default protected-path exclusions include app/admin/account/login/signup/billing/password pages. If consent, blockers or the shared free 5,000-event daily budget prevent recording, reports will be incomplete.

CSP and troubleshooting

If you use a Content Security Policy, allow https://sonar.pactuno.online in script-src and connect-src. Confirm the page’s exact origin matches the verified Sonar origin, including www. Check consent is granted, the snippet’s site ID is correct and tracking is enabled. Releasing the organization claim stops collection. Earlier visits cannot be reconstructed.

Control and privacy

Only the owning Sonar account can read reports. Pause tracking from its dashboard, delete the tracking site and its events, or delete workspace data. Data is retained up to 30 days. No automatic reports or emails are sent. City/country are approximate; bot filters and shared networks affect estimates.