Track and report 100% of your website data
Download all your data at any time
You do not need cookie consent for SEAL's data
Data Studio Connector coming soon
Actionable & non-sampled data reports
Offline Conversion tracking coming soon
Connect your data to any management tool with our Rest API
SEAL Metrics tracking system is based on counting completely isolated hits (page views). With this tracking system allows, you are confident that your cookieless analytics will not be banned with the next change in legislation.
GDPR, CCPA, PECR, and ePrivacy Regulations: all these regulations and directives have an essential and big goal: To protect citizens' privacy.
Privacy is a human fundamental right. By choosing SEAL Metrics, you are protecting your visitors' privacy.
If you're going to track your visitor's website behaviour individually, even if anonymously, you should ask for consent. Bounce rate, session duration and pages per session are examples of metrics that still require consent according to the ePrivacy Directive. They are tracking your visitor's individual journey on your website.
SEAL Metrics does not track visitors individually. We simply do not track people. By not tracking people, there is no risk of violating your visitor's privacy. Most cookieless analytics solutions use digital fingerprinting technology. We don't.
Digital fingerprinting technology is based on creating an ID from the user's device. This ID is created with an algorithm that considers your browser's setup, the resolution of your screen, IP,... and other variables that can make your device unique.
Once the cookieless tracking has generated an ID of your device, it starts to track you. You might be wondering "How different is it from cookie-based analytics?" The big difference is how this ID is generated.
So, under our understanding of current regulations (ePrivacy Directive), we consider that if you track users individually, you must request consent to track them.
For this reason, SEAL does NOT use digital fingerprinting technology. The goal of a cookie and digital fingerprinting ID is the same: to track individually.
Some digital fingerprinting systems suggest a workaround of deleting the ID after 24h or even less. There is no difference between a digital fingerprinting-based-ID and a cookie-based-ID regardless of the duration 24h, 12h,...
The big difference between cookie tracking and digital fingerprinting tracking is that cookie-IDs are stored in the user terminal, but digital fingerprinting-IDs are not.
Regulation is crystal clear about that. You must require consent if you store "something" in the user's terminal.
Not seeing any changes since the cookie banner?
Use EditThisCookie extension to check if it's installed correctly. If you are running Google Ads, the Enhanced Conversions might still be tracking regardless of the visitor's decision.
You’re not seeing 30-70% of your traffic in GA
≈ 35% of sources are mislabeled as direct traffic
Your basic metrics are misleading
Not seeing any changes since the cookie banner?
Use EditThisCookie extension to check if it's installed correctly. If you are running Google Ads, the Enhanced Conversions might still be tracking regardless of the visitor's decision.