> For the complete documentation index, see [llms.txt](https://cmp.docs.sirdata.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cmp.docs.sirdata.net/en/cmp-services/extra-vendorlist.md).

# Extra-vendorlist

Providers' in the Google AC ModeIntegrating natively the Sirdata CMP as a vendor enables you to collect a maximum of valid consents and ease the integration that will be operated by your partners equipped with the Sirdata CMP.

### How it works

When configuring Sirdata CMP, publishers can add their partners (vendors) to their vendorlist in order to collect a choice specifically for their purposes.

These vendors (companies) can be found in one of the 3 following lists :

* Vendors in the IAB Europe TCF
* "Provider" dans le Google AC Mode
* Extra Vendors in the list managed by Sirdata

![Purposes of Google Analytics](https://1869615683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUspPnkTFMlMDdGxvAb-1972196547%2Fuploads%2FjiX092GKlFnc8HApQilc%2Fliste%20des%20partenaires%20EN.png?alt=media\&token=188a05f7-03f3-4129-ba70-ffb6dcf6d2e7)

Being available in these lists enables the publisher to add your company to its CMP in one click.

This avoids the need to create customised purposes, for which it is necessary to :

* On the publisher side: contact you to make sure of the purposes and legal bases you use
* On your side: make sure that all your partner publishers are properly integrated

For everyone's peace of mind, we recommend to subscribe to this list in order to keep control of your processing by declaring your activities yourself and ensuring your integration in each site is exactly the same.

Therefore, this integration includes :

* A standardised integration with any website using Sirdata CMP
* The validity of the collected consent
* The compliancy with the GDPR requirements

**Example with the Google Analytics extra vendor :**

![Google Analytics purposes](https://1869615683-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MUspPnkTFMlMDdGxvAb-1972196547%2Fuploads%2FkXOjGpeb01PmEW7Zvfdu%2Fpurposes%20Google%20EN.png?alt=media\&token=2fd5ccaa-54e0-4a48-b816-b02847ce5d0a)

## Rates

* 50€ HT per month (annual commitment)

## Activation & integration request

Here is the [form ](https://docs.google.com/forms/d/e/1FAIpQLScNvnZUMisPDzPDh_Ixz6syZCmXMokL_3KDqfvQzCcH3fSFNA/viewform)to fill in.

As soon as we receive this information, Sirdata will create your 'vendor' form and support you to setting it up on your partner sites.


---

# 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://cmp.docs.sirdata.net/en/cmp-services/extra-vendorlist.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.