> 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/consent-notices/add-vendors-to-consent-notice.md). # Add vendors to consent notice When you get to the **VENDORS & PURPOSES** step of the creation of your cookie consent notice, you have to add every vendor dropping cookies on your website, to make them appear in your Consent Notice in the partners view. There are two ways of doing so thanks to our compliance report: * By [adding all vendors](/tracker-and-vendor-discovery/tracker-and-vendor-discovery-results/tracker-and-vendor-discovery-results-overview.md#vendors) that you see when you launch your compliance report on the Didomi console. * By [exporting the vendors](/tracker-and-vendor-discovery/tracker-and-vendor-discovery-results/download-tracker-and-vendor-discovery.md) of your compliance report and adding all vendors present in the file. Verify internally and frequently that your vendor list is comprehensive. The compliance report is a tool for informational purposes and it does not completely assure your compliance. --- # 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/consent-notices/add-vendors-to-consent-notice.md?ask=&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.