Your cookie banner is optional
Consent banners exist because trackers store personal data. Remove the tracking and the banner has nothing to ask for.
Cookie banners are not a legal requirement. They are a symptom. A site shows one because something on the page stores identifiers on the visitor’s device and sends personal data somewhere. Under the GDPR and the ePrivacy Directive, that is what triggers the need for consent.
Remove the tracking that needs consent, and the banner has nothing to ask for.
What sonex does instead
sonex counts a visit without ever identifying the visitor. There is no cookie, no local identifier, and no cross-site fingerprint. A pageview becomes an anonymous, aggregated number the moment it is received, and the raw request is never retained as a personal profile.
Because no personal data is processed, there is no consent to collect and no banner to display.
What you still get
Dropping the banner does not mean dropping the numbers. You keep:
- Visitors, views, bounce rate and visit duration
- Referrers, top pages and outbound links
- Country, region and city from coarse geography
- Realtime, funnels and session flows
The tradeoff people assume exists, insight versus privacy, is not real. You can have the reports and respect the person reading them.
The one script
Add the tracker to your <head> and delete the consent modal:
<script defer
src="https://trysonex.com/sonex.js"
data-website-id="YOUR_WEBSITE_ID"></script>That is the whole migration.