> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/ux-methods/discovery/behavioural-analytics.md).

# Behavioural Analytics

Behavioural analytics is a branch of analytics that focuses on understanding and analysing user behaviours and interactions within a digital platform or system.&#x20;

It involves tracking and examining user actions, such as clicks, navigation paths, transactions, and engagement patterns, to gain insights into user preferences, motivations, and decision-making processes.&#x20;

By analysing these behavioural data points, organisations can make data-driven decisions, optimise user experiences, personalise content, and improve overall performance.&#x20;

Behavioural analytics provides valuable insights into user behaviour, allowing businesses to enhance their strategies, optimise conversions, and deliver targeted experiences that align with user needs and goals.


---

# 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://www.designreference.xyz/ux-methods/discovery/behavioural-analytics.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.
