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.
Explain what you collect and why. Avoid legalese here.
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.
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.
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.
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
Decide when visitors should be asked to confirm their choices again. This helps you align with policy changes and long‑running sites.
You can show links to your Cookie Policy and Privacy Policy inside the banner. These should point to pages on your site that describe how you use cookies and data.
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.
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
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.
Add your GTM container ID and paste the snippets into your site.
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
<head> before any Google tags (GA4, Ads, or GTM). If you instead configure default consent directly in GTM, you can ignore this snippet. Optional controls for script blocking when you tag scripts with consent categories.
type="text/plain" and data-consent-category="analytics" (or ads, personalization, functional, security) will only run after the visitor grants that category. Adjust layout, typography, spacing, depth, and colors to match your brand. If you leave them as-is, the default theme will be used.
</body>. 