> 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/re-collect-consent.md).
# Re-collect consent
{% hint style="warning" %}
**It is not possible to re-collect consent in AMP format, since cookies are stored by Google.**
{% endhint %}
If you wish to re-collect consent after adding a new vendor/purpose or IAB vendor, please follow these steps:
#### **CASE 1: Adding a new custom vendor and/or purpose**
{% hint style="info" %}
This section applies to all notices using IAB TCF integration or not.
{% endhint %}
**✅ STEP 1**
**Add a new custom vendor to your banner**
1. Go to your consent notice in the **Consent Notices** (**1**) section.
2. Make sure you are in step **1. Regulations** and in the **Regulations** sub-table. (**2**)
3. Click on **Edit** under one of the regulations applied to your notice, in order to access the list of vendors and purposes for this regulation. (**3**)
4. In the Vendors table, search and select the custom vendor (i.e., non-IAB vendor) you wish to add.
5. Click on **Save**.
{% hint style="info" %}
You can also create a new custom vendor directly from the notice configuration flow or in the Data Manager section.
{% endhint %}
**If you want to add a new purpose to your existing vendor:**
1. Go to the **Data Manager** section.
2. Click the **Purposes** tab.
3. Click on **Add purpose +**.\
4. Name your purpose.
5. Describe your purpose.
6. Click on **Save**.
7. **Link your purpose to an existing vendor.**
**✅ STEP 2 (for the consent recollection)**
1. Go to step **1. Regulations** and the **Consent settings** tab.
2. Scroll to the **Consent re-collection** section.
3. Type "0" in the **window for recollecting consent** box, as shown below :
4. Click on **Save & continue**.
5. Publish your notice in step **3. Publish**.
#### **CASE 2: Adding a new IAB vendor**
{% hint style="warning" %}
This section is only valid if you are not using the IAB integration with all vendors.
{% endhint %}
**✅ STEP 1**
1. Go to your notice in the **Consent Notices** (**1**) section.
2. Make sure you are in step **1. Regulations** and in the **Regulations** sub-table. (**2**)
3. Click on **Edit** under one of the regulations applied to your notice, in order to access the list of vendors and purposes for this regulation. (**3**)
4. In the Vendors table, select the IAB vendor you wish to add.
5. Click on **Save**.
**✅ STEP 2**
1. Go to step **1. Regulations** and the **Consent settings** tab.
2. Scroll to the **Consent re-collection** section.
3. Switch on the toggle and enter the date desired for re-collection in the **Recollect consent after a date** section, as shown below.
4. Click on **Save & continue**.
5. Publish your notice in step **3. Publish**.
If you do not select a date for re-collection the notice will not be redisplayed and the newly added vendor will be considered as “**denied**”.
---
# 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/re-collect-consent.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.
