After the installation you have to add the static TypoScript named Cookie OptIn to your instance. To do this, proceed as follows:

1. Open the Template module in your backend and select the page with the root template within the page tree.
2. Choose Info/Modify in the selection above the content area.
3. Click Edit the whole template record.
4. Choose the Includes tab page.
5. Choose the template Cookie OptIn (sg_cookie_optin) on the multiple selection box (right) with the name Include static (from extensions).
6. After a clicking on the selection the template appears in the left box.
7. Save your changes with the Save button above the content area.

Should your TYPO3 installation be located in a subdirectory e.g. www.example.com/subdirectory, you should adjust the value general.folder in your extension settings in the TYPO3 backend.

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.

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.

1. Go to the Tracking / Cookies module (second last in the Web module group).
2. Select the page with the root template within the page tree (if necessary) or directly select the displayed page in the content area.
3. If there is no data protection/cookies entry yet:
   • Click on the button below the introductory text.
   • Fill in all necessary fields, with which you have created the entry.
   • Continue with the next step.
4. If an entry already exists:
   • Simply click on the name of the entry or on the pencil icon to the right of the entry name to edit the entry.

You can see in the figures below which fields will be visible at which positions in the frontend. Fill in the fields Title of Opt-In Window to Link to Display Information of a Cookie Group.

Fill in the cookie information text fields. All cookies used are broken down according to these four pieces of information. Here you only specify the label.

In the last step you link the imprint and the privacy policy declaration. Proceed as follows:

IMPORTANT: On the page of your privacy policy you should also add a button or link to the cookie settings OR insert the Cookie Consent content element in the data protection declaration.

If you decide to use the button/link variant, the user must access the cookie settings with a click on the button. To do this, you create an external link with the URL of your privacy policy additionally with the parameter ?showOptIn=1. The link on our site looks like this: sgalinski.de/datenschutz/?showOptIn=1. If a user has already decided which cookies he wants to load and at a later point in time reaches a page with the parameter ?showOptIn=1, the checkboxes he selected will be displayed again.

This is followed by the colors of the window where most of the content is shown.

The group checkboxes are located in our basic template to the left of the cookie group name. Essential cookies and scripts can get a different color than all other groups.

For each button in the Cookie-Opt-In you have the possibility to change the background, the button-hover (mouseover effect to show an available interaction) and the text color.

Finally, you can adjust the colors of the group details list and the cookie description tables.

For example, the Google Tag Manager can be integrated as follows:

This looks like this in the Scripts tab of a cookie and script group:

In Settings tab of the Cookie OptIn Extension you can adjust the runtime of our cookie. After this time has elapsed, users will be prompted again to enter the Cookie Consent. The default setting is 12 months; however, you can adjust this period.

Our cookie is essential for the function of the OptIn Extension cookie. It must be saved so that the tool knows which cookie groups the user has accepted. The structure of our cookie looks like this:

• Name:
  cookie_optin
• Example data:
  essential:1 | analytics:0 | performance:1

This means: The user has accepted the essential and performance groups, but not the analytics one.

All CSS and JavaScript files are compressed. If you don't want this, you have to uncheck the box Minify generated files.

Disable Powered by

You can hide the text Powered by sgalinski Cookie OptIn in the frontend by activating the checkbox under Disable Powered by.

Set cookie for the whole domain

If you are in a subdomain, e.g. subdomain.example.com, but want to save the user settings for the whole domain example.com, you can do so here. Just enter the domain for which the cookie Consent should be valid. This does not work with external domains. You should always make sure that your settings are still DSGVO-compliant.

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.

1. Go to Trigger in the GTM.
2. Select the type Page View.
3. Select the Some page views.
4. Then click the variable you just created in the first field below.
5. Since this is an OptIn solution, select Contains in the middle field.
6. In the third field, enter the key of a cookie and script group from the Cookie OptIn Extension with the value for which cookies may be used, in this case it is 1.
   Then enter marketing:1 in the field according to our example.
7. Create a trigger for each cookie and script group.

Now you have to set the new triggers in your Google Analytics tags. Depending on which cookie group you have assigned a tag to, you adjust the corresponding trigger in the tag. To change the trigger, proceed as follows:

1. Go to Tags in the GTM.
2. Click on the name of the tag. 
3. Then click the pencil icon to customize the tag.
4. Add the new trigger under Triggering.
5. Remove the old trigger by clicking Remove next to the trigger. 

More complex triggers are not executed on every page. In the GTM these must be converted as a trigger group. To create a trigger group, proceed as follows:

1. Go to Trigger in the GTM.
2. Click on Trigger Configuration and select Trigger Group.
3. Click Add and select at least two triggers for the group. 
4. Your selected triggers appear under Triggers.

You add trigger groups to a tag in the same way as other triggers. In our example you can see that the created trigger group Trigger Group Event can be found in the tag UA - Event. This tag is only activated if both triggers of the group are fulfilled.