Bot Rules let you remove traffic that is generated by known spiders and bots from your report suite. Removing bot traffic can provide a more accurate measurement of user activity on your website.
After bot rules are defined, all incoming traffic is compared against the defined rules. Traffic that matches any of these rules is not collected in the report suite and is not included in traffic metrics.
Removing bot traffic typically reduces the volume of traffic and conversion metrics. Many customers find that removing bot traffic results in increased conversion rates and increases in other usability metrics. Before removing bot traffic, communicate with stakeholders to make sure they can make the necessary adjustments to key performance indicators as a result of this change. If possible, it is recommended to first remove bot traffic from a small report suite to estimate the potential impact.
We recommend defining no more than 200 bot rules per report suite.
Bot traffic data is stored in a separate repository for display in the Bots and Bot Pages reports.
Impact of Bot Rules on Data Collection Bot Rules are applied to all analytics data. Data removed by Bot Rules is visible only in the Bots and Bot Pages Reports. ASI Slots honor bot rules on historical data if they are enabled at the time of reprocessing.
VISTA rules are applied before Bot Rules (see Data Processing Order). Therefore, if you have a VISTA rule in place to send bot traffic to another report suite, the original report suite's bot reports populate with little or no data.
High-Hit Visit Processing: If more than 100 hits occur in a visit, reporting determines if the time of the visit in seconds is less than or equal to the number of hits in the visit. In this situation, due to the cost of processing long, intense visits, reporting starts over with a new visit. High-hit visits are typically caused by bot attacks and are not considered normal visitor browsing.
Impact of IP Obfuscation on Bot Filtering The IAB bot list is based solely on user agent, so filtering based on that list is not impacted by IP obfuscation settings. For non-IAB bot filtering (custom rules), IP may be part of the filtering criteria. If filtering bots using IP, bot filtering happens after the last octet has been removed if that setting is enabled, but before the other IP obfuscation options, such as deleting the entire IP or replacing it with some unique ID.?
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.