Microsoft Clarity groups bot activity by page type

What changed

Teams can create categories or extend existing ones, with custom rules taking priority over automatic classifications. Review the groupings to see which parts of a site attract bots and correct misclassified paths. This is a bot-analysis feature; it does not by itself diagnose ad fraud or alter campaign conversion reporting.

Inspect several URLs from each automatically assigned class. Add explicit rules where the same URL pattern contains materially different page purposes, and check rule priority before relying on a dashboard. Compare the resulting classes with the questions the team needs to answer about content discovery and infrastructure load.

Page classes are most useful when they align with the decisions the team needs to make. Grouping every product URL together may be sufficient for a high-level review, but it may hide differences between available products, discontinued products and editorial buying advice. The source’s support for URL rules gives teams a way to make the classification more meaningful without interpreting every page manually.

Before building a recurring report, sample the pages assigned to each class and review exceptions with the site owner. Record the intended meaning of a class so that later URL changes do not quietly alter the report. A rise in bot activity on a page type is an observation about access, not direct evidence of a conversion or a recommendation. Connect it to a specific question about discoverability or site operations before using it to justify content or media investment.

Why it matters for advertisers

Page-level grouping can make bot activity easier to investigate, especially on sites mixing product pages, editorial content and support. The grouping remains a classification aid rather than evidence that every automated visit has the same commercial value.