> For the complete documentation index, see [llms.txt](https://docs.aisuru.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisuru.com/en/extensions/deep-thinking/analytics/researching-user-interests.md).

# Researching user interests

AIsuru lets you explore the interests of users who interact with your Agent through Deep Thinking. This **powerful analytics tool** helps you better understand your audience and personalize your engagement strategies.

### Accessing the feature

To access user interest research:

1. Open your Agent's management panel;
2. Select "Followers" from the side menu.

### Exploring individual interests

The "Users" page shows a table with the following information: Username, Email, and Actions.

To view a specific user's interests:

1. Find the desired user in the table;
2. Click the "Interests" link in the "Actions" column;
3. A pop-up window titled "Interests discussed by user \[username]" will appear.

🔍 In the pop-up window, you'll find:

* The **total number of interests** detected;
* A two-column table: "Interest" and "Weight".

**Note**: "Weight" indicates the relevance or frequency of the interest for that user.

### Overview of all interests

For a full picture of all users' interests:

1. On the "Users" page, click the "Interests" tab;
2. You'll be taken to a new page dedicated to overall interests.

On this page you'll find:

* The **total number of interests** detected;
* An "**Export**" button to download the data;
* A table with three columns: "Interest", "Weight", and "Actions".

### Features of the Interests page

1. **Detailed view**: the table shows all interests detected across users;
2. **Data export**: click "Export" to download a file with all interest data for offline analysis;
3. **Follower analysis by interest**:
   * In the "Actions" column, there's a "Followers" link for each interest;
   * Click "Followers" to see which users are interested in that specific topic.

### Tips for effective use

1. **Monitor regularly**: check the interests page periodically to identify new trends or changes in user preferences;
2. **Segmentation**: use interest data to create more precise and targeted audience segments;
3. **Content personalization**: tailor your Agent's messages based on the predominant interests of your users;
4. **Product development**: use interest insights to guide the development of new features or products.

"Researching user interests" is a **powerful tool** that helps you understand your audience better and make decisions based on concrete data. Make the most of this feature to create **more personalized and engaging experiences** for your users, improving your AI Agent's effectiveness and strengthening your connection with your audience.


---

# 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.aisuru.com/en/extensions/deep-thinking/analytics/researching-user-interests.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.