Cookie Use Notifications

To add a block with a cookie notification containing selectable and customizable files, go to the Block Library → "Other" → Block T972 "Cookies consent settings". That'll add a widget to the page that the visitor can use to manage 4 types of cookies: Essential, analytics, advertising, and custom cookies.

Go to the Content section of the block to set up the titles and descriptions for all cookie types. The four default categories are Essential, Analytics, Advertising, and Custom.

Essential cookies are enabled by default. They cannot be disabled, as they are used for the correct operation of the system and ensure the correct operation of the website, including protection against DDoS attacks.

If a visitor hasn't made a decision or has disabled cookies for analytics, Tilda's internal statistics will record the visit anyway, without using a cookie. There may be a margin of error in the results when using this method, but it won't go over 10% of visits.

When analytics cookies are allowed, the event is resent and the visit is linked to the past to make the statistics more accurate.

If a simplified stats mode is enabled in the internal Tilda statistics, cookies won't be created anyway, even if the visitor allowed them.

As long as the visitor hasn't made a decision or disabled the analytics cookie, Google Analytics and Yandex.Metrica code won't pass data over to the analytics systems. The code will only be initialized after the user takes action.

Some cookies in analytics counters are meant for advertising and are only be activated after permission has been granted to use advertising cookies specifically.

If you are coding an analytics script, you need to add a data attribute data-tilda-cookie-type="analytics" and type="text/plain" for the script, as in the example below, so that the script is activated after the user takes action.

The entire Google Tag Manager container is related to analytics cookies. Refusal to use this type of cookie will affect the entire GTM code.

As long as the visitor hasn't decided or disabled cookies for advertising systems, the Facebook and VKontakte pixel code won't be initialized and will not transmit any data. The code will only start working after the user takes action.

If you are coding pixel scripts or advertising scripts, you need to add the date attribute data-tilda-cookie-type="advertising" and type="text/plain" for the script, as in the example below, so that the script is activated after the user takes action.

If analytics cookies aren't allowed by the visitor, UTM tags will not be sent along with form data when the visitor navigates to another page. They will only be sent if the form has been completed and submitted on the same page.

If you use your own code in the Head section of the page or website or in the T123 block and that block stores cookies, you can set up the management of those files by preparing third-party code in advance and making small changes to it.

For your own script inserted in the <script> tag you need to add date attribute data-tilda-cookie-type="custom" and type="text/plain" for the script, as in the example below, so that the script is activated after the user takes action.

For a script loaded by a file from a third-party server, you'll need to replace the "src" attribute with "data-src" and add the data-tilda-cookie-type="custom" data attribute, as in the example below.