How to set up a GDPR compliant cookie banner?

📅 Last updated: June 2026

⏱ 3 min read

✅ All plans

In this article, you will learn how to integrate and configure a GDPR-compliant cookie consent banner into your ecosystem. Collecting clear, explicit consent before executing tracking scripts is an essential legal step in preserving your custom sending domain reputation and overall brand deliverability status.

What you will need:

An active SystemeScale account
An account with an external consent manager tool

To begin the setup process, first create a dedicated account on the external tracking compliance platform Cookiebot by visiting https://manage.cookiebot.com/en/login.

📌

Free Tier Limitation

Cookiebot's standard baseline free plan allows you to manage compliance parameters for exactly one (1) custom domain name. If you use multiple external root domains, a plan upgrade may be required.

Step 1: Map your domain and customize the layout

Before embedding code into your dashboard, you must configure your consent preferences within the external provider interface.

Inside your external compliance dashboard, navigate directly to the Domains tab and click the green Plus (+) button to input your root domain name exactly as it is registered.

Configure your consent behavior rules

Switch over to the Banner tab. Here, you can completely customize the visual look, layout rules, and underlying behavior of your cookie pop-up. Select your baseline compliance preferences and configure the exact cookie consent framework method to be active on your site pages.

Set up the interactive Privacy Trigger widget

Navigate to the Privacy Trigger tab to enable an interactive on-page widget. This trigger remains persistently visible across all live pages, allowing your visitors to instantly view, modify, or completely manage their compliance consent choices. Set your preferred visual display position and coordinating theme elements here.

Draft your explicit consent notifications

Open the Content tab to draft a clear, transparent description outlining the general purpose of your site’s cookie usage. Always keep descriptions direct, non-coercive, and completely transparent.

Note: Free plan users can input data in one language (defaulting to English). Paid configurations unlock multi-language support alongside automatic browser language detection.

The specialized Declaration tab remains exclusive to premium accounts and automates the display of granular, itemized script summaries for your users.

Step 2: Embed the script blocks into SystemeScale

Once you save your preferences, open the final tab labeled Your scripts. The platform will output two distinct script blocks that must be mapped to your workspace pages.

Primary Script Integration (Tracking Header)

The first script block handles the core operations of the banner and must be placed globally inside your page layout header settings.

Copy the first code block, log into your SystemeScale workspace, open the settings of the funnel or site pages you wish to target, and paste the code snippet directly into the Header tracking code input manager area.

💡

Blog and Ecosystem Integration

This solution is entirely optimized for blogs. Simply add the primary header script snippet to your global Blog layout settings page. The consent banner logic will automatically cascade across all published blog posts and sub-pages under that domain path.

Secondary Script Integration (Consent Declaration)

The second snippet displays your detailed cookie disclosure policy. To place it, open the specific page (such as your formal Privacy Policy page) inside the SystemeScale page editor. Drag a custom Raw HTML element directly into the target section block, click the element to open the code editor, and paste the second script block there.

⚙️

Alternative Providers

The platform featured in this walkthrough serves as a structural example. You can choose to integrate alternate consent managers (such as OneTrust, Termly, or Iubenda) within your workspace; the technical integration via header scripts and Raw HTML elements remains functionally identical.

Was this article helpful?

📄 How to improve your email deliverability → 📄 Good practices for email deliverability → 📄 How to create a custom error page (404 page) →