- Remember to use your own credentials from your iubenda account
- Be sure to open your browser in a private/incognito window
- 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
This is one of the possible setups of our Cookie Solution: it's essentially the default configuration except for consent on continued browsing (disabled here), and the addition of the reject button, per-category consent and IAB Transparency and Consent Framework.
While IAB TCF allows you to gain consent before showing personalized ads (as required by major advertising networks, more information in the dedicated demo), per-category consent 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. The categories displayed in the modal are automatically detected, but they can also be customized by using the purposes parameter or through the configurator (see the dedicated demo).
💡 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.
On the configurator:
More options available in the Advanced View.
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: