Cavuno
Sign InStart for free

Customize the cookie consent banner

Change the cookie consent banner title, description, and button labels in the AI Builder so the banner matches your board's voice and language.

Abi Tyas TunggalAJack WalshJ
By Abi Tyas Tunggal and Jack Walsh

By default, the cookie consent banner uses the standard wording "Hey, we use cookies" with an Accept and Reject button. On boards built with the AI website builder, the banner is part of the board's own code, so you change its wording in the AI Builder to match your voice and the language your audience expects.

The banner appears whenever Require cookie consent is enabled in Settings → Features. On hosted boards, the setting gates Cavuno Analytics, Google Analytics, Google Tag Manager, Meta Pixel, and the LinkedIn Insight Tag: none of them load until the visitor selects Accept. On builder and SDK boards, the board's own code loads Cavuno Analytics; the current starter template waits for Accept, and boards built on your own code should call analytics.install() only after the visitor accepts.

Cavuno Analytics is the built-in tracker behind your dashboard analytics. It sets a first-party session-id cookie and sends page view, engagement, and performance events. On hosted boards with Require cookie consent on, it waits for Accept like the third-party tags, so visitors who reject or ignore the banner are not counted. With the setting off, it runs for every visitor. See What Cavuno Analytics collects for the full list.

Before you begin

List the third-party tags enabled for the board and decide what the banner needs to explain. If legal requirements apply to your use of cookies or tracking, have the wording reviewed for your audience and configuration; Cavuno provides the controls but does not determine the wording you are required to use.

Edit the banner copy

  1. Open Website builder in the sidebar
  2. Describe the wording you want in chat, for example: "Change the cookie banner title to 'Cookies on this site' and the reject button to 'No thanks'"
  3. Check the banner in the preview
  4. Click Publish

The title, description, Accept and Reject buttons, and the cookie preferences link can all be reworded this way. Settings → Features turns the banner on or off but has no wording fields. Hosted boards show the standard wording, or the wording already saved for the board.

Visitors who have already accepted or rejected cookies won't see the banner again unless they clear their browser storage or reopen it from the cookie preferences link.

Verify the banner

Open your public board in a private browsing window so there is no saved consent choice. Confirm the banner shows the title, description, and button labels you published. Select Accept or Reject, then refresh the page and confirm the banner stays dismissed for that browser. If no banner appears, check that Require cookie consent is enabled under Settings → Features before testing again.

A board can keep a record of each banner choice so you can show later that a visitor consented. The banner records a choice by calling analytics.recordConsent() from @cavuno/board when the visitor selects Accept or Reject, and when they withdraw consent from the cookie preferences link. The call works before analytics load, so a rejection is recorded too.

The banner on hosted boards does not send consent records. On builder and SDK boards the banner is part of the board's own code, so choices are recorded only if that code calls analytics.recordConsent().

Each record contains:

  • A consent ID: a random identifier the banner creates once and keeps in its own consent cookie, so every choice from the same browser shares it
  • The choice: accepted, denied, or withdrawn
  • The banner version the visitor saw, a label of up to 128 characters that you set when the wording changes
  • Your board, and the time Cavuno received the record

Records do not contain the visitor's IP address, user agent, country, or analytics session-id, and the request is sent without cookies. They are stored apart from Cavuno Analytics data, never count toward your dashboard numbers, and are deleted after two years.

Consent records are not shown in your dashboard. A record shows that a choice was reported for that consent ID. It is not tamper-proof: anyone with your board's publishable key and a consent ID could send one.

Tips

  • Be specific about what cookies you use. "We use cookies to track visits and improve our site" is more trustworthy than vague boilerplate.
  • Match the tone of your board. If your board's voice is casual, keep the banner casual. If you have a B2B audience expecting formality, tighten it up.
  • Review every language. AI website builder sites can offer secondary languages. Check the banner in each language, and ask the builder to adjust any wording. Custom SDK sites set their own banner translations.
  • Make the reject button obvious. Depending on the laws that apply to your audience, refusing or withdrawing consent may need to be as easy as accepting it. The banner is one part of a consent implementation, not a guarantee of legal compliance.

Example

Instead of a generic description, name the purpose in plain language: “We use optional analytics cookies to understand which jobs and pages visitors use. Select Accept to enable them, or Reject to continue without them.” Adapt this example to the tools you actually run and the rules that apply to your board.

Frequently asked questions