Installation

There is a dedicated configuration in GTM for the use of Cookiebot to a wider extent than in the case of installation by uploading the cookiebot script itself to the CMS

Additionally, this dedicated configuration takes into account the transfer of data by Google tools (Analytics and Ads) in accordance with the user's decisions regarding cookies.

The implementation process itself is not particularly complicated

Analytics

The use of a dedicated configuration provides significant opportunities in the analytical area to examine decisions made by users in the area of ​​cookies.

GTM after full configuration

1. It introduces new events that we can then send to external applications
   
   Importantly, the event responsible for the user's decisions in the Cookies area is triggered every time the user makes some changes.
   
   So we can monitor not only the decision after displaying the Cookiebot window with various options to choose from, but we can also monitor any updates made by the user
   
   However, since these are not events triggered by ONe, but only by Google Tag Manager, no user data is transferred, which makes it impossible to tell analytics which client made such a decision regarding Cookies.
   
   
2. New variables are introduced that we can send as event parameters, where we will provide analytics with information about users' precise choices - which cookies they consented to and which they did not.
   
   However, there is no event about which button he used to make a selection
   - whether he clicked "I agree to all"
   - have you selected all of them and clicked "Accept"
   
   We only see that he accepted them all
   
   3. New events also appear cookie_consent_update, which is called immediately after the user makes a decision in the Cookiebot window
   
   Additionally, this event is triggered every time the page loads (there is no such loading in ONe), which, according to Cookiebot, is a recommendation to connect other marketing scripts to this event. This cannot be entered in ONe, because this event is triggered only when the page is loaded, and ONe is an application and the platform is loaded only on the first entry.
   
   It will continue to run external scripts, e.g. Pixel Meta based on our PageView event, but with an additional condition based on user decisions in the cookies area
   
   This also means that by default the user has not consented and the first loading will be in the "no consent" condition, i.e. we will not launch the Pixel. The first moment when Pixel can be launched is to go to the first page after making a selection in the Cookiebot window and accepting marketing scripts.
   
   The same solution can be used for any other type of cookies: statistical, preferences,
   
   
   

Summary

Integration is not difficult and offers many configuration options, and for each subsequent script or event entered in the future, a condition can be introduced based on the user's decisions regarding Cookies and at the same time monitor the user's choices.


I am still looking for a solution to enter information into GA4 which user made which decisions.