URL anonymization: Global settings and Specific Instructions

Some URLs on your website can directly identify individuals which you must configure Blockmetry to anonymize at the point of collection by submitting to us Specific Instructions. These URLs would show up in the web analytics records Blockmetry produces as the directly requested URLs or referring URLs. Further, some third-party popular services include user-identifying URLs, and Blockmetry is regularly updated to anonymize these URLs by default. These URLs would show up as referring URLs in the web analytics records Blockmetry produces. Since Blockmetry take privacy by design seriously, Blockmetry has rich capabilities to anonymize such URLs.

User-identifying URLs on your website.

These URLs occur when a URL contains a unique part that directly or indirectly can be tied to an individual. Typical examples include:

URLs on third-party websites

Some popular services produce URLs that could identify the individual from which measurements came from, which show up as referring URLs to your website. For example, on LinkedIn, a messaging thread accessed on the web has the following URL format: https://linkedin.com/messaging/thread/1234567890123456789/. Given that the thread ID (the 1234567890123456789 part) is unique to yourself and the person (or people) on the thread, any clicks to your site from links in the messaging thread could identify who on the thread clicked the link. Such URLs are anonymized by Blockmetry and recorded as https://linkedin.com/messaging/thread/LinkedInThreadID/. Please note that Blockmetry cannot realistically anonymize referring URLs from all third-party sites, but we would love your help in finding more examples. Please tell your account manager.