Banner text Required

This is the main message visitors see in the banner when they first arrive. Keep it clear and concise.

Aim for 50–80 characters in plain language.

0 / 80 recommended

Explain what you collect and why. Avoid legalese here.

0 / 220 recommended

Banner actions Required

Control the wording of the main buttons and links in the banner so they match your tone and legal requirements.

Primary action. Keep it short and positive.

Give a clear alternative to accepting everything.

Opens the full preferences panel for granular choices.

Used for CCPA/CPRA. Lets visitors deny marketing-related cookies without changing other choices.

Preferences panel text Recommended

These texts are shown in the preferences panel that opens from the banner or a “Manage cookies” link.

Short heading for the preferences window.

Explain that visitors can turn categories on or off at any time.

Confirm choice action, usually “Save preferences”.

Closes the panel without changing consent.

Consent categories Required

Choose which categories you want to expose to users. Essential categories (functional and security) are always present but not shown as separate toggles in this simple banner.

Regulatory frameworks Recommended

Tell ConsentPilot which privacy rules you mainly care about. If you are not sure, you can keep the default choices.
How to choose a legal profile

This is saved with your configuration so you can later see which region you optimised for when reviewing consent logs. It does not automatically block visitors from other regions.
Tick everything that needs to be covered. This is for documentation and compliance records; it does not change how the banner technically works.

Consent renewal & versioning Recommended

Decide when visitors should be asked to confirm their choices again. This helps you align with policy changes and long‑running sites.

Stored with each consent record. When you change this value, existing visitors are asked to confirm their choices again under the new configuration.
Treat stored consent as expired after this time. If you choose 6 or 12 months, the banner will appear again after that period even if the configuration version stays the same.

Cookie catalog (advanced / optional) Advanced

Optional helper for your Cookie Policy page. Use it to document the cookies you use by category; it does not change how the banner or Consent Mode behave.

Open cookie catalog editor
This snippet contains a simple HTML table describing the cookies you entered above. You can paste it into your Cookie Policy page and adjust the wording if needed.

Google & GTM integration Required

Follow these steps to connect ConsentPilot with GA4 through GTM. If you do not use GTM, you can skip this section.
Need help? See the Google & GTM guide

Step 1

Choose your GA4 mode

If you are not sure and want the strictest privacy stance, choose Privacy-first (recommended). You can switch to the data modeling option later if your legal team is comfortable with it.

Step 2

Install GTM on your site

Add your GTM container ID and paste the snippets into your site.

Find it in GTM under Admin → Install Google Tag Manager.
Step 3

Configure GTM tags

  • Open Google Tag Manager to configure your tags.
  • Create GA4 and (optional) Google Ads tags.
  • Set consent defaults to “denied” in GTM.
  • Publish your GTM container.
Step 4

Default consent before banner

Decide what Google should assume before the banner has shown or the visitor has made a choice. In almost all cases you want Google to treat everything as denied by default so it never assumes consent by accident and Tag Assistant is happy.
Why this still matters: Measurement mode controls when GA4 fires; default consent sets the starting state before your consent update reaches any Google tag.
Learn more about Consent Mode default state

Paste this high in your global layout, ideally in <head> before any Google tags (GA4, Ads, or GTM). If you instead configure default consent directly in GTM, you can ignore this snippet.

Advanced options Advanced

Optional controls for script blocking when you tag scripts with consent categories.

When enabled, scripts marked with type="text/plain" and data-consent-category="analytics" (or ads, personalization, functional, security) will only run after the visitor grants that category.

Appearance (optional) Optional

Adjust layout, typography, spacing, depth, and colors to match your brand. If you leave them as-is, the default theme will be used.

Presets fill the color pickers below. You can still fine-tune them afterwards.
Card shows a compact panel; slim bar uses a flatter, full-width style.
Controls padding and spacing inside the banner.
Choose the font style used in the banner.
Scales banner text and button labels.
Adjust the depth and outline of the banner.
Quick Start Guide
  1. Fill in the tabs from left to right (Text, Categories, Google & GTM, Appearance, Legal, Advanced).
  2. Use the Banner preview at the bottom to see how your choices look on a typical page.
  3. In Google & GTM, pick Measurement mode and follow the{" "} GTM recipes {" "} to wire GA4.
  4. Default consent before banner → Option A snippet (recommended).
  5. Use Publish & preview on the right to generate the snippet and copy it into your site before </body>.
  6. Test on your site and, if needed, see more details in the{" "} Docs & recipes .
Banner preview