> ## Documentation Index
> Fetch the complete documentation index at: https://docs.notifique.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Tags in the audience

> Reusable labels to mark contacts: Lead, VIP, Customer — and use them in segments and campaigns.

<Tip>
  A **tag** is a **label** on the contact file. It is **not** a topic (consent) or a segment (filter). **Tags** mark; **segments** combine tags with other rules.
</Tip>

## What is a tag?

A **reusable label** in the workspace, e.g. `Lead`, `VIP`, `Customer`, `Black Friday`. Create it once and apply it to as many contacts as you need.

Analogy: a **colored sticker** on the customer folder. The tag does not change who the person is — it helps you **find and group** later.

## Tag × topic × segment

|                | **Tag**                       | **Topic**                        | **Segment**                               |
| -------------- | ----------------------------- | -------------------------------- | ----------------------------------------- |
| Purpose        | **Mark** manually             | **Consent** per theme            | **Saved filter** (who is in the audience) |
| Example        | `VIP`, `Hot lead`             | "Accepts Newsletter"             | "VIP tag + accepts marketing"             |
| Where it shows | Contact file, import          | MARKETING template + preferences | Campaign audience                         |
| In the API     | `tags:*`, `tagIds` on contact | `topics:*`, `topic` rule         | `segments:*`, `type: tag` rule            |

## When to use?

Great for **classifying leads**, **marking active customers**, **tracking source** (`Website`, `Store`), or **internal status** (`Awaiting reply`). For **legal marketing opt-in per theme**, use [topics](/en/contacts-api/como-funciona/topicos-de-comunicacao).

## How it works in practice

1. **Audience → Tags → New**, pick a short clear name (`VIP`, `Lead`)
2. On the **contact file** or during import, attach one or more tags
3. Build a **segment** with a `type: tag` rule to filter who has that label
4. Use the segment as the **audience** of a campaign

<Note>
  A tag **does not block sending** on its own. A contact tagged `VIP` still must pass marketing rules and suppressions at send time.
</Note>

## Tags in segments

Example: VIP contacts who accept marketing:

```json theme={null}
{
  "version": 1,
  "match": "all",
  "rules": [
    { "type": "tag", "tagId": "YOUR_VIP_TAG_UUID" },
    { "type": "receiveMarketing", "value": true }
  ]
}
```

Combine with `property`, `contactField`, or `topic` — see [Segments in the audience](/en/contacts-api/como-funciona/segmentos-na-audiencia).

## In the API

Scopes `tags:read`, `tags:create`, `tags:update`, `tags:delete`. Routes in the **Tags** group of the API reference.

On the contact, send `tagIds` on create/patch or use workspace tag routes.

## Common mistakes

* Confusing **tag** with **topic** — tag is an internal label; topic is consent per subject
* Expecting a tag to replace **suppression** — do-not-contact identities stay on the [suppressions list](/en/suppressions-api/como-funciona/introducao)
* `tagId` from another workspace in a segment → validation error

## Next steps

* [Segments in the audience](/en/contacts-api/como-funciona/segmentos-na-audiencia): build audiences with `tag` rules
* [Communication topics](/en/contacts-api/como-funciona/topicos-de-comunicacao): consent per theme
* [Campaigns in the panel](/en/contacts-api/como-funciona/campanhas-no-painel): batch sends
* [Introduction](/en/contacts-api/como-funciona/introducao): concept map