How can I exclude IP addresses in Piano Analytics?

Configure an IP exclusion in the Exclusions module

1. Open Data Management > Configuration > Exclusions.

2. Set the scope (top right) to the level you want to apply the rule to (for example, Organization or a specific site).

3. Create a new exclusion rule (via the + button).

4. Select IP address as the condition type.

5. Enter:

   • A single IPv4 (only if anonymization is not enabled), or

   • An IP range (required when anonymization is enabled), such as 203.0.113.*

6. Save the rule.

Scope (organization vs. site)

Exclusions apply to the scope shown in the interface at the time you create the rule.

• Use site scope to avoid impacting other sites/domains in the same organization.

• If you need the same rule across multiple sites, ensure it is added for each relevant site (or configured at the organization level if appropriate).

What happens to excluded data?

Not retroactive by default

IP exclusions are not retroactive: only data collected after the rule is saved will be excluded.

If you need historical data to reflect a new exclusion (for example, for an audit or corrected reporting), Piano can perform a data regeneration/reprocessing. This is a separate operation and will incur additional cost depending on the time range and volume. Please contact the support team.

Viewing excluded volumes

Even when traffic is excluded, you can still assess the volume of excluded events.

• Explorer privacy-related views (for example, Privacy > Exclusion), and/or

• Exclusion-related properties such as exclusion_type, exclusion_cause, and exclusion_detail (useful in Data Query with an events metric like Events (all))

⚠️ IP Address Anonymization

If the IP Address Anonymization option is enabled for your organization, we remove the last segment (last octet) of IP addresses before processing them.

As a result:

• Do not provide or enter complete IP addresses for exclusion (for example, 192.0.2.45). They will not be matched.

• Instead, exclude an IP range that corresponds to the truncated value, for example:

  • 192.0.2.* (equivalent to 192.0.2.0–192.0.2.255)

This is expected behavior and is tied to privacy requirements: the full IP is not retained, so the platform cannot reliably exclude a single address when anonymization is enabled.