Flowpoint gives you granular control over the data you collect on your website. You can configure its various privacy settings to meet your organization's needs or to adhere to compliance requirements.
Programmatically Enable/Disable Flowpoint
When you add Flowpoint to your website, it collects data by default. In some cases however, you may need to request and receive user consent before sending data to Flowpoint. Typical scenarios for this approach are capturing cookie consent or terms of use acceptance.
To disable Flowpoint, implement the following line of code:
You can programmatically set flowpointDisabled on page load or using a consent solution. For example, flowPointDisabled might initially be set to false (Flowpoint tracking is enabled) on page load, but can be programmatically disabled if a website visitor opts-out of tracking cookies. The exact implementation depends on your use case and any compliance requirements you are bound to.
IP Address & Email Tracking Settings
Each project in Flowpoint can be configured with specific IP address and email address tracking settings.
IP Blocklist
Utilize the IP address blocklist to exclude specific IP addresses from being tracked by Flowpoint. There are two purposes for this functionality:
You can block a specific user or segment of users from being tracked.
You can block internal traffic from being tracked. This is useful for filtering-out internal use of your website by organizational members.
The IP blocklist is configured for each project in your Flowpoint account. Configure the blocklist by selecting a project, navigating to Settings and selecting Project.
Email Address Blocklist
Utilize the email address blocklist to exclude specific email addresses from being tracked by Flowpoint. There are two purposes for this functionality:
You can block specific user email addresses if required by privacy regulations.
You can block tracking for key internal stakeholders. For example, you may not want to track website usage by executives or HR leaders.
The email blocklist is configured for each project in your Flowpoint account. Configure the blocklist by selecting a project, navigating to Settings and selecting Project.
Capturing Email Addresses
By default, Flowpoint does not capture email addresses. Email addresses and other user attributes are captured using Visitor ID. The email address blocklist is only relevant when using Visitor ID to capture email addresses.
Limiting or Disabling IP Address Tracking
In addition to blocking specific IP addresses, you can limit or disable your collection of IP addresses altogether.
Collecting Partial IP Addresses
You can force Flowpoint to collect only the first octet in an IP address. For example, the IP address "192.168.1.1" would be stored in Flowpoint as "192.xxx.xxx.x.x". This functionality useful if internal policies or privacy regulations prevent you from identifying traffic by region using IP addresses.
Partial IP address collection is a setting applied to each of your projects in Flowpoint. To configure the setting, navigate to a specific project, select Settings and then Project.
Important: If you enabled collection of partial IP addresses, you will not be able to detect the geographic regions of your website visitors.
Learn more about IP addresses and how they're used by reading Understanding IP Addresses on the Flowpoint blog.
Disabling IP Address Tracking Altogether
In some cases, you may need to disable IP address tracking altogether. If this is necessary, you can configure the setting for specific projects. When IP address tracking is disabled, you will no longer be able to detect the geographic regions of your website visitors.
Disabling IP address tracking is a setting applied to each of your projects in Flowpoint. To configure the setting, navigate to a specific project, select Settings and then Project.
Learn more about IP addresses and how they're used by reading Understanding IP Addresses on the Flowpoint blog.
Additional Resources
Explore the finer details of Flowpoint's approach to privacy by reviewing our legal and compliance documentation: