ÃÛ¶¹ÊÓƵ

Exclude by IP address

You can exclude data from specific IP addresses, such as internal website activities, site testing and employee usage, from your reports. Excluding data improves report accuracy by excluding IP address data. Additionally, you can remove data from denial of service or other malicious events that can skew report data.

To exclude data by IP address, you can configure exclusions as described below, or you can configure your firewall.

Configure exclusions by IP address

NOTE
When configuring exclusions by IP address, consider the following:
  • Hits excluded by IP address are billed as server calls.
  • Private IP addresses do not need to be excluded. Only external IP addresses reach ÃÛ¶¹ÊÓƵ data collection servers. Private addresses include 10.*.*.*, 192.168.*.*, 172.[16-31].*.*, and 169.254.*.*.
  • You can use wildcard indicators (*) to exclude a range of addresses. For example, 0.0.*.0 would exclude all IP addresses between 0.0.0.0 and 0.0.255.0. You can exclude up to 50 different IP addresses.
  • Data from an excluded IP address is excluded for any new hits coming into the system within 5 minutes of the exclusion being set.
  • Data for hits captured prior to the time when changes were made to the IP address is not affected.

To configure exclusions by IP address:

  1. In ÃÛ¶¹ÊÓƵ Analytics, select Admin > All admin.

  2. On the Admin page, select Exclude by IP.

Impact of IP obfuscation section_51B7529FFF16449CA016FDC51D87E2CA

If IP obfuscation is enabled, IP exclusion happens before the IP address is obfuscated, so customers don’t need to change anything when they enable IP obfuscation.

If the last octet is removed, that is done before IP filtering. As such, the last octet is replaced with a 0, and IP exclusion rules should be updated to match IP addresses with a zero on the end. Matching * should match 0.

recommendation-more-help
2969e653-1f9b-4947-8b90-367efb66d529