The European Court of Justice (ECJ) has ruled that cookie banners, which do not expressly require the consent of the website visitor, are not lawful under the DSGVO. To make it easier for TYPO3 developers to implement this new requirement, we have developed sgalinski Cookie OptIn, an easy-to-integrate module that enables embedding for cookies and tracking scripts that is compliant with DSGVO (GDPR) and ePrivacy. You can find further information in the german blog article from Dr. Schwenke.
| TYPO3 Versions | 6.2.X | 7.6.X | 8.7.X | 9.5.X |
| PHP Versions | 5.5.X | 7.0.X | 7.1.X | 7.2.X | 7.3.X |
| Tested Browsers | Internet Explorer 11 and Evergreen Browsers |
Cookies may be loaded due to the DSGVO (GDPR) and the ePrivacy regulation only if the respective side visitor agrees this expressly (cookie consent). This also eliminates the need for opt-out solutions in which the user must actively object in order to no longer receive cookies. For this reason, sgalinski Cookie OptIn only embeds cookies that you define as essential.
Non-essential cookies are sorted into any number of groups in the supplied backend module. These cookies are listed transparently and clearly to the visitors of your site with information such as origin, description and duration. The user can then decide which cookie groups he wants to accept.
You install the extension via Composer or the TER and include it with a few lines of TypoScript in your instance. Thanks to the clearly arranged backend module and an intelligent pre-configuration, your cookie opt-in banner is ready for use with just a few clicks. Any tracking scripts can also be added in no time at all, but will only be loaded once the user has agreed to it.
In the backend module of the extension, the color design of the cookie pop-up can be configured so that the banner integrates seamlessly into the frontend of your website. This gives you full control over the appearance of the cookie hint.
The cookie banner of the extension can be translated completely into any number of different languages and is played out accordingly on each language of your website.
In addition, different cookie groups can be configured for different language versions of your website. This ensures transparent, flexible data protection for all your users.
You can insert any scripts in the settings of sgalinski Cookie OptIn, which will be loaded as soon as the respective user has agreed. We have taken special care to ensure that no tracking information is lost through the OptIn banner.
Sgalinski Cookie OptIn for TYPO3 is the simplest solution to play out tracking scripts and tags as well as cookies in compliance with data protection laws.
With the clear opt-in banner you create trust and transparency with your users.
The backend module helps you to quickly divide all your cookies, tags and scripts into groups that users can freely accept.
Thanks to our licensing model, you will receive all updates for sgalinski Cookie OptIn as soon as they are available.
Our TYPO3-based website base is a comprehensive package for creating and managing websites of all kinds. The sgalinski Cookie Consent is contained in the Website-Base. Basically there is the option to create a Website at a fixed Price or to choose a Website as a Service package, which does not incur any additional costs for hosting or security and function updates. All information about the available editions of the Website-Base can be found on the pages linked below.
The extension can be easily obtained from the TER or installed via Composer.
To install the extension with Composer, you need to execute composer require sgalinski/sg-cookie-optin.
In both cases, the extension must then be added using the Template module and configured via the Tracking / Cookies module. Both steps are described below.
After the installation you have to add the static TypoScript named Cookie Optin to your instance. To do this, proceed as follows:
Before you set up your Cookie OptIn Extension in the backend, you should check your website for cookies. To do this, use the following tool, which is best opened in a new tab or window.
As shown below, enter your homepage address and confirm your entry with Scan Now.
In addition to the tool, you also have the possibility to manually check your page for cookies. To do this, follow these instructions.
The result is a clearly arranged table, as shown below. This table contains most of the information required for configuring the extension. The section on the group of essential scripts & cookies describes which data you have to enter where.
Note that this list may not be complete.
Furthermore, it is not enough to check only the homepage for cookies. It is important that the other main and sub pages of the website are also scanned.
Only if all cookies and tracking scripts are loaded exclusively via the Cookie OptIn/Consent Extension is it possible to create a GDPR-compliant website. If this is the case, the tool will not be able to deliver any results after the complete configuration when re-examined. In this case you will receive the message: No Cookies Found. You must insert cookies and scripts into our Cookie Consent until the tool cannot find cookies on any of your pages.
The figure shows which fields will be displayed where in the frontend. Fill out the fields Title of the Opt-In Window up to Link to Display Information of Cookies of a Group.
In the last step you link the imprint and the data protection declaration.
IMPORTANT You should also include a button or link to the cookie settings in the data protection declaration. So that the settings for the cookies open again when you click on the button. To do this, create an external link with the URL of your privacy statement and the parameter ?showOptIn=1. The link on our site looks like this: sgalinski.de/datenschutz/?showOptIn=1.
In this tab, the information that can be seen in the frontend is entered when a user (in our example) clicks on Further Information and then chooses Cookie Information in Essential.
The Group Title and Description of your Essential Cookies are already visible when a user clicks on Futher Information. The individual cookies that are to be listed below must be generated under Cookies with Create new.
The necessary information about the cookies can be found in the list from the tool in the first step. The Name of the cookies can be found in the Cookies column. Under Description you will find the Purpose and usually also the Provider of the cookies. The Lifetime corresponds to the Duration column. Finally, the last column tells you how to group your cookies.
If a cookie is categorized as Necessary, it is essential for the functionality of the website and you have to add it here.
You can add all non-essential cookie and script groups in the Other Groups of Scripts & Cookies tab. To do this, first create a cookie group and then proceed in the same way as with the essential cookies. However, you will most likely need to create more cookies at this point than before.
When grouping cookies, you can refer to the table in step 1 of the configuration.
For security reasons we cannot support HTML code for cookie scripts. Therefore you have to rewrite the HTML code to Javascript. The scripts can be added to your created groups under Scripts.
All cookie-related scripts must be added to the configuration and must not be loaded anywhere else!
Here is an example for the Google Tag Manager:
<script async src="https://www.googletagmanager.com/gtag/js?id=GA_MEASUREMENT_ID">
</script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'GA_MEASUREMENT_ID');
</script>var script = document.createElement('script');
script.setAttribute('type', 'text/javascript');
script.setAttribute('async', true);
script.setAttribute('src', 'https://www.googletagmanager.com/gtag/js?id=GA_MEASUREMENT_ID');
document.body.appendChild(script);
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'GA_MEASUREMENT_ID');This looks like this in the Cookie OptIn Extension in the backend:
In order for us to know which cookie groups the user has accepted, we must also store an essential cookie. The structure is as follows:
Name: cookie_optin
Example data: essential:1|analytics:0|performance:1
Explanation: The user has accepted the essential and performance groups, but not the analytics one.
Finally, adapt the sgalinski Cookie OptIn/Consent to your corporate identity colors. Enter the hex color code directly into the corresponding fields or use the color selection field. The color selection will appear automatically as soon as you click in the field.
Don't forget to save your changes with the Save button above the content area!
If you want to translate the content, simply select the language for which you want to create a translation above the content area. Easily adapt all content to the corresponding language and save the changes with the Save button above the content area.
You are now ready with the installation & configuration of the sgalinski Cookie Consent!
Only the standard layout is currently available. However, it is possible to overwrite the CSS of the cookie window.
In the long term, it is planned to offer different layouts for selection.
We assume that it is possible to create a DSGVO-compliant website with the sgalinski Cookie OptIn Extension. For this it is, however, necessary to load all cookies and tracking scripts exclusively via the extension. As this is the responsibility of the individual website administrator, we cannot assume any responsibility for the legal security of the software.
In addition, the DSGVO conformity of a website includes other aspects that are not covered by sgalinski Cookie OptIn.
You are very welcome to report any suggestions for improvement and feedback about bugs in our tracker to our internal Gitlab. You can also send this directly to our support team via our email address support@sgalinski.de.
[1] There is no guarantee for permanent availability or support of the software. Licensees may use the software during the license period as long as it is officially supported and available.