Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Neowize is an AI driven ecommerce optimisation platform that analyses shopper behaviour, predicts intent, and recommends UX experiments and personalisation rules for online stores.
Neowize is an AI driven optimisation platform for ecommerce stores. It captures behavioural events on the storefront, builds predictive models of intent and abandonment, and proposes UX experiments, on site personalisation, and product recommendation rules. The platform integrates with Shopify, BigCommerce, custom storefronts, and major analytics tools.
A JavaScript SDK injected on the storefront emits behavioural events (pageview, scroll, add to cart, checkout step) to the Neowize backend. Order data is sent server side via the platform integration. Neowize aggregates everything, runs prediction models, and exposes a dashboard of recommended changes, plus an SDK that can apply personalisation rules client side.
Neowize sets first party cookies on the merchant domain (nw_uid, nw_session, nw_test) and may store experiment assignments in localStorage. It collects IP, user agent, referrer, page URL, behavioural events, cart content, and order amount when an order is placed.
Behavioural tracking and personalisation are not strictly necessary, so the Neowize SDK requires consent under Article 5(3) ePrivacy. Neowize acts as a processor for the merchant; certain aggregated AI models may be used to improve its own product under an independent controller role. Disclose Neowize in your privacy notice.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Neowize is primarily hosted on AWS in Ireland for European customers. Some support and analytics subprocessors are based in the United States. Transfers to non EU subprocessors rely on the EU-US Data Privacy Framework and on Standard Contractual Clauses. The DPA lists the current subprocessors.
Sign the DPA, opt for EU residency, gate the SDK behind consent in your CMP, separate analytics and personalisation categories, minimise the event payload, and document Neowize in your record of processing activities. For experiments that may impact pricing or eligibility, evaluate the EU AI Act obligations.
Websites using Neowize must obtain user consent under GDPR regulations.
DPIA considerations
A DPIA is recommended on EU consumer flows. Neowize combines behavioural profiling, AI driven personalisation, and integrations with the storefront and order data. Document the events tracked, the inference model, the retention, and any US subprocessors.
Sample consent text
We use Neowize to understand shopper behaviour and improve our store. Neowize sets first party cookies on our domain and processes events on its servers, primarily in the EU. We only activate it after you accept the analytics or personalisation category in our cookie banner.
Third-party domains contacted
app.neowize.comapi.neowize.comcdn.neowize.comevents.neowize.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| nw_uid | http_cookie | 1 year | Persistent visitor identifier set by Neowize to associate behavioural events with the same shopper across visits. |
| nw_session | http_cookie | Session | Session identifier used to group events within a single visit. |
| nw_test | http_cookie | 30 days | Stores the personalisation and experiment variant assigned to the visitor. |
| nw_attr | localStorage | 90 days | Stores attribution data (source, medium, campaign) for the visitor for cross visit analytics. |
Neowize collects user analytics data — you legally need a consent banner. Try FlowConsent free.
Neowize sets first party cookies on the merchant domain (nw_uid for the visitor ID, nw_session for the session, nw_test for experiment assignment). Behavioural events are stored on the Neowize backend with a derived identifier.
Yes. Tracking, personalisation and AI driven experiments are not strictly necessary. Article 5(3) ePrivacy requires consent before the Neowize SDK loads.
Consent under Article 6(1)(a) GDPR for tracking and personalisation. Contract performance under Article 6(1)(b) for any strictly necessary cart or checkout functionality powered by the integration.
Mostly no for the core platform, which runs on AWS in Ireland. Some support and analytics subprocessors are in the United States. Transfers to non EU subprocessors rely on the EU-US Data Privacy Framework and on SCCs.
A DPIA is recommended on consumer flows where AI driven personalisation can impact pricing or eligibility. Document the events captured, the predictive model, the retention, and the access controls.
Sign the DPA, choose EU residency, gate the SDK behind consent in your CMP, split analytics and personalisation categories, minimise the event payload, and evaluate the EU AI Act for experiments that influence eligibility or pricing.
Alternatives include Dynamic Yield, Bloomreach Engagement, Nosto, Insider, ContentSquare and Optimizely Web Experimentation, plus open source tools like GrowthBook. Choose based on EU hosting, AI explainability, and ecommerce integration depth.
Add a Neowize entry covering the nw_uid, nw_session and nw_test cookies with lifetime and purpose. Mention the EU hosting, the US subprocessors, the role of Neowize as processor, and link to its privacy notice.