Skip to main content
CustomerOS can identify 30-40% of the companies that your website visitors work from their IP address. To get started, you need to provide your domain(s) to the CustomerOS team in order to link the visitors to your website to your CustomerOS Workspace. We will set up a reverse proxy for you to use to maximise the amount of users you can receive events from, without causing too much technical complexity. All you need to do is add a CNAME DNS record to your websites domain that will allow us to have our reverse proxy behind your domain. During a setup call you will add the following script tag to the Header of your website, replacing the URL domain with that of your new reverse proxy Once done, the CustomerOS team will verify that this is working, and if not will help troubleshoot any issues identifying traffic. With the tracker working, all ICP fit organizations from your web traffic will be created as leads in your workspace, and usage added as a Touchpoint to the respective Lead.
Common Error: If you use a Content Security Policy (CSP) list to block websites please add ipify.org to your website’s list. CustomerOS uses ipify.org to log the users IP address.

​
GDPR Compliance

TL;DR Website Visitor Identification is GDPR compliant.
  1. CustomerOS falls under the basis of “legitimate interest” under GDPR rules
  2. We recommend that you state your usage of CustomerOS in any places you list your use of other software that utilizes customer data
  3. We recommend that you update your cookie policy to indicate that CustomerOS may set a cookie named ‘CosUserId’, with a lifetime of the remainder of the user’s session, and with the purpose to distinguish between visitors.
CustomerOS’s tracker collects data of your website’s visitors to our infrastructure and our partner infrastructure hosted on AWS (Amazon Web Services), located in Dublin, Ireland (eu-west-1) and Frankfurt, Germany (eu-central-1) respectively. All collected data is encrypted both on transfer and while at rest. We collect behavioral data of all your website’s visitors. This includes; the pages they viewed, by which source they were referred, and how much time they spent on your site. We process your visitors’ IP addresses which we match against our proprietary database to check the company behind the visit and their geographic location. All visitor data is then aggregated at the company level. Our legal justification falls under legitimate interest. We do not share a visitor’s IP address and provide our customers only with publicly accessible corporate data, which is exempt from GDPR.
“processing is necessary for the purposes of the legitimate interests pursued by the controller or by a third party, except where such interests are overridden by the interests or fundamental rights and freedoms of the data subject which require protection of personal data, in particular where the data subject is a child.”
See Art. 6(f) GDPR - Lawfulness of processing for reference. When it comes to B2B marketing and analytics, legitimate interest is the most suitable basis, and commonly used. The justification of “legitimate interest” is based on the simple ground that the individual whose visit data is processed could have a legitimate interest in what you’re offering them. Furthermore, CustomerOS’s focus is on providing business identifications rather than data on a personal level. For that reason, CustomerOS uses personal data to a minimal extent.

​
Cookies

The CustomerOS tracker sets a cookie in the visitor’s browser for it to be able to distinguish between different visitors on the same network: 
Cookie: CosUserId
Purpose: A unique identifier to distinguish between different visitors
Lifetime: Session
If you use CustomerOS and need to comply with GDPR, we recommend you do the following:
  • Update your privacy statement to inform visitors about your usage of CustomerOS.
  • Update your cookie notice to notify visitors about cookies set by CustomerOS.
GDPR requires you to inform visitors about what happens to their personal data. Hence, you need to add a note in your privacy statement that explains that you are gathering information and for what purpose. You’ll also need to update your cookie notice to notify visitors about the cookie set by CustomerOS. Here’s an exemplary text snippet you can include: “We use CustomerOS to measure the business usage of our website. This service shows us the company names and addresses based on the IP addresses of our visitors. For CustomerOS to distinguish between different visitors on our website, it sets a cookie named ‘CosUserId’ with a lifetime of the remainder of the user’s session.”

​
Third-party Visitor Identification Integrations

CustomerOS opts to be fully compliant with the Data Protection Act and only deanonymises companies. If you wish to deanonymise individuals using 3rd parties it is your and your solution’s responsibility to not identify European website visitors to remain in compliance with this Act.
Reach out if you have an existing solution you would like to feed into CustomerOS.
⌘I