> 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/retrieve-vendor-id.md).

# Retrieve vendor ID

To find your vendor ID for tag conditionality, you can follow these steps in the Didomi console:

1. **Access Consent Notice Settings**: Navigate to the section where you manage your consent notices and select the relevant notice.
2. **Edit Vendors and Purposes**: Within the settings, locate the section for editing vendors and their purposes.
3. **Identify Vendor API ID**: Find each vendor’s unique API ID in the vendor list, necessary for configuring tag conditions in tools like Google Tag Manager.
4. **Copy Vendor API ID**: You can find the API ID in the 2nd column and use this ID to set conditions on tags based on user consent for each specific vendor.

{% hint style="warning" %}
Note that since February 2024, the API ID has taken precedence over the IAB/SDK ID in the console, with a view to multi-regulation harmonization. If you were a Didomi customer before this date you may still use this IAB/SDK ID column. You don't have to replace it by the API ID unless it is not only for GDPR usage.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.didomi.io/consent-management-platform-cmp/consent-notices/retrieve-vendor-id.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.