Our Optivo library collects various pieces of information about visitors and leads we send to your website, depending on the configuration. This data is used to identify visitors and perform matching on our server.
Here is a summary of the data collected and its purpose:
| Data Collected | Purpose |
|---|---|
| Anonymous ID | Generated against all traffic that triggers the library initialization. Stored in local storage as ‘optivo.id.v1:visitorId’. |
| User Agent | Captured to identify the browser and operating system of the visitor. Stored as events in local storage as ‘optivo.id.v1:events’. |
| IP Address | Captured to identify the location of the visitor. Stored as events in local storage as ‘optivo.id.v1:events’. |
| Encrypted Email | Captured as part of the conversion process and sent to our server for matching purposes. If no match found, the data is destroyed. Stored as events in local storage as ‘optivo.id.v1:events’. |
This data is stored in local storage on the visitor’s device and is not shared unless we can identify the visitor via query string parameters set by ESB Connect or by an email. In such cases, this data is sent to our server to perform matching. Before any event data is sent, any captured email is encrypted with SHA256. We never receive plain text emails.
On our server, we perform matching to identify whether this visitor matches a lead we sent. If a lead is found, we store this data. If not, the data is destroyed.
If you do not wish to send IP or user agent data, you can disable this by applying some additional configuration parameters to the library installation script:
(Please note boolean parameters ‘captureIp’ and ‘captureUserAgent’ which are true by default. Set these to false to prevent this data from being captured.)
