Skip to main content
The cookie consent banner asks visitors for permission before non-essential cookies are set on your storefront. It gates the integrations you configured (Google Analytics, Google Tag Manager, Meta Pixel, Crisp, tawk.to), the affiliate referral code and the campaign attribution SellAuth records on invoices, and it records the visitor’s choice so they are not asked on every visit. It is managed under Legal & Privacy > Cookie Banner.
SellAuth provides the mechanics: blocking scripts until consent, a reject button that is as easy as accept, per-category preferences, a stored consent record and a way to withdraw. Whether you need the banner at all, in which mode, and what your cookie policy must say depends on where you and your buyers are. Have a professional review your setup.

​
Who has it on

Shops created after the banner shipped have it on from the start. Shops that existed before keep their current behaviour until you switch it on, because turning it on changes what your visitors see and, in opt-in regions, delays your analytics until they accept. In every mode the banner honours the browser’s Global Privacy Control signal: analytics and marketing are treated as declined unless the visitor explicitly accepts them afterwards.

​
Categories

Visitors choose per category. Strictly necessary cookies cannot be switched off. Google Analytics and Google Tag Manager receive Google Consent Mode v2 signals that match the visitor’s choice.

​
Turning it on

1

Update your theme

The banner is part of the official themes. If your theme shows an update available under Themes, update it first.
2

Publish a cookie policy

The banner links to your Cookie Policy, falling back to your Privacy Policy. The Cookie Policy starter template under Legal & Privacy lists every cookie a SellAuth storefront and checkout can set, grouped by the same categories as the banner. If you inserted the template before the banner existed, insert it again to pick up the full list.
3

Choose a mode and position

Automatic by region is the default. The banner can sit as a bottom bar, a card in either bottom corner, or a centered dialog.
4

Enable and save

Tick Show the cookie banner and save. A “Cookie settings” link is added to your storefront footer so visitors can change their mind later.

​
Text and appearance

The title and message are translated into every storefront language by default. If you write your own, your text is shown to every visitor regardless of language. The banner takes its surface, text and accent colours from your theme, so it looks native on every official theme in light and dark mode; only the Accept button uses the accent colour, so Reject stays equally visible.

​
Asking again

Visitors are remembered for 180 days by default (30 to 365). When you add a new tracking tool or change your cookie policy, use Ask again under Legal & Privacy > Cookie Banner. It bumps the policy version, discards every stored choice and shows the banner to everyone once more.

​
Checkout

The checkout runs on your storefront domain and reads the same consent record. It only loads the analytics, marketing and chat integrations the visitor allowed. A visitor who lands on the checkout directly, without passing the storefront, gets the opt-out behaviour outside the opt-in regions and no non-essential scripts inside them, until they visit a storefront page and choose. The embedded checkout on your own website runs inside an iframe on a different site, so it cannot read the storefront’s consent cookie and behaves like a direct visit. Your own site’s banner governs your own page.

​
Custom themes

A custom theme has to ship the banner itself. Three pieces are needed:
  1. Render snippets/cookie-consent.njk in your layout before the theme script and before Alpine. Copy the snippet from any official theme.
  2. Mark every non-essential script as inert until consent: <script type="text/plain" data-consent="analytics"> (or functional / marketing). The runtime activates them when the category is allowed. The official snippets/script-integrations.njk shows this for each integration.
  3. Offer a way to reopen the banner: any link to #cookie-settings or an element with data-cookie-settings.
The runtime exposes window.saConsent with has('analytics'), onChange(callback), open(), acceptAll() and rejectAll(), and fires a sa:consent event on document whenever the choice changes. See Theme Structure.

​
Next steps

Legal pages

Publish the cookie policy the banner links to.

Analytics

The figures SellAuth reports without any cookies.