> ## 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.

# Communication topics

> Consent per theme: Newsletter, Promotions, and a link for people to choose what they want.

<Tip>
  A **topic** is a **subject** the person agrees to receive. It is **not** a tag (label) or a segment (filter). **Tags** mark; **topics** record consent per theme.
</Tip>

## What is a topic?

A **marketing theme** in the workspace, e.g. **Newsletter**, **Promotions**, **Launches**. A person can accept one and decline another.

Analogy: general opt-in asks "can I send marketing?". A **topic** asks **which shelf** interests them.

## Topic × tag × segment

|              | **Topic**                              | **Tag**                     | **Segment**                               |
| ------------ | -------------------------------------- | --------------------------- | ----------------------------------------- |
| Purpose      | Consent per **theme**                  | Manual **label** on file    | **Saved filter** (who is in the audience) |
| Example      | "Accepts Newsletter"                   | `VIP`, `Lead`               | "VIP tag + subscribed to Promotions"      |
| In campaigns | **MARKETING** template linked to topic | `type: tag` rule in segment | Campaign audience                         |

## When to use?

Great for **multiple marketing content types** and **MARKETING** category templates. **Transactional** messages (order, password) do not follow the same topic rules.

## How it works in practice

1. **Audience → Topics → New**, name, stable **slug**, description, default opt-in for new contacts
2. On **marketing template**, link the correct **topic**
3. On send or campaign, system checks general marketing **and** topic subscription
4. Generate **preferences link** on contact record (\~90 day token)
5. In email, use **`{{preferences_link}}`**
6. **MARKETING** templates also send **RFC 8058** headers. See [One-click unsubscribe](/en/emails-api/como-funciona/one-click-unsubscribe-rfc-8058)

<Warning>
  Keep **slug** stable once campaigns depend on it.
</Warning>

## Relation to `receiveMarketing`

* Contact usually needs **`receiveMarketing: true`**
* **MARKETING** template with topic requires subscription to that theme
* Those who fail the check **do not enter** the campaign queue, no per-person error

## In the API

Scopes `topics:read`, `topics:create`, `topics:update`, `topics:delete`. Routes under **Topics** in the API reference.

## Next steps

* [Audience segments](/en/contacts-api/como-funciona/segmentos-na-audiencia): audiences with `topic` rules
* [Dashboard campaigns](/en/contacts-api/como-funciona/campanhas-no-painel)
* [Introduction](/en/contacts-api/como-funciona/introducao)