The fingerprint method is used if the user's browser does not accept cookies, or Anonymized tracking is activated. We use the same method to hold sessions together in both mobile applications and websites.

When a user accesses the website, the pixel checks whether an everID/cookie exists. If this is not the case, a new everID is generated and a new cookie is stored. If the user blocks cookies, an erverID is generated, but no cookie can be set. Instead, the tracking server creates an internal fingerprint to hold the session together. When anonymous tracking is active, the pixel does not create an everID and the tracking server uses the same technology as it does for users that block cookies.

There are multiple ways for the tracking server to process fingerprints:

  • Creating a fingerprint internally by using a hash of the customer ID and user agent.
  • A pixel-generated fingerprint via the client (only available for anonymous tracking and if specifically configured by the customer).
  • Creating a fingerprint by using the user agent and IP address from the client.

The fingerprint is only used to hold the current session together and not forwarded to any permanent databases. It's only stored in the tracking server during the session and deleted as soon as the session ends. The visitor is not recognized during a new session, even if the IP and user agent are identical. Further, a fingerprint ID cannot be viewed via the front end or the raw data.