Piano Analytics already excludes known bots automatically. For the traffic that gets through, look for the signs below, find what the bot activity has in common, then exclude it with a Data Management rule.
Traffic Piano excludes automatically
Piano Analytics relies on industry-standard bot identification signals, including the IAB/ABC International Spiders and Bots List (updated frequently), to exclude known bots. It identifies them by user agent, IP address, or network information.
Extremely abnormal traffic is also flagged as non-human automatically. For example, a visit that generates more than 250,000 events is treated as bot traffic.
New crawlers and automation sources appear regularly, so standard lists can't cover all non-human traffic right away, especially when bots imitate common browsers or vary their patterns.
Signs of bot traffic
No single sign proves that traffic comes from a bot. The more signs you see together, the more likely it is.
-
Page views: only one page view per visit.
-
Time spent: no time spent per visit (0 seconds), or very little across many visits (for example, a few seconds).
-
Visitors: every unique visitor has exactly one visit.
-
Source: Direct traffic only, often with no referrer URL.
-
Timing: a sudden peak on a given day or hour, or other unnatural bursts.
-
Devices and browsers: the same device type and browser repeated across a large volume of visits.
-
ISP or organization: an unusual ISP or connected organization, such as a data center or hosting provider.
-
Geography: traffic from an unexpected country or city compared to your normal audience.
Narrow down the source
To exclude the bots without affecting real visitors, find out what they have in common:
-
Pages: which pages are targeted, for example a single entry page with no clear reason.
-
Browser and operating system: which ones the bot uses.
-
Location: which city or country the traffic comes from.
-
Network: which organization or ISP it comes from.
Exclude suspicious traffic
Most of the time, you can exclude bot traffic with a Data Management exclusion rule that combines several criteria. This works best when the bot uses an old or unusual browser version, or comes from an unusual city (for example, a small US town when all your site traffic is in France). To create the rule, see Exclusions. If you can't use IP addresses, see How to exclude robot behaviour without IP address from Data Management?
The properties most often used are:
-
City: the city the visit comes from.
-
Organization: the connected organization or ISP.
-
User agent: the browser and device identifier sent with each hit.
Add properties such as operating system or device category to refine the rule and reduce the risk of excluding legitimate users.
Exclusion limits
-
No retroactive effect: exclusions apply only to events collected after the rule is created. See Will my Data Management rules be retroactive?
-
Historical data: to correct data that was already collected, contact Support to request a data regeneration. This is generally a paid service.
Overly broad rules, such as excluding an entire city or country, can remove legitimate traffic.