How to show cookie list into banner.

Hi @masajeintegrativo,

As this functionality is not necessary on the banner but is available on the cookie policy, we don’t have a solution for this. There’s also no way, for now, to use the shortcode and split it into parts for every category.

Within the laws and guidelines, we try to keep the cookie banner as simple as possible for website visitors to read and understand. Adding a cookie list will, in my opinion, complicate matters with more jargon and technical information. For anyone interested a cookie policy is provided.

We could add this to our feature request and see if we can add a custom implementation for anyone who feels otherwise,

Let me know if this works for you,
regards Aert

@aahulsebos
Hi Aert,

I ask for this function because I saw that my GRPD assessor suggest that is better to show the cookie information separately them by category.
And also I see that exist other pages that have this information into the banner, and for sure also into Cookie Policy page.
You can see one example in attached image.
https://www.dropbox.com/s/izn55lvgzagtn8c/Cookie%20list%20into%20banner%20category.png?dl=0

If is not possible now to split it into parts for every category, I will continue using the general list into the cookie policy page, but I will be gratefully if your team can study this option as as improvement for a near future.

Thanks a lot for all your support,

im interested too in this

Hi @iviadvagency and @masajeintegrativo

Wanted to give some extra background:

In Complianz the cookie policy page (for the US called the Opt-out preferences page) is considered to be the second layer of the banner. As @aahulsebos already explained we decided to offer more detailed information about cookies (including information about expiration and information about the vendor) on the second layer, and separated by the used services because research showed that in that way the visitors can really have a clear overview. A different question is why we decided to separate the cookies on that second layer based on services. The reason behind that is that we wanted to offer a future proof solution for the draft ePrivacy Regulation.
If that new ePrivacy Regulation will become mandatory for the EU in the coming years, the possibility to give consent based on needed services, and just-in-time notices, will become the dominating way of asking consent and giving information. For example, if a visitor only needs Youtube, a website should not ask for consent for all the other services that might also use cookies in the marketing/tracking categories. It should give the possibility to only choose Youtube. To already accommodate that new change in the law it is in our opinion better to list the cookie table based on the used services.

I just wanted to share this information with you and the community as background information, and want you to know that we are always open to new suggestions on this topic. This is why I invite you to make a feature request or to contribute with a Pull Request on our github page.

ok, ty for the explanation!

Hi Mathieu,
Thanks a lot for the explanation ??
Regards,