> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/data-manager/vendors/add-purpose-to-vendor.md).

# Add purpose to vendor

{% hint style="success" %}
**Access Type**: Data Manager - Editor
{% endhint %}

A [purpose](/data-manager/purposes.md) describes the reason your organization or its vendors is collecting the end-user's data and how your organization processes that data. In this article, we will cover how to add a purpose (IAB, Global, Custom) to any vendor within your organization's Data Manager.&#x20;

Click **Data Manager** in the left-hand panel and select the **Vendors** tab on the subsequent page.&#x20;

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FIPxM6WqEj9wRpcBd2GTd%2FScreenshot%202026-03-16%20at%201.13.17%E2%80%AFPM.png?alt=media&amp;token=46b68d90-a2f4-4275-92ce-32d6be5c1e15" alt="" width="563"><figcaption></figcaption></figure>

Navigate to a vendor on the subsequent list and click **Edit** inline with the vendor name.&#x20;

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FoXLn6GelyTTEuVtzvOc2%2FScreenshot_2026-03-17_at_1_03_18%E2%80%AFPM.jpg?alt=media&amp;token=72dc36b3-dc2d-49bd-a9f9-bf527612cf3f" alt="" width="563"><figcaption></figcaption></figure>

Purposes added to a vendor require a legal basis which define whether:

<table data-header-hidden><thead><tr><th width="309"></th><th></th></tr></thead><tbody><tr><td>Opt-in (based on consent)</td><td>The end-user needs to explicitly consent to the data processing involved with the stated purpose</td></tr><tr><td>Opt-out (based on legitimate interest)</td><td>The end-user is by default opted-into the data processing involved with the stated purpose and they have the option to reject the purpose. This processing must be legitimate, necessary, and not prejudice the rights and interests of individuals.</td></tr></tbody></table>

From the vendor configuration page, navigate to the respective **opt-in purposes** or **opt-out purposes** drop-down menu and select the desired purpose to add to the vendor.

{% hint style="warning" %}
**Note**: For organization's who plan to utilize the vendor in the context of a consent notice with an IAB TCF 2.3 integration, please be aware that the following purposes can only be used with an opt-in (based on consent) legal basis:

* (1) Store and/or access information on a device
* (3) Create a personalized ads profile
* (4) Select personalized ads
* (5) Create a personalized content profile
* (6) Select personalized content
  {% endhint %}

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FbzFA3ovSZQDoRNNiwgZY%2FScreenshot%202026-03-17%20at%202.18.55%E2%80%AFPM.png?alt=media&amp;token=4a630166-ed89-4119-8b6a-30d573d1bcbf" alt="" width="375"><figcaption></figcaption></figure>

Click **Save** when finished to confirm the addition(s). The purpose will be added to the vendor and listed in the appropriate legal basis column for the vendor.

<figure><img src="https://1825037175-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNDxbAdc00ce6bH5u1urh%2Fuploads%2FE4cb8XCd9yBfZwoizYGD%2FScreenshot_2026-03-17_at_2_42_12%E2%80%AFPM.jpg?alt=media&amp;token=9731a097-6445-4e04-9d6c-16b8e22e632b" alt="" width="563"><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://docs.didomi.io/data-manager/vendors/add-purpose-to-vendor.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.
