> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/accounts/tags.md).

# Tags

Manually monitoring new developer activity in each account or checking for new accounts added to a segment can be time-consuming.

Reo.Dev simplifies this process by using **pre-defined Tags** to highlight new activity in any account or segment, ensuring you're always equipped with the latest intel.

Pre-defined tags in Reo.Dev include:

* **CRM Stage** - When an account moves from one CRM stage to another (e.g., from In-market to Discovery, or any other stage change).
* **Dev Funnel** - when an account changes stage in Developer Funnel
* **Surge**: When the [Account Activity Score](/accounts/account-activity-score.md) (AAS) for an account increases by more than 40 in the last 7 days. A surge status lasts for 7 days unless the activity continues to increase.
* **New**: When a deanonymised developer is added to an account
* **New Activity**: When a developer does a new activity in an account
* **New account:** When a new account is added in the last 24 hours. This tag is visible only for 24 hours from the day it's added. 
* **New lead:** When a new developer/buyer is added to a developer/buyer segment respectively. This tag is visible only for 24 hours from the day it's added. 
* **Buyer**: When a developer we show might have the authority to make purchase decision.

**A few things to note here:** 

* Pre-defined tags are not customizable 
* Pre-defined tags are not synced into your CRM 
* Because  pre-defined tags are not synced to CRM, they can't be used in workflows running in your CRM. 


---

# 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.reo.dev/accounts/tags.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.