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

# CRM Tags

Les tags sont parfaits pour segmenter votre audience dans votre zone de contacts.

Pour créer un tag > Allez dans l'onglet Contacts > Sélectionnez l'icône de l'onglet comme indiqué ci-dessous.

<figure><img src="/files/OEhxzeGpkRR1IrAw3qE5" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/YMlBRsLPWtqJi1iqW6vX" alt=""><figcaption></figcaption></figure>

Une nouvelle fenêtre s'ouvre alors dans les paramètres des contacts

**Sélectionnez : Créer un nouveau TAG**.

<figure><img src="/files/psVEHgP9nGKleFAyPbtm" alt=""><figcaption></figcaption></figure>

**Créez maintenant votre nom de balise**

<figure><img src="/files/BMIvof1hHfhL1k4bjYbl" alt=""><figcaption></figcaption></figure>

Et voilà, votre balise est maintenant créée. Vous pouvez également créer des tags sur divers widgets tels que les caisses, les formulaires, les automatismes de déclenchement et bien plus encore. Pour accélérer le processus de création de tags.


---

# 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.netsimpler.io/netsimpler/crm/crm-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.