Cookiequiet

FeaturesPricingFree toolsLawsPlatformsCompareGuidesBlogFAQGlossary
FRStart freeLog in
Platforms

How to add a cookie consent banner to a Wix site

In Wix, add the snippet from Settings, then Custom Code (in the Development & integrations section), with Add Code to Pages set to All pages and Place Code in set to Head; the site must be published with a connected domain. Turn off Wix's Show banner toggle under Privacy & Cookies, and add your tags through Custom Code rather than Marketing Integrations so Cookiequiet can hold them.
Published 20 October 2026 · By the Cookiequiet team · Markdown

Steps

Check the prerequisitesCustom code on Wix requires a published site with a connected domain, which in practice means a Premium plan. Copy your snippet from the Cookiequiet dashboard.
Open Custom CodeIn your site's dashboard, go to Settings, then click Custom Code in the Development & integrations section, then + Add Custom Code.
Paste and place the snippetPaste the snippet, give it a name such as Cookiequiet, choose All pages (load the code once), choose Head under Place Code in, and click Apply.
Turn off Wix's own bannerGo to Privacy & Cookies in the dashboard, open Cookie Consent Banner and switch the Show banner toggle off. Do not install Usercentrics for Wix alongside Cookiequiet.
Move your tags to Custom CodeTags connected under Marketing Integrations are loaded by Wix and only follow Wix's own consent policy. Disconnect them and add the Google tag or Meta Pixel as a second Custom Code snippet in the Head, below Cookiequiet, marked with type="text/plain" and a data-cq-category.
Add the Cookie preferences linkTurn on the floating preferences button in the banner settings, or add a Custom Code snippet placed in Body - end containing a link with href="#cq-preferences" and data-cq-show-preferences.
Test on the published siteOpen the live site in a private window, click Reject all and check that no _ga or _fbp cookie is set. Accept all, reload, and check the consent log.

Where to paste the snippet in Wix

Wix adds custom code from the dashboard, not from the editor. The site must be published and have a connected domain first.

  1. In your site's dashboard, go to Settings.
  2. In the Development & integrations section, click Custom Code, then + Add Custom Code at the top right.
  3. Paste the snippet and name it, for example "Cookiequiet".
  4. Under Add Code to Pages, select All pages and keep the option to load the code once per visit.
  5. Under Place Code in, select Head, then click Apply.
html
<script src="https://cookiequiet.com/cq.js" data-site="YOUR_SITE_KEY" data-consent-mode="1" data-auto-block="1" defer></script>

Wix documents that custom code snippets are deleted when you change the site's domain, so re-add the snippet after a domain change.

Wix's own banner and cookies

Wix's original cookie banner is no longer available for new sites; Wix now offers Usercentrics for Wix instead. If your site still has the original banner, go to Privacy & Cookies in the dashboard, open Cookie Consent Banner and switch Show banner off. Do not install Usercentrics for Wix at the same time: one banner, one consent log.

The cookies Wix itself sets on your site (XSRF-TOKEN, hs, svSession, SSR-caching, bSession, fedops.logger.sessionId, _wixAB3 and a few others) are all classed as essential in Wix's own list, so there is nothing to block on Wix's side; list them under Necessary in your cookie table. Wix's platform analytics keeps running whatever a third-party banner says; only Wix's consent policy, set by its own banner or by Velo code through the Consent Policy API, changes that.

How to handle Marketing Integrations and embeds

Marketing Integrations. The Google tag, Google Ads, Meta Pixel and Google Tag Manager connected under Marketing Integrations are injected by Wix's own code and obey Wix's consent policy, not Cookiequiet. With data-auto-block="1", Cookiequiet holds scripts of known trackers (gtag.js, fbevents.js) that are created with JavaScript after it has run, but Wix controls the loading order of its own code, so the result must be tested. The reliable route is to disconnect the integration and add the tag as a second Custom Code snippet in the Head, below Cookiequiet, in one of two ways:

  • marked, so it does not load before consent: <script type="text/plain" data-cq-category="analytics" src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXX"></script> plus the inline part marked the same way (the Meta Pixel gets marketing);
  • or preceded by Google's default consent block for Consent Mode, as shown in the Google Analytics 4 guide.

Embed HTML element. Wix renders the HTML of that element inside an iframe on another origin. Cookiequiet, which runs in the page, cannot see or hold anything inside it, so never put a tracker there; use Custom Code.

Videos. Wix's video elements build their players with JavaScript. The auto-blocker treats youtube.com/embed as marketing and holds the player until that category is granted; check the behavior in the test step. For a Vimeo or YouTube iframe you write yourself, Custom Code is not the place either (it is not visible content), so rely on the auto-blocker.

Chat and other apps from the Wix App Market. They are loaded by Wix. The auto-blocker holds the ones in its list of known trackers; the others run, which the cookie scanner will show.

Wix's link panel expects a web address, not a bare #cq-preferences, so use one of these:

  • turn on the floating "Cookie preferences" button in the banner settings; it appears after a choice in the corner you chose;
  • or add a Custom Code snippet placed in Body - end containing <a href="#cq-preferences" data-cq-show-preferences>Cookie preferences</a>, styled with inline CSS to match your footer.

How to test

  1. Open the published site (not the editor preview) in a private window and click Reject all.
  2. Check the cookies in the developer tools: cq_consent, Wix's essential cookies, nothing from Google or Meta.
  3. Clear the cookies, click Accept all, reload: the marked tags run.
  4. Check the consent log in the Cookiequiet dashboard.

What is specific to Wix

  • Premium only. Custom code needs a published site with a connected domain; free Wix sites cannot load the snippet.
  • Wix Studio uses the same dashboard path (Settings, then Custom Code).
  • Velo developers can also push the choice into Wix's own consent policy with consentPolicyManager.setConsentPolicy from the Wix SDK, which makes Wix's own tools follow it; that is page code, beyond this guide.
  • Geo-targeting works on every plan: show the banner only to visitors in regulated countries if your US visitors should not see it, see do I need a cookie banner.

Questions

No. Wix only allows custom code on a published site with a connected domain, which requires a Premium plan.
Wix classes its own cookies as essential and keeps its platform analytics running regardless of a third-party banner. Only Wix's own consent policy, set by its banner or by Velo code through the Consent Policy API, changes that. Cookiequiet controls the tags you add through Custom Code and the known trackers it holds.
No. Two banners record two different consents and confuse visitors. Keep one, and if it is Cookiequiet, make sure the Show banner toggle of the Wix banner is off.
Because Wix loads it with its own code and only its own consent policy can stop it. Disconnect the integration and add the Google tag as a marked Custom Code snippet below Cookiequiet, or with Google's default consent block.

Sources

Related

Google Analytics 4 and Cookiequiet: Consent Mode v2 or no tag before consentRun Google Analytics 4 with Cookiequiet: Consent Mode with analytics_storage denied until consent, or the Google tag marked so it never loads before consent.Meta Pixel and Cookiequiet: fire the pixel only after marketing consentHold the Meta Pixel until marketing consent with Cookiequiet: mark the base code, fire it from Google Tag Manager on cq_consent, or use Meta's consent calls.Cookie banner for Squarespace: install Cookiequiet with code injectionPaste the Cookiequiet snippet in Squarespace's Header code injection, turn off its banner and analytics cookies, mark your tags and test Reject all.
Back to Platforms

Put a quiet banner on your website today

Free for one website with every core feature, no card and no trial clock. Upgrade a website to Pro for $3 a month when you want the AI designer, no branding and the five-year consent log.
Start free, no cardSee pricing