> 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/consent-management-platform-cmp/vendor-lists/determine-purposes-for-vendors.md).

# Determine purposes for vendors

To determine which purposes should be linked with your vendors, you should consider the following points:

1. Understand the Nature of the Vendor: Identify what services the vendor provides and what data they collect. 
2. Consult Legal and Compliance Teams to understand the regulatory requirements related to data processing activities for your specific case. 
3. Vendor's Privacy Policy: Review the privacy policy of the vendor. Often, vendors will specify the purposes for which they process data.
4. Didomi Console: you can access the "Vendors & Purposes" section. Here, you have the option to select our default vendors, which come with purposes generally declared by the vendors themselves. 
5. Custom Purposes: If the predefined purposes do not fully cover the activities of your vendors, you might consider creating custom purposes. This can be done in the Didomi Console, where you can define and link these custom purposes to the appropriate vendors.


---

# 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/consent-management-platform-cmp/vendor-lists/determine-purposes-for-vendors.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.