Dokumentation - we_cookie_consent 4.1.2 - English

Same as version 4.0.1. differs, however, in the following places:

The extension NO longer uses jQuery in the frontend.

To simplify matters, you can use the export function to export the created tags, triggers and variables from the services for GTM and then import them into the GTM container.
In addition, a variable called "we_consent_state" and a trigger called "cmp_we_cookie_consent_changed" are provided, which are required for using the CMP in Consent Mode 1 (Basic) and Consent Mode 2 (Advanced). This is used to notify the CMP of all changes to consent.

1. Storage folder: The ID of the data record folder is stored here. See point 2.4.2.
2. Privacy page: You must enter the UID of your privacy page in the Privacy page input field. See point 2.4.2.
3. Style Prefix: In the Style Prefix input field, you can adjust the positioning of the cookie banner.
   Input options:
   • Display at the bottom of the screen: klaro we_cookie_consent (default)
   • Display at the top of the screen: klaro we_cookie_consent notice--top
   • Display in the middle with the buttons below each other: klaro we_cookie_consent notice--center
   • Display in the center with the buttons below and next to each other: klaro we_cookie_consent notice--center--floated
   • Unstyled output without CSS: nostyle
4. Additonal Class: Here you can add an additional CSS class for the styling
5. Storage Method: Here you can set whether the user settings should be saved in a cookie or in the browser's local storage. (Default: Cookie)
6. Cookie Name: You can change the name of your consent cookie in the Cookie Name input field. This was designed for the use of different language versions with different services that are provided via directories and not via different top level domains.
7. Lifetime: In the Lifetime input field, you can specify the validity period of the cookie. After this time has expired, the user is asked to accept the cookies again. The default setting is 365 days.
8. State: In the State input field, you can set whether your cookies are preset to activated or deactivated in the cookie banner. Input options: false (default), true (not GDPR compliant!)
9. Must Consent: In the Must Consent input field, you can set whether users can use your website without interacting with the cookie banner. Input options: false (default), true (not GDPR compliant!)
10. Group Service: Here you can activate or deactivate the grouping of services into categories. The grouping is based on TYPO3 system categories.
11. Accept all: Here you can set whether all services are activated when the banner is clicked away without user action.
12. Hide Decline all: Here you can set whether the "Decline" button should be displayed. (The button is displayed by default)
13. Hide Learn more: Here you can set whether the "Edit settings" button should be displayed. (The button is displayed by default)
14. Cookie domain: Here you can configure whether the settings made are only valid for the current domain or also for subdomains.
15. Consent Mode Basic: The default settings for Google Consent Mode Basic can be activated here: With Google Consent Mode Basic, NO Consent Mode default settings are initially loaded for the consent types!
16. Consent Mode Advanced: The default settings for Google Consent Mode Advanced can be activated here: With Google Consent Mode Advanced, ALL Consent Mode default settings for the consent types are initially loaded with "Denied"! This makes it possible to model the data with Google Analytics, for example, without consent.
17. Cookie icon permanently available: You can use it to create a permanent output of the consent control on all pages (bottom left)
18. Icon field default: You can use it to store your own icon for the permanent output of the consent control
19. Icon field hover: You can use it to store your own icon in hover state for the permanent output of the consent control

IMPORTANT: Before using Google Consent Mode, please check how you are allowed to handle the data and which jurisdiction or company guidelines apply to you!

When using an integrated or individual service WITH Google Tag Manager (Google Tag Manager service), proceed as follows:

1. Activate the Consend Mode "Basic" or "Advanced" in the TYPOScript parameters
2. Navigate to the List module and select Cookie Consent in the page tree
3. Click on the edit icon of the corresponding Google service
4. In the Google Consent Mode tab, make the settings for the consent types in the event of consent
5. Click on Save
6. Download the GTM template (template.tpl) for we_cookie_consent from Github (https://github.com/websedit/gtm-template-typo3-we_cookie_consent-cmp) -> continue with step 7
   Or search for it directly in GTM under Templates -> Search in gallery -> Import tag template -> Search field: "TYPO3 we_cookie_consent CMP" and add it to the workspace -> continue with step 13
7. Switch to the Google Tag Manager interface (https://www.google.com/intl/de/tagmanager/)
8. Click on Templates in the left-hand area
9. Click on "New" in the "Tag templates" area on the right to create a new template
10. In the subsequent window, click on the three dots at the top right and select "Import"
11. Select the downloaded template.tpl file and click on "Open"
12. Finally, click on "Save" in the top right-hand corner of the template editor. The template is now imported.
13. Switch to Tags in the left-hand area
14. Create a new tag, give it the name "TYPO3 we_cookie_consent CMP" and select the template "TYPO3 we_cookie_consent CMP" in the tag configuration
15. Configure the setting options (Default consent settings, Wait for Update, Redact Ads Data, Enable URL passthrough, Cookie ID to check) according to your requirements.
    Important: You do not need to carry out any configuration. The template is structured in such a way that it is compatible with the default settings of the TYPO3 extension we_cookie_consent. Entries for the "Default consent settings" and "Cookie ID to check" are therefore not mandatory.
16. Set the value for "Wait for Update" to "500" ms. This is usually sufficient.
17. Assign the trigger "Consent Initialization - All Pages" to the new tag
18. Also assign the trigger "cmp_we_cookie_consent_changed" to the new tag using the "or" link
19. Then use the preview function of the Google Tag Manager to check extensively whether all services with the correct consent types are being rolled out and your tags are being fired in the right place.
20. Once all tests have been completed, you can publish the new tag via "Send"