Introduction
Help Wix site owners audit the cookie banner, installed apps, marketing integrations, custom code, embeds, and consent-state behavior with a repeatable release checklist.
This guide is written for Wix site owners, agencies, marketers, and privacy teams.
What it means
Review Wix Privacy & Cookies settings on the published domain and confirm that Accept, Reject, category settings, and preference reopening are all available and understandable.
Inventory every tracking path: Wix marketing integrations, installed apps, Google Tag Manager, custom code, pixels, chat widgets, video embeds, maps, forms, payment tools, and automation services.
Assign each non-essential technology to the intended consent category and verify the live result; a dashboard category does not prove that the underlying request waits for consent.
Test a clean first visit, Reject, granular choices, Accept, withdrawal, and a returning visit while recording network requests, cookies, browser storage, iframes, and consent signals.
Check representative templates such as home, blog, product, booking, checkout, form, member, campaign, and embedded-content pages because apps can load selectively.
Repeat the checklist after publishing a Wix app, custom-code, marketing, tag-manager, form, or embed change and keep evidence with the release record.
Why it matters
Wix supplies platform privacy controls, but site owners choose the apps, integrations, code, forms, and disclosures. Those additions are where unexpected tracking and policy gaps commonly appear.
A repeatable release checklist helps site owners catch tracking regressions after an app, form, embed, custom-code, or marketing configuration changes.
Common mistakes
- Assuming the presence of the Wix banner automatically blocks every installed app, custom script, iframe, and pixel.
- Adding the same analytics or advertising service through both Wix and Google Tag Manager, causing duplicate or inconsistent consent behaviour.
- Testing in a browser that already stores a consent choice instead of starting with a clean visitor state.
- Checking cookies only and missing network requests, local storage, pixels, SDK calls, embedded content, or server-side destinations.
- Testing the homepage but not the pages where bookings, forms, stores, members, video, maps, or chat apps actually load.
- Updating the app stack without updating the cookie disclosure, privacy notice, vendor list, purposes, or retention information.
Wix tracking-app audit by consent state
| State | Expected result | Evidence to capture |
|---|---|---|
| Clean first visit | Only strictly necessary activity runs before a choice | Request log, storage inventory, banner and default consent signals |
| Reject | Non-essential analytics, ads, personalisation, and optional embeds stay inactive | Reloaded page traces across representative templates |
| Granular choice | Only the selected categories activate | Category-specific requests, storage, and signal updates |
| Accept | Approved services activate once without duplicate integrations | Expected vendor calls, cookies, storage, and consent update |
| Withdrawal | Future non-essential activation follows the changed choice | Preference change, reload result, and retained evidence |
Practical checklist
- Record the Wix site version and export or screenshot the current Privacy & Cookies and banner settings.
- List installed Wix apps, business integrations, custom code, GTM containers, analytics, ad pixels, embeds, chat, forms, payment providers, and automation destinations.
- Map each item to its owner, provider, purpose, data, consent category, legal basis, destination, and retention period.
- Open the published site in a clean private session and capture requests, cookies, storage, pixels, iframes, and consent signals before interaction.
- Select Reject, reload representative pages, and verify that non-essential analytics, advertising, personalisation, and optional embeds remain inactive.
- Repeat with granular choices and Accept, then withdraw consent and confirm future activation changes accordingly.
- Compare the observed inventory with Wix configuration, tag triggers, the cookie declaration, privacy policy, and consent log.
- Fix mismatches, rescan, save timestamped evidence, and schedule another check after the next relevant release.
How GDPRChecker helps
Use GDPRChecker on the published Wix domain to independently inventory requests, cookies, trackers, storage, policy links, and signals that appear before consent.
Technical scan results support implementation review but do not certify GDPR compliance or replace legal review of purposes, lawful bases, contracts, rights, security, and retention.