> For the complete documentation index, see [llms.txt](https://docs.browsee.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.browsee.io/heatmaps/segmentation-in-heatmaps.md).
# Segmentation in Heatmaps
Heatmaps give you a visual way to analyze your page engagement. It gives you a visual data representation of mouse activities on your pages like click, scroll, and attention. You can read more about[ heatmaps here](https://docs.browsee.io/heatmaps/heatmaps).
### Segmentation in Heatmaps?
Ever wondered about whether users behave differently based on referrals, countries, or Ad campaigns?
Now you can segment your heatmaps based on various parameters. Suppose you are curious about how people behave on the page when they land via Google Ads vs when they land via Google search.
Just go to the heatmap and use the filter at the top right to filter as per your need as shown below
You can filter your heatmap on the basis of:
1. UTM Source
2. UTM Medium
3. UTM Campaign
4. Referral
5. Country
6. [User Attributes](https://docs.browsee.io/heatmaps/segmentation-in-heatmaps#segment-heatmaps-by-user-attributes)
Other than that, you can also filter your heatmaps on the basis of click types like:
1. Rage Clicks
2. Dead Clicks
#### **Segment Heatmaps by User Attributes**
You can send User Attributes (for example, paid/unpaid/trial user, project ID) to Browsee and can use those attributes to segment your heatmaps. [Check here](/integration/api-calls/identify-call.md) on how you can send your user attributes to Browsee.
Once, you have sent these attributes, you will see these attributes in the "Filter By" dropdown in your heatmaps as shown below. Here, we have sent project IDs in identify calls.
Segment Heatmaps by User Attributes
Check below on how you can segment Heatmaps by User Attributes:
How to Segment Heatmaps with User Attributes
\
**Caveats**
* You can not segment your Attention Maps as of now
---
# 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://docs.browsee.io/heatmaps/segmentation-in-heatmaps.md?ask=&goal=
```
`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.