Avoid the cookie banner
Avoid the cookie banner with cookieless web analytics.
A cookie banner is more than a popup: it lowers conversions, confuses visitors, and keeps your team busy with consent documentation and CMP platforms. Cookieless web analytics removes the problem at the source. MetriXs sets no cookies and reads nothing from your visitors’ devices, so the consent obligation never triggers and the banner is never needed.
Why the cookie banner appears in the first place
The ePrivacy Directive requires prior consent before a website stores data in, or reads data from, a visitor’s device. Tools like Google Analytics set cookies such as _ga and _gid to recognise the same person across pages and sessions, which is exactly why the law forces a cookie banner in front of any analytics.
The exception for features that are strictly necessary to provide a service is narrow, and rarely defensible for analytics. The reliable path is not to circumvent the rule but to stop triggering it: measure without touching the device at all.
Why a smaller or later banner is not the answer
Many sites shrink the banner, park it in a corner, or delay it by a few seconds. The obligation remains, and visitors who decline stay missing from your numbers. A meaningful share of visitors declines or never answers the dialog, which means lost data on exactly the metrics you want to measure: traffic, sources, conversion rates.
The costs stack up too: every consent management platform costs something monthly, needs configuration for each new script, and adds its own cookies that belong in your privacy policy. More on the data loss caused by cookie banners in our blog: <a href="/blog/cookie-banner-data-loss">Cookie banner data loss</a>.
Cookieless analytics removes the trigger
MetriXs identifies each visit with a daily-rotating hash computed from the IP address, the browser header, and the domain. The hash is computed server-side and never stored on the visitor’s device; the raw IP address is discarded right after processing. Because nothing is stored on, or read from, the device, the consent obligation does not apply to MetriXs analytics. There are no cookies to document and no banner standing between visitors and your data.
Transparency still matters: your privacy policy should disclose that you run web analytics with MetriXs and what it processes. No prior consent is required, just a short notice.
Cookie banner vs. cookieless web analytics
| With a cookie banner (classic analytics) | Cookieless (MetriXs) | |
|---|---|---|
| Prior consent | Required (ePrivacy) | Not required |
| Visitors who decline | Missing from your data | Fully visible |
| Consent management platform | Required, recurring cost | Not needed |
| Conversion rate | Reduced by the popup | Unaffected |
| Cookies on the device | Analytics and CMP cookies | None |
| Privacy policy | Consent documentation and proof | Short disclosure |
What the no-banner path buys you
A complete dataset from day one
Every request is measured, independent of any consent decision. No “decline all” visitors, no unanswered dialogs.
No CMP cost, no upkeep
No consent platform, no banner configuration for every new script, and no consent-log duties.
Legal clarity instead of grey zones
Because MetriXs stores nothing on and reads nothing from the device, the consent obligation does not trigger for your analytics.
Faster pages
The MetriXs tracker is about 4 KB, does not block rendering, and ships no consent logic at all.
Measure without a banner, starting today
Free forever plan, no credit card required. Add one ~4 KB script and your site is measured, without asking visitors to make a choice.
Start free trial →Frequently asked questions
- Can I really run analytics without a cookie banner?
- Yes. MetriXs sets no cookies and reads nothing from visitor devices, so the ePrivacy consent requirement does not apply to your analytics. You embed the script directly and stop showing a banner for web analytics.
- Do I still have to disclose the analytics somewhere?
- Yes. GDPR transparency (Article 13) still applies: your privacy policy should state that you run web analytics with MetriXs and what it processes. No prior consent is needed, just a short notice.
- Do I lose data because visitors never have to decline?
- The opposite. With classic analytics, every visitor who declines the banner is missing from your numbers. With cookieless analytics there is no decision to make, so nobody is missing: you get complete metrics from day one.
- What do I do with my existing banner?
- If MetriXs is your only analytics tool, you can remove the banner for web analytics. If you run other tools that need consent, such as ad networks or embedded video, keep the banner for those.
- How does this interact with other tracking tools?
- Each tool is judged by its own data processing. MetriXs stores no personal data: no cookies, no persistent IP address, no user profiles. Other tools (ad networks, embedded content) keep their own obligations, independent of MetriXs.
- How much does MetriXs cost?
- There is a free forever plan. Paid plans start at €6/month per website. See /pricing for details.
Keep reading
Related topics
- Cookieless web analytics: how it works
- GDPR-compliant analytics: what to look for
- Analytics without cookies or a consent banner
- MetriXs and the GDPR
- Cookie banner data loss
- Do you need a cookie banner for Google Analytics?
- MetriXs vs Google Analytics, compared
- Pricing, free plan and paid plans
- MetriXs for WordPress sites
- MetriXs for Shopify