Config Version and Re-consent

Config Version controls when returning users are prompted to re-consent after you make changes to your consent configuration.

How It Works

Each time you publish your project, the CMP stores a config version number in the user's consent cookie. When a returning user visits your site, the CMP compares the stored version with the current version. If they differ, the consent banner is shown again immediately, regardless of other settings.

When Re-consent Happens Automatically

Even without a manual config version change, the CMP will automatically prompt users to re-consent in the following cases:

• IAB Global Vendor List (GVL) auto-update: If you have enabled auto-update for the vendor list in your dashboard, the vendor list is updated automatically when the IAB publishes a new GVL version. When new vendors or purposes are added, users who have not consented to them will be prompted to re-consent.
• Consent string expiry: IAB TCF consent strings have a maximum validity period (typically 13 months). When the consent string expires, the user must re-consent.
• Browser cookies cleared: If the user clears their cookies or uses a new browser or device, no prior consent exists and the banner is shown.

Re-consent Interval

The Re-consent Interval setting controls the minimum number of days before a user is asked for consent again when the vendor list auto-updates. This prevents users from being prompted too frequently due to vendor list changes.

Available options: 0, 7, 30, 60, 90, 120, or 150 days.

• 0 days: re-prompt immediately whenever the vendor list updates.
• 30 days (recommended): users will not see the banner again within 30 days of their last consent, even if the vendor list updates.
• 90+ days: reduces banner fatigue for users but delays consent updates.

Note: Config version changes always override the Re-consent Interval. If the config version changes, users are re-prompted immediately regardless of the interval setting. The interval only applies to automatic vendor list updates.

To configure:

1. Go to your project in the dashboard.
2. On the Settings tab, find Re-consent Interval in the advanced settings section.
3. Select the minimum number of days.

Auto Config Version

When Auto Config Version is enabled in your project settings, the config version increments automatically each time you publish changes. This means any published change will immediately prompt returning users to re-consent.

If disabled, you can manually set the config version number. Only increment it when you want to force re-consent across all users.

Setting Up Config Version

1. Go to your project in the dashboard.
2. On the Settings tab, find Config Version under the install section.
3. Toggle Auto Config Version to enable automatic versioning.
4. Or set a manual version number and increment it when you want to trigger re-consent.

Priority

1. Config version change - highest priority, always triggers re-consent immediately.
2. Consent string expiry - triggers re-consent after the consent validity period.
3. Vendor list auto-update - triggers re-consent subject to the Re-consent Interval setting.

Important Notes

• Users who consented before config versioning was introduced will not be re-prompted unless you explicitly increment the version.
• Re-consent applies to all consent types (GDPR, CCPA, GPP, TCF Canada).
• The config version is stored in the user's consent cookie alongside their consent string.