Blocking Rules allow you to control collection from certain IP addresses or ISPs that you do not wish to track and contribute to your data credit allowance. These can perhaps be internal IP addresses that you do not want to track, or the IP address of known bots perhaps.
To add a Blocking Rule, simply navigate to Settings > Blocking Rules from the left hand menu and click the Add Blocking Rule button. From here you need to select the relevant Scope: whether it is an IP address or an ISP. In the Rule field, you can add an individual IP address, an IP range, or the name of the ISP that you wish to block. You can also add a description so that you know what is being filtered out.
You can also choose to whitelist IP addresses in the Type dropdown. To protect against collection from bots, if Decibel detects unusually high volumes of traffic from a single IP address, collection from that address will be automatically blocked. However, this can be prevented by selecting the Whitelist option.
Once happy, click Save Blocking Rule. You can edit or delete these at any time by clicking the relevant icons.
Please note: There is a limit of 250 Blocked IPs per account. Decibel may also automatically create Blocked IPs if unusual traffic patterns are detected while processing data.
How do I add multiple IPs?
If you have a large number of IP addresses that you don't want to track, you can add IP ranges based on CIDR notation. More information, along with a helpful guide on converting to IP ranges, can be found here.
Examples of accepted IP addresses and ranges can be found below.
Why are some IP addresses showing as "Automatic Block"?
To protect against collection from bots, if Decibel detects unusually high volumes of traffic from a single IP address, collection from that address will be automatically blocked.
Removing Blocked IPs
You can remove a Blocking Rule at any time by clicking the Delete icon next to the relevant Rule that you no longer wish to block or whitelist. This will result in Sessions from the respective IP address or ISP being collected, however does not work retrospectively so will not result in the collection of previous Sessions from that rule.