CookiePedia: the complete cookie library

Of course, you can easily do it.
You might need to activate a block of code following the consent expressed by visitors to your site.
Imagine, for example, that you want to activate a SCRIPT only if the visitor gives consent to a specific cookie. This could be useful, for instance, to display the Facebook like button on one of your posts only if the visitor consents to a cookie, and to hide the button if they don’t.
Doing this is very simple: define the cookie that will act as the trigger for the button. You can use one of your choosing or one already used for other purposes (as long as they are relevant to what you are managing).
In the cookie definition, under the “General data” section of the cookie, you will find the Content Activation Selector field.
Enter the name of the selector you want in this field — for our example, you can use FB_like_button.
On your page, you will have a script that inserts the Facebook button, something like this:
<script type="text/javascript" async>
codice
</script>
Now modify the first line of this code like this:
<script type="text/plain" CookieMan_Selector=FB_like_button async>
and leave everything else unchanged.
In this way, the SCRIPT will be activated only if the selected cookie receives consent from the visitor, and the button will remain invisible if consent is not given.

Further note: You can go even further. If you want, you can make it so another block of code is activated when the cookie does not receive consent.
In the example we saw, if the selected cookie does not receive consent, the Facebook like button is not displayed.
If you prefer, you can display something else instead of the button in this case — so the space doesn’t remain empty — or you could encourage the visitor to give consent with a message.
To do this with CookieMan, you don’t have to do anything special. You just need to insert in your page the
<script type="text/plain" CookieMan_Selector=FB_like_button_off async>
code
</script>
As you can see, we used the same selector you defined in the cookie, but with _off added: FB_like_button_off.
All scripts with this selector will be activated if the cookie is not accepted.

If you have enabled multiple languages on your site (learn more), you need to inform your visitors about cookies with all the details translated into the active languages.
CookieMan performs this check for you: every time you publish a new version, a verification is done on all the cookies on your site, and you will be notified in the notification center if any cookie is not correctly translated into all active languages.
You can then manage this by modifying the cookie tabs and adding the text for each cookie in all languages.

Yes, the database is constantly updated with information about cookies detected on the sites. This ensures compliant and uninterrupted management.

By inserting a new cookie manually or through self-learning, you will be able to access all the information about that cookie in CookiePedia.
For CookieMan all cookies must be fully described, so that there is no risk to the site owner.
If the self-learning activity detects a cookie that is not in CookiePedia, it will report it to you. You will then have the option of registering the cookie yourself, because perhaps it is a cookie created by you or your developers, or you can request it to be censored by CookieMan.
If it is a known cookie, from a commercial solution, CookieMan will register it for you, with all the necessary information, and you will find it complete in your site definition.