> For the complete documentation index, see [llms.txt](https://documentation.freshpaint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.freshpaint.io/readme/bot-blocking.md).

# Bot Blocking

When bot blocking is enabled, Freshpaint automatically classifies each incoming event and prevents bot traffic from being delivered to destinations or counting towards MTUs. Bot blocking is not enabled by default.

## 1. Functionality

Freshpaint applies a `$source_classification` property to every event at ingestion. This property indicates whether the event originated from a known bot or from regular traffic. It is present on all events regardless of whether bot blocking is enabled for the account.

<table><thead><tr><th width="162">Classification</th><th width="532">Description</th></tr></thead><tbody><tr><td><code>UNCLASSIFIED</code></td><td>Traffic that does not match any known bot pattern. This typically represents normal user activity.</td></tr><tr><td><code>KNOWN_BOT</code></td><td>Traffic that matches known user agents for web crawlers such as Googlebot, Applebot, Bingbot, and others.</td></tr><tr><td><code>AWS_BOT</code></td><td>Traffic that matches a specific bot pattern observed on AWS infrastructure, identified by a combination of browser characteristics and source IP address.</td></tr></tbody></table>

When bot blocking is not enabled, all events, including those classified as bots, are delivered to destinations normally.

When bot blocking is active on an account:

* Events with a `$source_classification` of `KNOWN_BOT` or `AWS_BOT` are **not delivered** to any destination.
* Blocked bot events do **not count** towards MTU usage.
* Blocked events still appear in [Traces](/admin-panel/investigate-testing-and-debugging/traces.md) with a **Bot Detected** status for debugging purposes.

### Viewing Source Classifications

In [Traces](/admin-panel/investigate-testing-and-debugging/traces.md), events classified as bots display a **Bot Detected** status. Use the status filter to isolate these events.

<figure><img src="/files/wLpIIDV7hk2Y2FOf2hi4" alt="&#x22;Event Verification&#x22; library with &#x22;bot detected&#x22; status checked. Shows traces with status &#x22;bot detected&#x22;."><figcaption></figcaption></figure>

## 3. Enable Bot Blocking

To request bot blocking, contact a Freshpaint representative or email **<support@freshpaint.io>**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.freshpaint.io/readme/bot-blocking.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.