The per-category consent with custom categories feature gives users granular control on which categories of cookies or other identifiers to give consent to:
- Strictly necessary (purpose id 1): activated (no consent required)
- Basic interactions & functionalities (purpose id 2): blocked
- Experience enhancement (purpose id 3): blocked
- Measurement (purpose id 4): blocked
- Targeting & Advertising (purpose id 5): blocked
- Scripts with purposes 2 and 5: blocked
The categories are displayed along with a short description and toggle so that users can either grant or reject consent for the particular processing purpose.
💡 Click on the "Learn more and customize" button to see this feature in action. Grant consent to the "Experience enhancement" category to release the YouTube and Twitter scripts below.
The categories displayed in the modal are automatically detected, but in this demo they've been customized by using the purposes parameter.
Here's an example of how it works: if you're using all 5 categories (and you're not using an iubenda cookie policy), you'll need to specify "purposes": "1, 2, 3, 4, 5", if you don't use "Targeting & Advertising" scripts (id 5) you can simply specify "purposes": "1, 2, 3, 4" and so on. To implement, add the perPurposeConsent parameter to your Cookie Solution code snippet and set to true.
Alternatively, you can also activate this functionality through the configurator (GDPR > Edit > Manual configuration > Offer granular control with per-category consent > Custom):
- Remember to use your own credentials from your iubenda account
- This is a sample for pure demonstrative purposes, no consents are saved (result of
_iub.csConfiguration.skipSaveConsent = true). Just refresh the page to make the cookie banner reappear. - If you don't see the cookie banner on your first visit, you may have a consent cookie saved from another demo: reset consent and refresh the page to make the cookie banner reappear.
Block cookies prior to consent
To demonstrate the cookie blocking feature, we've embed a YouTube video:
And a Twitter follow button:
Follow @iubendaBoth scripts are blocked through manual tagging, one of the methods available with the Cookie Solution.
Since both the YouTube video widget and the Twitter follow button are part of the Experience enhancement purpose (id 3), we've added data-iub-purposes="3" to their scripts so that the Cookie Solution can properly identify them for release.
Click on the Accept button - or just activate the "Experience enhancement" toggle - to release these scripts (refresh the page to return to the starting point).
Learn more
Read our advanced guide for more information about per-category consent (including manual tagging and Google Tag Manager blocking methods).
Other helpful resources: