Cookies:
SEAL Metrics doesn’t work with cookies, neither 3rd nor 1st party cookies.
Digital fingerprinting, Userid, and any kind of technology that allows to individual tracking:
SEAL Metrics, in compliance with ePrivacy Regulation, doesn’t work with any kind of technology that can track individual users, even if the data is hashed, encrypted, or anonymized.
Userid:
SEAL Metrics, in compliance with the ePrivacy Regulation, doesn’t work with any kind of technology that can track individual users, even if the data is hashed, encrypted, or anonymized.
User-Agent:
SEAL Metrics, in compliance with the ePrivacy Regulation, doesn’t work with any kind of technology that can track individual users, even if the data is hashed, encrypted, or anonymized.
IP:
We don’t work with IP data, even if the IP information is hashed, encrypted or anonymized.
Aggregated Data:
SEAL Metrics only works with aggregated data. We counts every single page view in aggregated way. Our technology is not based on individual tracking. We can’t identify an individual user.
Visitors:
For us a visitors is a click that is coming from a referrer that is not the same domain tracked.
For example, if a page view is loaded and the referrer is coming from the same domain, then it’s a page view; if the referrer is coming from other domain or it’s empty, then is a visitor.
First-Party Tracker:
SEAL Metrics has developed a new 1st party pixel. This 1st party tracker keeps it from being blocked by adblockers. Following our business philosophy, we never track individually.
UTM Parameters:
SEAL Metrics can read your UTMs parameters or your special parameters for having statistics by:
- Source: utm_source
- Medium: utm_medium
- Term: utm_term
- Campaigns: utm_campaign
GEO Reports:
SEAL Metrics doesn’t show geo data because you can individually identify your users, depending on if they are connected. As we previoulsy explained we don’t work with IP information, nor do we work with other information that can identify individually your users.
