First, if you don't already have one for your website, you must set up Google Tag Manager according to the official documentation.
If you don't have any consent management yet, you will have to review each tag after Leckerli setup according to the official documentation. If you do not configure consent for a tag, the tag will fire anyway and could not follow user consent settings if they do not have Built-In Consent Checks. It's important to review all your tags, and choose between No additional consent required and Require additional consent for tag to fire.
- Go to the tag configuration panel, select Advanced Settings and Consent Settings.
- If the tag does not need any consent or has Built-In Consent Checks like Google Analytics: GA4 Configuration, you can select that no additional consent is required. With this option, the tag will fire anyway and could load script or even set a cookie; you must check the behavior of the tag to understand how it works. If the tag has Built-In Consent, that means it should follow user consent settings, could still load a script but must not set cookies not allowed by user. Depending on how the Built-In Consent was implemented in the tag, it could update its behavior after the user changes consent settings.
- You can also require additional consent for the tag to fire, and in this case the tag will not fire if the user did not allow the consent required. To be able to fire this tag after the user changes consent settings without wait on a new page load, have a look at trigger event usage below in this documentation.
First you have to install the tag template (not yet available in the template gallery, so you need to import it manually).
- Download the latest Leckerli Google Tag Template from GitHub.
- Select the Templates tab in your website's Google Tag Manager workspace.
- Click on the New button, select Import in the three-dot menu, and upload the template you downloaded previously.
- Review the code and permissions, then save the template.
Then you can add the tag and configure it.
- Select the Tags tab in your website's Google Tag Manager workspace.
- Click on the New button.
- Click on the Triggering block and select Consent Initialization - All Pages.
- Click on the Tag Configuration block and select Leckerli Cookie Banner in the Custom section.
- (Optional) Click on Tag permissions and review them.
- Set the leckerli settings according to the configuration section below and the Leckerli README. The field must be a valid JSON string and can have multiple lines. You should at least remove not required consent from the permissions array.
- (Optional) Change the default consent (this is the consent values before the user's consent settings are updated). The default is set to denied for all consents (ad_storage, analytics_storage, functionality_storage, personalization_storage, and security_storage).
- Click on the Save button and optionally choose another tag name.
If you need to fire a tag when the user's consent settings are updated, you can configure a trigger. Remember that tags that do not have required additional consent have already been fired and should not be fired again if you are not sure about what will happen. Tags that have Built-In Consent Checks have probably handled the user's consent update.
- Select the Triggers tab in your website's Google Tag Manager workspace.
- Click on the New button.
- Click on the Trigger Configuration block and select Custom Event in the Other section.
- Set the Event name value to
leckerliConsentUpdate. - Click on the Save button and set Leckerli Consent Update as trigger name.
Using the html[lang] attribute, a Trigger and a Tag dedicated for each language can be created.
- Create a Custom variable type DOM element with "Element selector" : html and "Attribute name": lang
- For each language
- Create a Trigger type "Consent Initialization" which fire only on your custom variable = your language code
- Create a Tag type "Leckerli Cookie Banner" with json configuration according to your language strings
{
"banner": {
"title": "Wir respektieren Ihre Privatsphäre.",
"description": "Wir verwenden Cookies, um Ihr Surf-Erlebnis zu verbessern, personalisierte Anzeigen oder Inhalte zu schalten und unseren Verkehr zu analysieren. Durch Klicken auf „Alles akzeptieren“ stimmen Sie unserer Verwendung von Cookies zu.",
"accept": "Alles akzeptieren",
"reject": "Alles ablehnen",
"customise": "Anpassen",
"customiseDescription": "Beim Surfen im Internet werden Daten, meist Cookies, auf Ihrem Gerät gespeichert oder abgerufen. Diese dienen hauptsächlich der Funktionalität der Website und können auch für Statistik, Sicherheit, Überwachung und Marketing genutzt werden. Obwohl sie Sie meist nicht direkt identifizieren, ermöglichen sie ein personalisiertes Erlebnis. Sie können Ihre Cookie-Präferenzen anpassen, aber die Ablehnung bestimmter Cookies kann Ihr Surferlebnis beeinträchtigen.",
"save": "Speichern",
"settings": [
{
"slug": "analytics_storage",
"title": "Google Analytics",
"description": "Google Analytics ermöglicht es, das Verhalten von Website-Besuchern zu messen und zu analysieren, indem es Schlüsseldaten über ihre Herkunft, Navigation und Engagement liefert, um die Website zu optimieren und das Benutzererlebnis zu verbessern."
}
]
},
"permissions": [
"analytics_storage"
]
}
- Settings can be defined in website code and tag settings, website config and tag config are merged (webside have priority)
- Cookie name is not editable
- Auto load can be disabled in tag config (but not from website), a script will still be loaded to setup callback
- gtag must be loaded before Leckerli
re-import and overwrite current tag template, verify if any breaking change between your previous version and the new one exist, fix settings if required. Use preview mode to check that everything works well, then publish.
minor update can introduce breaking change for now as leckerli is in active early developement stage, so tag templage will only load updated patch version. The goal is to avoid breaking change in minor update in near future.