> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/faq/debugging-monitoring/invalidate-or-renew-consent-by-cmp.md).

# Invalidate or renew consent by CMP

AdPage detects **expired consent** when a visitor sends marketing data, such as a purchase, but the related cookie was stored before their consent was recorded. The two events cannot be linked. This counts as a missed match.

The solution is to require returning visitors to provide consent again. This creates a new cookie that can be linked.

Follow the steps for your CMP below.

***

### Cookiebot

1. Sign in to [admin.cookiebot.com](http://admin.cookiebot.com/).
2. Go to **Domains & Aliases** → [**Manage your domain groups**](https://admin.cookiebot.com/domain-groups).
3. Click the **>** icon beside the domain group.
4. Click **Renew user consents** in the lower-right corner.
5. Confirm with **Renew**.

Existing consents remain in the consent log. Returning visitors see the banner again when they revisit the site.

🔗 [Cookiebot documentation](https://support.cookiebot.com/hc/en-us/articles/360004553893-Renew-existing-user-consents-in-the-Cookiebot-Admin)

***

### Usercentrics

1. Sign in to the [Usercentrics Admin Interface](https://app.usercentrics.eu/).
2. Go to **Configuration** → **CMP Settings**.
3. Find the **Manual Resurface** section.
4. Enable the setting. The banner immediately reappears for all existing users.

The same screen displays the last manual resurface date.

🔗 [Usercentrics documentation](https://support.usercentrics.com/hc/en-us/articles/18732083948828-Framework-specific-banner-resurfaces-and-common-resurface-situations)

***

### CookieYes

1. Sign in to [app.cookieyes.com](http://app.cookieyes.com/).
2. Go to **Dashboard** → **Site Settings**.
3. Scroll to **Renew User Consent**.
4. Click **Renew Now**.
5. Confirm with **Renew Consent**.

After confirmation, the banner reappears for users who previously provided consent.

🔗 [CookieYes documentation](https://www.cookieyes.com/documentation/renew-user-consent/)

***

### Consent Studio

1. Sign in to the [Consent Studio dashboard](https://consent.studio/app).
2. Select the correct domain.
3. Go to **Domain Settings** using the navigation gear icon.
4. Open the **Danger Zone** tab.
5. Choose a future date. Visitors who consented before that date see the banner again.
6. Click **Save & Publish**.

Note: The date must be in the future. It uses the **Europe/Amsterdam** time zone. Remove the date and save again to undo this setting.

🔗 [Consent Studio documentation](https://learn.consent.studio/en/articles/6422074-invalidating-consent-before-a-given-date)

***

### Complianz for WordPress

Complianz uses a **cookie version number**. Increasing it makes the banner reappear for returning visitors.

1. In WordPress, go to **Complianz** → **Cookie policy**.
2. Scroll to **Cookie notice version** or **Revision date**.
3. Increase the version number or change the date.
4. Save the changes.

Visitors who consented under a lower version number see the banner again.

🔗 [Complianz support](https://complianz.io/support/)

***

### Borlabs Cookie for WordPress

Borlabs provides an **Update Cookie Version & Force Re-Selection** feature.

1. In WordPress, go to **Borlabs Cookie** → **Settings**.
2. Find **Cookie Version** or **Force Re-Selection**.
3. Increase the version number.
4. Save the changes.

Visitors who consented under the previous version must choose again. Their previous choice is not preselected.

🔗 [Borlabs Cookie documentation](https://borlabs.io/support/)

***

### Other CMPs

Most CMPs support consent invalidation. The feature names vary:

| CMP                                              | Setting to look for                   |
| ------------------------------------------------ | ------------------------------------- |
| OneTrust                                         | “Re-consent” or “Consent expiry”      |
| Axeptio                                          | “Invalider les consentements”         |
| iubenda                                          | **Cookie Solution** → version setting |
| Didomi                                           | “Consent reset” or its API            |
| [Consentmanager.net](http://consentmanager.net/) | “Cookie Version”                      |

Is your CMP not listed? Search its settings for *renew*, *reset*, *invalidate*, *version*, or *force re-consent*. You can also contact your CMP’s support team.


---

# 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.adpage.io/faq/debugging-monitoring/invalidate-or-renew-consent-by-cmp.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.