Beyond World Wide Privacy Regulations

How SEAL Metrics works

SEAL tracks isolated hits instead of visitors

Since Urchin Analytics, web analytics solutions (WAS) are based on unique visitor behavior tracking. WAS tracks every page requests by visitors in order. But, this tracking methodology based on store *every single click made by each user* requires consent according to the ePrivacy Directive. It's a directive and not legally enforceable for now.

SEAL does it differently. It only tracks hits and these hits have NO relation with other hits. So if one unique visitor visits 7 different URLs, SEAL will track 7 hits, but SEAL doesn't know if these 7 hits were made by 1, 2, or 4 visitors.

SEAL doesn't track individually

Based on our interpretation (and that of the lawyers we contacted ), the ePrivacy Directive states:

If you're tracking a visitor individually, you MUST ask for consent.

It doesn't matter if you're tracking individually with cookies, super-hashed digital fingerprinting with a short lifetime, server-side, or any similar technology. The directive is clear: If you track individually you require consent.

SEAL metrics does NOT track individually. We are a privacy-first web analytics and want Marketers in the EU to have to best web analytics tool making more efficient your marketing strategy.

SEAL identifies sources, not users

Since we do not No User ID or Fingerprinting, we can measure 100% of your traffic without any legal risk. SEAL works with a proprietary system based on IDs, which does NOT identify users. It identifies traffic sources. Each time a user accesses the website from a source, the system assigns an ID (not user_id) to that source. Refer to the example below. And no, it does not affect your SEO :)


Once a user visits your site, SEAL generates an id for that source in the parameter _adin. Adin parameter will appear in the URL and stick in the URL during all the navigation of the visitor. Once the user makes a conversion, SEAL's conversion pixel is triggered, asking: "what is the _adin parameter that I belong to?". Then SEAL can assign this conversion and the revenue to a source+campaing+term.

SEAL doesn't store or handle any personal data

According to our latest Audit, GDPR doesn't even apply to SEAL because it does not store or handle any personal data. Saying "we are GDPR compliant" seems like an understatement :)

Legal peace of mind

Before creating SEAL Metrics we made a lot of interviews with lawyers from different firms. Our main goal was to create a Web Analytics Solution that is fully aligned with the core of the privacy regulation.

We didn't want that our solution can be unuseful due a normative change. We are completely aligned with the focus of all Privacy Regulations: Protect the privacy of citizens.

In this way, SEAL Metrics doesn't track individually, respecting completely the privacy of users, because we don't track them.

We could make a any-law compliant, but itsn't enough for us, we wanted to create the most sophisticated analytics tool not based on tracking people,... and we did it! For this reason you must work with a Google Analytics alternative.

Trusted by EU Marketers

SEAL Metrics™️ is a Cookieless Conversion Tracking tool for Marketing teams who need to see all conversions per source, campaign, medium, keyword to optimize their campaigns.

  • Running in 5min
  • 100% of my traffic
  • GA complementary
  • Legal peace of mind