ConsentPixel – Privacy · Verified

Platform Guide · Wix · 2026

Wix Cookie Banner: Setup, Options & What Actually Keeps You Compliant

Setting up a Wix cookie banner in 2026 isn't one decision — it's three. Wix's own native banner, the Usercentrics app Wix now recommends, or an independent tool: each covers a different amount of what privacy law actually requires. Here's how to set one up, and how to tell which trackers your banner is really blocking.

By ConsentPixel TeamUpdated August 202614 min readInformation, not legal advice
250M+
Wix websites worldwide — millions running GA4, Meta Pixel, and chat widgets
3 routes
To a Wix cookie banner: native (being retired), Usercentrics, or independent
$5,000
Per-visitor statutory exposure under California Penal Code §637.2 for pre-consent tracking
The short answer

To add a Wix cookie banner: go to your Wix dashboard → Settings → Privacy & Cookies → and enable a consent banner. For new sites, Wix now routes you to its recommended partner app (Usercentrics) rather than the old native toggle. Turning it on makes Wix load only essential cookies until a visitor consents.

The catch: whichever banner you pick only blocks what it can actually see. Scripts you add through Wix's marketing integrations or Custom Code can fire anyway — which is where the real compliance risk lives. This guide covers both halves. It's general information, not legal advice.

If you searched for "Wix cookie banner," you're probably at one of two moments: you just realized your Wix site has no consent banner and you want one, or you already turned something on and you're not sure it's actually doing the job. Both are the right instinct. Wix sites drop cookies by default, and in 2026 the gap between "a banner is showing" and "trackers are actually blocked before consent" is exactly where fines and lawsuits happen. Let's get both parts right — the setup, and the part the setup doesn't cover.

Do you even need a cookie banner on Wix?

Short version: almost certainly, yes. Even a basic Wix site sets its own analytics cookies out of the box. The moment you add anything else — Google Analytics, Meta Pixel, Wix Stores, a chat widget, or any app from the Wix App Market — your site is placing tracking cookies on every visitor. Privacy laws like the EU's GDPR (and its ePrivacy rules) require explicit opt-in before non-essential cookies load; US state laws like California's CCPA require a clear opt-out. Without a banner, your Wix cookies are being set with no consent mechanism at all.

There's one honest exception worth naming, because it saves people money: a free Wix plan can't run third-party tracking tools — Custom Code and most marketing integrations are paid-plan features. So a truly bare free site carries little exposure. But the instant you upgrade to a paid plan (often specifically to add Google Ads with Wix, GA4, or a marketing pixel), you create a compliance obligation. If that's you, a banner isn't optional.

Quick self-check

Open your site in a private/incognito window and, before clicking anything, open your browser's developer tools → Network tab. If you see requests to google-analytics, facebook, hotjar, clarity, tiktok, or similar before you touch any banner, those trackers are firing without consent — the exact condition regulators and plaintiffs look for.

Your 3 Wix cookie banner options in 2026

This is where most guides oversimplify. There isn't one "Wix cookie banner" — there are three routes, and Wix itself changed the landscape recently. Here they are, honestly compared, strongest coverage first.

Most coverage

1. An independent consent tool (e.g. ConsentPixel)

Best for: any paid Wix site running GA4, Meta Pixel, Google Ads, a chat widget, or session-replay — especially with US visitors.

A dedicated tool added through Wix Custom Code that blocks trackers before consent regardless of how they were added — marketing integrations and Custom Code scripts — passes all four Google Consent Mode v2 parameters, detects the Global Privacy Control (GPC) signal, and keeps a timestamped consent log.

Blocks third-party integrations and Custom Code scripts before consent
GPC detection + full GCM v2 + CIPA session-replay blocking + exportable audit log
Requires a paid Wix plan (Custom Code access); not available on free/Light plans
Wix-recommended

2. Usercentrics (the app Wix now recommends)

Best for: smaller Wix sites that mainly use Wix-native features and want an official, no-code path.

In 2024 Wix partnered with Usercentrics, and in 2026 it's the officially recommended consent app in Wix's Privacy & Cookies settings — installed from the Wix App Market. Because it's built in direct partnership with Wix, it coordinates with Wix's own server-side script loading, which generic banners miss. Free tier covers GDPR and Google Consent Mode v2; a paid tier (around €7/mo) adds CCPA and 60+ languages.

Official, no-code, auto-scans and auto-categorizes Wix components
Free tier includes GDPR + GCM v2
Wix's own docs note it can't guarantee blocking of every third-party/Custom Code script
Being retired

3. Wix's old native banner

Best for: legacy sites that still have it enabled — but not the path for new sites.

Wix's original built-in cookie notice was a simple toggle under Privacy & Cookies. As of 2026, Wix has discontinued the old native banner for new sites in favor of the Usercentrics app. If you have an older Wix site, you may still see the native toggle — but it offers the least control over which cookies are actually blocked.

Zero setup if already on — a banner is better than none
Discontinued for new sites; least granular blocking; no GPC, limited third-party control
The 2026 change worth knowing

If you follow an older tutorial that says "just flip the native Wix cookie banner toggle," it may be out of date. Wix has moved its recommended path to the Usercentrics app. The Settings → Privacy & Cookies screen is still where you start — but what it offers you now depends on how new your site is.

How to set up a Wix cookie banner

There are two live routes, and which you should pick depends on what your site actually runs. If you're on a paid plan with real marketing tools — GA4, Meta Pixel, Google Ads, a chat widget, or session-replay — the independent Custom Code route is the one worth doing, because it's the only one that reliably blocks all of those before consent (the gap we cover in the next section). If your site only uses Wix-native features, the no-code Usercentrics app is a reasonable lighter option. Here's each, recommended route first.

🧩 Recommended: add an independent consent tool via Custom Code
  1. Confirm you're on a paid Wix plan (Core, Business, or Business Elite) — Custom Code is a paid feature. This is the route that covers marketing integrations and Custom Code scripts, not just Wix-native ones.
  2. Go to Settings → Custom Code → + Add Custom Code.
  3. Set Add Code to Pages: All Pages · Place Code in: Head · Load: Once, and paste the consent tool's snippet.
  4. Drag the consent snippet to the top of the Head list — it must load before any GA4, GTM, Meta Pixel, or Wix Google Tag Manager script so it can establish consent state first.
  5. Register your marketing integrations and Custom Code scripts in the tool so it knows what to block by category (analytics, marketing, functional, session-replay).
  6. Confirm behavior on a fresh incognito visit: nothing non-essential should fire in the Network tab until you consent. That verification is the whole point — it's what separates "blocked" from "a banner is showing."
🔧 Lighter option: the no-code Usercentrics app (Wix-native sites)
  1. Sign in to Wix and open your dashboard (the Wix website manager).
  2. In the left menu, click Settings, then open Privacy & Cookies.
  3. Click Add a cookie consent banner. Wix routes you to its recommended app (Usercentrics); review and click Agree & Add.
  4. Customize the banner — position, colors, button labels, and languages — so it matches your site, then Save & Publish.
  5. Confirm behavior: on a fresh visit, only essential cookies should load until the visitor clicks Accept or adjusts categories. Consent Mode is enabled automatically when the banner is on. Bear in mind this route handles Wix-native scripts best — verify whether your third-party tools are actually blocked.

Note a Wix-specific quirk that explains why the route matters: Wix reliably supports Head injection for tracking scripts, and routes GA4/GTM/Meta through its marketing-integrations panel — so a consent tool has to intercept both the Custom Code path and the native integration path. That's why a no-code banner that only sees part of the picture often isn't enough on a paid Wix site, and why the independent Custom Code route is the more complete setup.

Before you trust the banner

See which trackers fire before consent on your Wix site

A banner showing isn't proof anything is blocked. Run a free scan to see every tracker and cookie that loads before a visitor opts in — including your Wix marketing integrations and Custom Code scripts — in about 10 seconds. No account needed.

No account needed for the scan · no credit card · information, not legal advice

What a Wix cookie banner doesn't block (the part that matters)

Here's the single most important thing to understand, and it's true of every banner option to some degree: a consent banner only blocks what it controls. Wix loads a lot of scripts, and they don't all flow through the same door.

  • Wix-native scripts (Wix Analytics, Wix Stores, Wix Chat) — these the banner handles well. Decline analytics, and Wix's own tools stop.
  • Marketing integrations (GA4, Meta Pixel, Google Ads, TikTok, Pinterest connected via Settings → Marketing Integrations) — depending on your banner, these can fire independently of the visitor's choice.
  • Custom Code scripts (Hotjar, Clarity, Klaviyo, live chat, a third-party Google Tag Manager container) — Wix's own documentation is explicit that it cannot guarantee the banner blocks non-essential cookies from these.

That gap is not a knock on Wix — it's how consent works technically. But it means a visitor can click "Reject" and still be tracked by the very tools you rely on for marketing, if those tools sit outside the banner's control. The fix is a consent layer that intercepts all paths and blocks before consent, not just the native ones. We built the deeper, Wix-specific version of this into our Wix platform guide — including a full built-in-banner-vs-ConsentPixel breakdown and the exact Custom Code install order.

Why "a banner is showing" isn't the same as "blocked" Visitor clicks "Reject" Wix-native scripts Banner blocks these ✓ Marketing integrations GA4 · Meta · TikTok — may fire anyway ⚠ Custom Code scripts Hotjar · Clarity · chat — fire independently ✕ A consent layer that intercepts ALL paths before consent The banner controls the green path; the amber and red paths need a layer that blocks before consent.
The gap isn't unique to Wix — but Wix's mix of native scripts, integrations, and Custom Code makes "showing a banner" and "blocking trackers" two different things.

Native vs Usercentrics vs independent: an honest comparison

Here's the category-level view — not a sales grid, just where each route genuinely lands on the things privacy law cares about. (For the tool-by-tool product comparison, see the Wix platform page.)

CapabilityWix native (legacy)Usercentrics (Wix-recommended)Independent (ConsentPixel)
Blocks Wix-native scripts on declineYesYesYes
Blocks marketing integrations (GA4, Meta)LimitedPartialYes
Blocks Custom Code (Hotjar, chat, GTM)NoNot guaranteedYes
Google Consent Mode v2 (all 4 params)PartialYesYes
Global Privacy Control (GPC) detectionNoVariesYes
CIPA session-replay blockingNoPartialYes
Timestamped, exportable consent logBasicYesFull
Works on free Wix planYesYesPaid only

The pattern is consistent: coverage improves as you move from the legacy native banner toward a dedicated consent layer. For a small Wix site using only Wix-native features, Usercentrics' free tier is a reasonable, official choice. For a paid Wix site running real marketing tools — and especially one with US visitors — the independent route is what closes the gap the others leave open.

The US angle most Wix guides skip: CIPA

Nearly every "Wix cookie banner" tutorial focuses on GDPR. That's important — but if any of your visitors are in the United States, the more urgent 2026 risk is often the California Invasion of Privacy Act (CIPA). Plaintiffs' firms have built a sustained wave of "wiretapping" lawsuits arguing that session-replay tools, tracking pixels, and chat widgets capturing a visitor's activity before consent amount to unlawful interception. Under California Penal Code §637.2, a plaintiff can seek statutory damages of $5,000 per violation — often read per affected visitor — with no proof of harm required.

Why this matters specifically on Wix: the highest-risk category — session-replay tools like Hotjar and Clarity — is exactly the kind of script added through Custom Code, which the banner options control least well. A Wix eCommerce or booking site running Hotjar on its checkout, serving California shoppers, can carry real exposure even with a banner showing. The defense is simple in principle: those scripts must be hard-blocked until consent, not merely "managed." You can follow the broader litigation trend on our CIPA Lawsuit Tracker.

The one thing to check today

If your Wix site uses any session-replay or heatmap tool via Custom Code and gets US traffic, confirm it does not fire before consent. This is the single highest-value privacy fix on most Wix sites — and the one a banner alone often doesn't handle.

Other Wix privacy housekeeping worth doing

While you're in the privacy corner of your Wix website manager, a few adjacent questions come up constantly. Quick, honest answers:

  • Wix privacy policy generator / templates. Wix offers a basic privacy-policy template, and there are standalone Wix privacy policy generators. Useful as a starting point — but a policy is only accurate if it lists the trackers actually on your site. The stronger approach is to generate the policy from a real scan of what fires, so it names GA4, Meta, and any Custom Code tools as data recipients rather than using generic boilerplate.
  • Is Wix HIPAA compliant? This is a common search, and the honest answer matters: a website builder is not "HIPAA compliant" on your behalf, and standard Wix plans are not designed for regulated protected health information. If you handle PHI, don't rely on any banner or builder to make you compliant — that's a question for qualified counsel and a proper BAA arrangement, not a cookie tool.
  • Are Wix websites ADA compliant? Accessibility (ADA/WCAG) is separate from cookie consent, but it's part of the same "is my site legally sound" question. Wix provides accessibility tools, but compliance depends on how you build and maintain the site — it isn't automatic.
  • Custom meta tags & SEO. Wix lets you add custom meta tags and manage SEO settings per page — worth confirming your privacy policy and cookie pages are indexable and correctly titled.
  • Google Tag Manager & Google Ads with Wix. If you run GTM or Google Ads through Wix, the consent order is critical: Consent Mode v2 must fire before your Google tags, or EU/UK conversions get dropped. This is a setup detail worth verifying, not assuming.
  • Terms of use & the "what is Wix.com on my credit card" question. Two unrelated but common Wix FAQs: your site should have clear terms of use / terms and conditions alongside the privacy policy; and an unfamiliar "Wix.com" charge on a credit card is typically a Wix subscription or domain renewal — check Settings → Billing and your domain management area rather than assuming fraud.

Key takeaways

  • You almost certainly need a Wix cookie banner — even a basic site sets cookies, and any marketing tool or paid-plan integration creates a real obligation.
  • There are three routes in 2026: the legacy native banner (being retired), the Usercentrics app Wix now recommends, and an independent consent tool via Custom Code.
  • A banner only blocks what it controls. Wix marketing integrations and Custom Code scripts can fire independently — Wix's own docs say the banner can't guarantee blocking them.
  • Coverage improves toward a dedicated consent layer that intercepts every path — integrations and Custom Code — before consent.
  • Don't skip the US/CIPA angle: session-replay tools firing before consent create $5,000-per-visitor exposure under §637.2, and they're the category banners handle worst.
  • Verify, don't assume: a scan of what fires before consent is the only way to know your banner is actually working.

The bottom line

A Wix cookie banner is genuinely easy to turn on — Settings → Privacy & Cookies and you're most of the way there. The harder, more important question is what it's actually blocking. In 2026, with Wix steering new sites to Usercentrics and US wiretapping litigation targeting ordinary small businesses, "a banner is showing" is no longer the finish line. "Nothing non-essential fires before consent" is.

Pick the route that matches your site: Usercentrics' free tier for a simple Wix-native site, or an independent consent layer for a paid site running real marketing tools and serving US visitors. Then verify it — because the only banner that protects you is one you've confirmed is doing its job.

See exactly what fires on your Wix site before consent

Run the same scan a plaintiff's firm would: every tracker and cookie loading before opt-in on your Wix site — marketing integrations and Custom Code included — in about 10 seconds. Then, if it's your site, close the gap with a single Custom Code snippet.

Scan your Wix site free →
No account for the scan · then a 14-day free trial, no credit card, from $8.99/mo · or read the full Wix setup guide · information, not legal advice
CP
The ConsentPixel Team

ConsentPixel — Privacy · Verified helps Wix site owners and agencies make consent real — blocking marketing integrations and Custom Code scripts until a visitor genuinely consents, passing all four Google Consent Mode v2 parameters, detecting GPC, and logging every consent decision as proof. This article is general educational information, not legal advice. ConsentPixel is not a law firm.

Frequently asked questions

How do I add a cookie banner to my Wix site?

Sign in to Wix, open your dashboard, and go to Settings → Privacy & Cookies. Click to add a cookie consent banner — for current sites, Wix routes you to its recommended partner app (Usercentrics), which you install from the Wix App Market with no code. Customize the banner's position, colors, and languages, then Save & Publish. Once it's on, Wix loads only essential cookies until a visitor consents, and Google Consent Mode is enabled automatically. On a paid plan, you can alternatively add an independent consent tool through Settings → Custom Code for broader tracker coverage.

Does Wix have a free cookie banner?

Yes. Wix's recommended consent app (Usercentrics) has a free tier that covers GDPR and Google Consent Mode v2, with a paid tier (around €7/month) adding CCPA support and 60+ languages. Wix's older native banner was also free but is being discontinued for new sites. The trade-off with the free options is coverage: they handle Wix-native scripts well but may not fully block third-party marketing integrations or Custom Code scripts like Hotjar or a chat widget. If your site runs those, verify what's actually blocked rather than assuming the free banner covers everything.

Does the Wix cookie banner block Google Analytics and Meta Pixel?

It depends on how they're connected and which banner you use. Tools connected through Wix's marketing integrations panel or injected via Custom Code can fire independently of the banner — Wix's own documentation states it cannot guarantee the banner blocks non-essential cookies from third-party and Custom Code sources. That means a visitor could decline and still be tracked by GA4, Meta Pixel, or a chat widget. To reliably block these before consent, you need a consent layer that intercepts both the marketing-integration path and the Custom Code path, and that passes Google Consent Mode v2 to your Google tags.

Is Wix HIPAA compliant?

No website builder makes you "HIPAA compliant" on its own, and standard Wix plans are not designed to handle protected health information (PHI). A cookie banner or consent tool addresses privacy-law consent (GDPR, CCPA, CIPA) — it does not create HIPAA compliance. If your organization handles PHI, HIPAA obligations depend on your specific data practices and require appropriate legal and contractual arrangements (such as a Business Associate Agreement), which is a question for qualified counsel — not something any banner, builder, or plugin can grant. This is general information, not legal advice.

Does my Wix site have CIPA (US wiretapping) risk?

Potentially, yes — if your Wix site uses session-replay or heatmap tools (like Hotjar or Clarity), tracking pixels, or chat widgets that capture visitor activity before consent, and you receive visitors from California. Under California Penal Code §637.2, plaintiffs can seek statutory damages of $5,000 per violation, often read per affected visitor, with no proof of harm required. These tools are usually added via Wix Custom Code, which cookie banners control least well. The protective step is to hard-block session-replay and similar scripts until the visitor consents, rather than relying on a banner to manage them. This is general information, not legal advice.

Should I use Wix's banner or an independent consent tool?

For a small Wix site that only uses Wix-native features, the Wix-recommended Usercentrics app (free tier) is a reasonable, official choice. For a paid Wix site running real marketing tools — Google Analytics, Meta Pixel, Google Ads, TikTok, a chat widget, or session-replay — and especially one serving US visitors, an independent consent tool added via Custom Code gives broader coverage: it blocks marketing integrations and Custom Code scripts before consent, detects the GPC signal, handles CIPA session-replay risk, and keeps an exportable consent log. The honest test is coverage versus your actual tracker stack — scan your site to see what's really firing before deciding.

Information, not legal advice. This article is general educational information about setting up cookie consent on Wix and does not constitute legal advice or create an attorney–client relationship. Privacy laws — including GDPR, CCPA/CPRA, CIPA, and US state laws — apply differently depending on your business, data practices, and jurisdiction, and product features and Wix's own offerings change over time. The $5,000-per-violation figure reflects statutory damages under California Penal Code §637.2; actual exposure varies by case. References to Wix, Usercentrics, and other products describe their documented capabilities, not any allegation of non-compliance. Verify your specific obligations with qualified counsel. ConsentPixel — Privacy · Verified is a consent-management and detection tool, not a law firm.
Scroll to Top