> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/bot-studio/actions/customer-management/how-to-set-tags.md).

# How to Set Tags

Learn to set Tags on DoubleTick to segment customers, personalize interactions, and automate categorization for better engagement and targeted marketing.

In the realm of automated customer interactions, effective management of customer data is paramount. One powerful tool for enhancing customer engagement and personalization within chatbot flows is the "Set Tags" action. This action allows businesses to assign specific tags to customers based on their interactions, preferences, or other relevant criteria. Let's delve into how this action works with a practical example.

> [<mark style="color:green;">**Click to Learn; How to Create Tags?**</mark>](/chat-management/find-and-organise-chats/how-to-use-tags.md)

### **Benefits of Set Tags Action:**

1. **Segmentation:** Tags enable you to segment your audience based on their interests, behaviors, or demographics, allowing for targeted marketing efforts.
2. **Personalization:** With tagged customer profiles, you can deliver personalized experiences, leading to increased engagement and satisfaction.
3. **Automation:** The Set Tags action automates the process of categorizing customers, saving time and resources compared to manual tagging.

### **Example Scenario:**

Imagine you're managing a virtual clothing store's chatbot. You want to categorize customers based on their clothing preferences to tailor your marketing efforts accordingly. Here's how you can utilize the "Set Tags" action:

1. **Customer Interaction:** A customer interacts with your chatbot, expressing an interest in men's fashion.
2. **Set Tags Action:** After the interaction, you implement the "**Set Tags**" action in your bot flow. You configure it to add the tag "Men's Fashion Enthusiast" to customers who express an interest in men's clothing.
3. **Tag Application:** Once the customer expresses their preference, the "Set Tags" action dynamically adds the "Men's Fashion Enthusiast" tag to their profile within your system.
4. **Personalized Engagement:** With the tag assigned, you can now personalize the customer's experience. For instance, you can send them targeted promotions, new arrivals in men's fashion, or relevant blog posts.

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FSNtqcVQ0GwyYm2bszCGh%2Ftags%20(1).gif?alt=media&amp;token=b4fcc116-fe05-49ae-8a41-1fc6783cc9f2" alt=""><figcaption></figcaption></figure>

***


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.doubletick.io/bot-studio/actions/customer-management/how-to-set-tags.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
