Wix

Prerequisites

Wix requires a published site with a connected domain for the supported custom-code workflow. Check your site's available settings and Wix's custom-code requirements.

Add site-wide code

1. Open the site's dashboard Settings → Custom Code.
2. Add the complete ConsentEase dashboard snippet in the Head on all intended pages, before trackers where the platform allows.
3. Use the load-once option where available to avoid duplicate loaders during navigation.
4. Save/apply and test the published domain.

Native consent and code categories

Review Wix's native consent settings and the category assigned to custom code. Consent initialization must be available before optional tags; do not categorise the entire banner as optional marketing code that cannot load before a choice.

ConsentEase has Wix consent-policy integration paths where the API is available. Verify the platform's actual state and each tracking tool rather than assuming every Wix app inherits a banner choice.

Navigation

Test initial load and client-side navigation between multiple pages. Check that the banner initializes once and the preferences control remains available. Native apps, frames and hosted flows can require separate configuration.

Verify the published site

Use separate fresh browser contexts for no choice, accept, reject and custom preferences. Check tag consent requirements, network traffic, storage and reopening preferences. Test relevant routes and mobile layouts. A theme installation does not prove coverage of checkout, embedded frames or hosted third-party pages.