Wisepops
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Wisepops SAS · wisepops.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Wisepops at a glance
- Vendor
- Wisepops SAS
- Headquarters
- Not stated on the vendor’s pages as of 10 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 10 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 10 Nov 2026
- Panel verdict
- The AI panel rates Wisepops 2.5/5, the mean of 6 judges. Wisepops, an on-site campaign tool from Wisepops SAS of Paris, scores highest on consent and tracking at 5 to 7: consent-denied behaviour is documented feature by feature, cookies are first-party with published lifetimes, and an end-user deletion endpoint exists. how scores are made
- As of
- Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Wisepops, an on-site campaign tool from Wisepops SAS of Paris, scores highest on consent and tracking at 5 to 7: consent-denied behaviour is documented feature by feature, cookies are first-party with published lifetimes, and an end-user deletion endpoint exists. That spread is a genuine split — the data protection officer scores 5, citing consent that cannot be revoked programmatically and the vendor's written position that consent is not required under GDPR, ePrivacy and CNIL exemptions, while others credit its reviewability. Data and integrations scores 5-6 on a documented API and experiment-exposure events landing in the customer's Google Analytics 4. Statistical rigour scores 5-6: Bayesian intervals and defaults of 95% significance and 80% power are published, though we found no public information on protection against peeking. Experimentation scope scores 4-5, covering client-side A/B tests of its own popup, bar, embed, feed and push formats. Weakest are performance impact at 0, with no public information on script weight, and pricing transparency at 1-2, where only a free 7-day behavioral audit is public and no prices were found.
Speaks for it
- Consent-denied behaviour is documented down to which targeting features stop, with campaigns still serving on session-only cookies
- Cookies are first-party only, with published lifetimes of session, up to two years persistent and seven days in Safari
- Experiment-exposure events are pushed automatically into the customer's own Google Analytics 4 property
- Statistical defaults of 95% significance and 80% power are published with a sample-size calculator, duration formula and worked example
- The contracting entity is named and European — Wisepops SAS at 87 Boulevard Suchet, Paris — with the CNIL named as supervisory authority
Held against it
- No public prices were found on any page read, leaving an annual cost uncomputable from public information
- We found no public information on the snippet's script weight, loading behaviour, flicker handling or effect on Core Web Vitals
- Tests auto-conclude at statistical significance, with no public information on peeking protection, multiple-comparison correction or sample-ratio-mismatch detection
- The privacy policy states providers may be located outside the EEA in non-adequate countries under standard contractual clauses, and subprocessors are listed by activity category only
- Experiments are confined to the vendor's campaign formats, with no public information on split-URL, multivariate or server-side tests
Best for
- You run on-site campaigns — popups, bars, embeds, web push — and want to A/B test design, copy and targeting rules without a developer
- Your privacy reviewer needs documented consent behaviour, including exactly what still runs when consent is denied
- You are on Shopify and want Customer Privacy integration to work without configuration
- You want experiment-exposure events in your own Google Analytics 4 property so results can be checked against your own data
Avoid if
- You need tier prices or an annual cost estimate from public pages before a sales conversation
- You require measured evidence of a third-party script's effect on Core Web Vitals before installing it
- You need split-URL, multivariate or server-side experimentation across your site rather than campaign widgets
- You need the basic testing tool to measure a campaign's impact on revenue or other long-term metrics
The scores
| Criterion | Panel median |
|---|---|
| Experiment types & delivery | 2 of 5 |
| Statistical method & guardrails | 2.5 of 5 |
| Consent & visitor tracking | 3.5 of 5 |
| Analytics, data export & integrations | 3 of 5 |
| European sovereignty | 1.5 of 5 |
| Pricing transparency | 1 of 5 |
Experiment types & delivery
Show reasoningHide reasoning
How this is scored
What can be tested and where: client-side changes through an editor, server-side and feature experiments through SDKs, multivariate and multi-page tests, and personalisation — judged on what the documentation shows rather than on the feature grid.
0 — Not an experimentation tool; the product cannot split traffic or serve variants (analytics, heatmaps or session recording only).
3 — Client-side A/B tests built in a visual editor, with a traffic split and targeting by URL or device.
5 — A/B, split-URL and multivariate tests through a visual or code editor, audience targeting on behaviour and attributes, and either rule-based personalisation or server-side experiments through a documented SDK.
8 — Client-side and server-side experiments through documented SDKs for common languages, multi-page tests, feature-flag experiments sharing one audience and metric model with web tests, mutually exclusive experiment groups, holdouts, and personalisation that can itself be tested against a control.
10 — One experimentation programme across every surface: web, app, server and edge from the same platform, experiment interactions managed, a documented experiment lifecycle from hypothesis to archived result, and a library of past results a team can search.
The Growth Lead
The WYSIWYG editor lets my team test design, copy, coupon amounts, images and targeting rules without a developer, with manual traffic allocation, control groups and automatic rollout of the winner, and targeting runs well beyond URLs into 30-plus behavioural signals plus acquisition, behaviour and relationship attributes. The documented scope is campaign-level testing of popups, bars, embeds and notifications with dynamic-variable personalisation; we found no public information on split-URL or multivariate tests, server-side SDKs or feature-flag experiments. 1 3 4 9
The E-Commerce Manager
The documentation shows A/B tests with two to six groups on their own campaign formats — popups, bars, embeds, feed and push notifications — with a WYSIWYG editor, configurable traffic allocation, control groups, automatic rollout of the winner, and personalisation through dynamic variables with targeting on acquisition, behaviour and relationship attributes. We found no public information on split-URL tests, page-level multivariate designs, feature flags or a server-side SDK, so the testable surface is the campaign layer rather than my product pages. Rule-based personalisation tested against a control group is there, which is what I ask for first, but nothing beyond that surface. 3 4 9
The Product Engineer
Tests are built in a WYSIWYG editor over popups, bars, embeds, feed and web push campaigns, with manual traffic allocation, two to six variants, control groups, automatic rollout of the winner, and behavioural targeting across thirty-plus signals plus dynamic-variable personalisation. We found no public information on server-side experiments or SDKs, split-URL or multivariate tests, multi-page tests or mutually exclusive groups, so the documented level is a client-side testing layer — well built for campaigns, but everything I would want to ship behind a flag lives on someone else's script. 3 4 5 9
The CRO Consultant
What's testable is real but bounded by the vendor's own formats: A/B tests on popups, bars, embeds, feed and web push campaigns, with a WYSIWYG editor, manual traffic allocation, control groups, automatic rollout of the winner, behavioural targeting across acquisition, behaviour and relationship attributes, and dynamic-variable personalisation of campaign content. We found no public information on split-URL tests, multivariate tests, server-side SDKs or feature-flag experiments, and no documented way to test page content outside the campaign widgets. Fine as a campaign optimiser, not a site-wide experimentation programme. 1 3 4 9
The Data Protection Officer
Experiments are client-side A/B tests of the vendor's own campaign formats — popups, bars, embeds, feed and web push — built in a WYSIWYG editor with settable traffic allocation, control groups, automatic roll-out of the winning variant, and audience targeting on more than thirty behavioural, acquisition and relationship signals. Dynamic variables allow the campaign content itself to be personalised. I found no public information on server-side experiments through a documented SDK, split-URL or multivariate tests, or testing of page content outside the campaign layer. 3 4 9
The Skeptic
What is documented is client-side A/B testing of the vendor's own campaign formats — popups, bars, embeds and push notifications — through a visual editor with traffic allocation, control groups, up to six arms and automatic rollout of the winner, plus behavioural and attribute targeting and personalisation through dynamic variables. We found no public information on split-URL or multivariate testing, or on server-side experiments through an SDK. Experiments live inside the campaign tool rather than across the site, which puts this between the basic editor offering and a fuller programme. 1 3 4 9
Statistical method & guardrails
Show reasoningHide reasoning
How this is scored
Which statistics decide the winner and what protects the customer from misreading them. Scored on what the vendor documents: the method by name, how peeking and multiple comparisons are handled, and whether sample ratio mismatch is detected.
0 — No statistical evaluation; the product shows raw counts per variant and leaves the decision to the user.
3 — A results report per variant with the method named (frequentist or Bayesian) and a significance or probability-to-beat figure.
5 — A documented method with confidence or credible intervals shown per variant, and a sample-size or test-duration calculator or stated guidance on when a result may be read.
8 — Sequential testing or another documented protection against peeking, plus correction for multiple metrics or variants, sample ratio mismatch detection, variance reduction such as CUPED, and guardrail metrics that can stop a harmful test.
10 — The statistics are auditable: methodology published in enough detail to reproduce a result, the choice of method explained per use case, raw per-visitor data available for independent re-analysis, and the interface refuses to present an underpowered result as a conclusion.
The Growth Lead
Results name the method — Bayesian statistics with a confidence interval and significance per metric — and the documentation publishes defaults of 95% significance and 80% power, a worked sample-size example, a duration formula, a multi-variant sample penalty and a recommended four-to-eight-week run, with tests auto-concluded at significance. That is what I need to defend a number to finance, though we found no public information on protection against peeking, sample ratio mismatch detection, multiple-comparison correction or guardrail metrics. 1 3 5 6
The E-Commerce Manager
The method is named and worked through: Bayesian statistics with confidence intervals and significance per metric, conclusion at 95% confidence with automatic conclusion of the test, defaults of 95% significance and 80% power, a worked example of about 80,000 visitors per variant to detect a 10% lift on a 2% baseline, a duration formula, a recommended four-to-eight-week ceiling, and a public sample-size calculator. We found no public information on protection against peeking, correction for multiple comparisons, sample-ratio-mismatch detection, variance reduction or guardrail metrics. One stated limitation matters to me as a retailer: the basic testing tool does not measure a campaign's impact on revenue or other long-term metrics — those figures sit in a higher plan. 3 5 6
The Product Engineer
Defaults are published in the open — 95 per cent significance and 80 per cent power — alongside a worked sample-size example, a duration formula, a multi-variant sample multiplier, a calculator page and drift-aware guidance to cap tests at four to eight weeks; detailed results report Bayesian intervals per metric and tests auto-conclude at significance. We found no public information on peeking protection, multiple-comparison correction, sample ratio mismatch detection or variance reduction, so I would treat these reports as directional, not decision-grade. 1 3 5 6
The CRO Consultant
The planning side is properly documented: Bayesian statistics with confidence intervals per metric, defaults stated at 95% significance and 80% power, a worked example of roughly 80,000 visitors per variant for a 10% lift on a 2% baseline, a duration formula, a recommended eight-week maximum and a three-fold sample multiplier for extra variants. What I could not find is protection during the run — no public information on sequential testing or peeking correction, multiple-comparison adjustment, sample ratio mismatch detection, variance reduction or guardrail metrics — and tests are auto-concluded at statistical significance. 1 3 5
The Data Protection Officer
The method is named — Bayesian statistics with a confidence interval for each metric — and tests are auto-concluded at 95% confidence. A sample-size calculator is published alongside stated defaults of 95% significance and 80% power, duration guidance of four to eight weeks, and the sample inflation caused by adding variants. I found no public information on sequential-testing protection against peeking, sample ratio mismatch detection, multiple-comparison correction or guardrail metrics — the documented auto-conclusion at significance comes without any stated protection of that kind. 3 5 6
The Skeptic
The method is named — Bayesian statistics with confidence intervals and significance per metric — and defaults are stated at 95% significance and 80% power, alongside sample-size guidance with a worked example, a duration formula and a recommended maximum length. What we found no public information on is anything that would stop a team from peeking: the auto-conclusion at statistical significance is described with no sequential correction, and no multiple-comparison handling or sample ratio mismatch check is documented. The note that multi-variant tests multiply the required sample is a power caution, not an inference correction. 3 5 1
Consent & visitor tracking
Show reasoningHide reasoning
How this is scored
Whether the test script respects §25 TDDDG and the ePrivacy rules as evidenced on the vendor's own pages: when the script runs relative to consent, what it stores on the device, whether a cookieless or consent-free mode exists, and how visitor identifiers are handled.
0 — No consent handling of any kind: the vendor states that the script runs and stores identifiers regardless of the visitor's consent.
3 — A documented integration with a consent tool or a setting that holds the script until consent, and the cookies or storage keys the script sets listed.
5 — Documented behaviour before and after consent, integration with common consent management platforms, and a published list of cookies and storage keys with their lifetime.
8 — A documented consent-pending mode that holds tracking until consent while variants can still be served, a cookieless or first-party-only option, IP anonymisation and retention of visitor data stated, and guidance on the legal basis for testing in the EU under §25 TDDDG.
10 — Built for §25 TDDDG: the default configuration stores nothing on the device without consent, a server-side or cookieless mode documented end to end, per-visitor data deletable on request, and the vendor states in writing how each mode maps to consent requirements.
The Growth Lead
This is documented to a level my DPO can actually review: a consent mode that keeps campaigns displaying after denied consent while tracking drops to session-only cookies, a JavaScript option to deny consent by default, automatic Shopify Customer Privacy integration, first-party-only cookies with stated lifetimes, and the vendor's written exemption position citing GDPR Article 6, the ePrivacy Directive and CNIL Deliberation 2020-091. There is also a documented endpoint to delete and suppress end-user data. We found no public information on IP anonymisation, and the documentation states consent cannot be revoked programmatically. 7 8 10
The E-Commerce Manager
Consent behaviour is documented in real detail: campaigns still display when consent is denied, falling back to session-only cookies, an option to default consent to denied through the JavaScript API, first-party-only cookies with published lifetimes (session cookies until browser close, persistent up to two years, seven days on Safari), automatic Shopify Customer Privacy integration, an end-user deletion endpoint, and stated retention periods. The vendor's stance is that consent is not required at all, claiming exemption under the GDPR, the ePrivacy Directive and CNIL guidance — a position I would want my own legal review of, all the more so since consent cannot be revoked programmatically once granted. We found no public information on IP anonymisation. 2 7 8 10
The Product Engineer
The consent documentation is unusually explicit: a consent-denied mode keeps campaigns serving on session-only cookies, disables returning-visitor detection and cross-session capping, plugs into Shopify Customer Privacy automatically, and exposes a default-consent option, while cookies are first-party with stated lifetimes (session, up to 730 days persistent, seven days on Safari) and an end-user deletion endpoint is published. The default posture, though, is persistent cookies with consent stated as not required, resting on the vendor's own exemption analysis under GDPR, the ePrivacy Directive and CNIL guidelines, and consent cannot be revoked programmatically; we found no public information on IP anonymisation, visitor-data retention, or guidance mapping the modes to §25 TDDDG specifically. 7 8 10
The CRO Consultant
This is a package a client's DPO can actually review: first-party cookies only with published lifetimes (session cookies deleted on browser close, persistent up to two years, seven days in Safari), a consent mode that keeps campaigns displaying while holding long-term tracking, documented behaviour with consent denied down to which targeting features stop, an automatic Shopify Customer Privacy integration, and a documented deletion endpoint for end-user data. The vendor also puts a written legal-basis position on the page — that consent is not required under the GDPR, the ePrivacy Directive and CNIL guidelines — which is a stated stance a DPO will want to test, not a gap in the documentation. We found no public information on IP anonymisation or the retention period applied to visitor data. 2 7 8 10
The Data Protection Officer
The vendor answers my standing question plainly: the script and its first-party cookies run before the banner is answered, under claimed exemptions from the ePrivacy Directive and CNIL guidelines, with persistent cookies by default and lifetimes published (session, up to two years, seven days in Safari). Cookie Consent Mode documents behaviour with consent denied — campaigns still serve on session-only cookies — and Shopify's Customer Privacy is integrated automatically, but the published cookie information gives categories and lifetimes rather than the storage key names, consent cannot be revoked programmatically, and I found no written mapping of the modes to the German telemedia consent rule. An end-user data deletion endpoint for GDPR requests is documented, which is more than most vendors show. 7 8 10
The Skeptic
Behaviour before and after consent is documented in detail: denied consent keeps campaigns running on session-only cookies with a listed set of disabled targeting features, an option sets the default consent state to denied, and Shopify Customer Privacy integrates automatically. Cookies are stated as first-party only with lifetimes given — session, or up to two years, seven days in Safari — and an end-user deletion endpoint exists. Against that, the vendor's stated position is that consent is not required at all, since the default configuration uses persistent cookies under claimed exemptions, and we found no published list of cookie key names, no statement on IP anonymisation, and no guidance framed for §25 TDDDG. 7 8 10
Snippet performance & flicker
n/r
n/r
n/r
n/r
n/r
n/r
Show reasoningHide reasoning
How this is scored
The cost the client-side snippet imposes on the page it tests: blocking load, flicker of original content, script weight and the effect on Core Web Vitals — scored on what the vendor measures and publishes, not on "lightning fast".
0 — A synchronous, render-blocking snippet stated as the only way to install the product, with no flicker handling.
3 — An asynchronous or anti-flicker snippet with a timeout, described in the installation documentation.
5 — Asynchronous loading and flicker handling explained with their trade-off, the snippet delivered from a CDN, and its size or loading behaviour documented.
8 — Published performance figures including the impact on Core Web Vitals, a self-hosting or first-party-domain option for the script, per-project bundles containing only active experiments, and a server-side or edge alternative for flicker-sensitive tests.
10 — Performance is a stated commitment: measured overhead published and maintained, flicker eliminated by edge or server-side rendering as a documented path, and tooling that shows the customer what their own configuration costs the page.
The Growth Lead not rated — no public information
We found no public information on the snippet's loading behaviour, script weight, flicker handling or any impact on Core Web Vitals in the captured pages, including the on-site marketing performance guide and the vendor's homepage. 9 1
The E-Commerce Manager not rated — no public information
We found no public information on the snippet's loading behaviour, script weight, anti-flicker handling or any measured effect on Core Web Vitals; the pages captured on this topic cover popup formats, display rules and benchmark practice rather than script performance. For a shop where a tenth of a second shows up in the conversion rate, this is the gap I notice most. 9
The Product Engineer not rated — no public information
We found no public information on snippet weight, loading behaviour, flicker handling, Core Web Vitals impact or a self-hosting option; the captured pages registered under this heading discuss click-through benchmarks and SEO-friendly popup design, which is marketing performance, not the cost the script imposes on the page. For a tool whose whole delivery mechanism is a third-party script, that silence is the finding. 9
The CRO Consultant not rated — no public information
We found no public information on what the snippet costs the page — nothing on script weight, loading behaviour, flicker handling, a self-hosting option, or any measured effect on Core Web Vitals. The pages captured under performance concerns turned out to cover CTR benchmarks, popup formats and targeting instead. 1 9
The Data Protection Officer not rated — no public information
I found no public information on the snippet's loading behaviour, script weight, flicker handling or effect on Core Web Vitals; the captured pages for this area cover campaign benchmarks, popup best practice and a mobile-SEO guide rather than the technical cost of the script. 9 1
The Skeptic not rated — no public information
We found no public information on the snippet's loading behaviour, flicker handling, script weight or effect on Core Web Vitals. The pages captured under this topic cover CTR benchmarks and a mobile-friendly popup guide rather than any measured cost of the script to the page. 9 1
Analytics, data export & integrations
Show reasoningHide reasoning
How this is scored
Getting results and raw data out: integration with analytics and tag management, export of visitor-level results, warehouse-native analysis, and an API — because an experiment result that cannot be checked in the customer's own data is a claim, not a finding.
0 — A closed dashboard: the vendor states that results cannot be exported or sent to another tool.
3 — Results exportable as a CSV file or report, and an integration with at least one named analytics tool.
5 — Integrations with common analytics and tag managers (Google Analytics, Adobe Analytics, Google Tag Manager or similar), export of results, and a documented API or webhooks.
8 — Visitor-level raw data export or streaming to a data warehouse, warehouse-native analysis on the customer's own metrics, CDP integration for audiences, and an API for managing experiments and reading results with stated limits.
10 — The platform treats the customer's warehouse as the source of truth: metrics defined once and computed there, full historical experiment data exportable in open formats, and a versioned API a team can build its own programme tooling on.
The Growth Lead
Results and lead data leave the platform through a documented API with stated limits — reporting and contacts endpoints, standard usage of 1,500 API calls within 30 days — plus webhooks and Zapier, and the Google Analytics integration pushes campaign and experiment-exposure events into our own GA4 property through the GTM data layer, which is the independent check I want before defending a result. We found no public information on visitor-level raw export to a data warehouse, warehouse-native analysis or CDP integrations. 10 11 1
The E-Commerce Manager
Data flows out through named channels: automatic GA4 events including experiment exposure, Google Tag Manager dataLayer support, a documented API for campaign display-and-conversion metrics and collected contacts with stated limits (1,500 calls per 30 days on standard usage), webhooks, and Zapier. We found no public information on visitor-level raw experiment data, warehouse streaming or warehouse-native analysis, so I can read results in GA4 but cannot re-check them against my own order data. 10 11
The Product Engineer
There is a documented API with stated limits — 1,500 API calls within 30 days standard — serving campaign display and conversion metrics and contact export with per-website keys, plus webhooks, Zapier, and a Google Analytics 4 integration that auto-detects and pushes display, click, form-submit and experiment-exposure events usable as conversions with dataLayer support. We found no public information on visitor-level raw export, warehouse streaming or warehouse-native metrics, and the API reads results rather than managing experiments, so my bar for building internal programme tooling on it is only half met. 1 9 10 11
The CRO Consultant
Results get out in several usable ways: automatic GA4 integration sending display, click, form-submit and experiment-exposure events with GTM dataLayer support, a documented API for campaign metrics and collected contacts with stated pagination and rate limits (1,500 API calls per 30 days as standard usage), webhooks, Zapier and a claimed hundred-plus integrations. Exposure events landing in the client's own GA4 is the piece I care about most, because a test can then be checked against the client's own data. We found no public information on visitor-level raw export, data warehouse streaming or warehouse-native analysis. 1 10 11
The Data Protection Officer
A documented API exposes campaign display and conversion metrics and collected contacts with pagination, together with webhooks, a stated limit of 1,500 API calls within 30 days in standard usage, and Zapier for non-developers. Google Analytics 4 events — including an experiment-exposure event — are pushed automatically with dataLayer support, so exposure data reaches the customer's own analytics. I found no public information on visitor-level export or streaming to a data warehouse, warehouse-native analysis, or CDP integration. 10 11 1
The Skeptic
A Google Analytics 4 integration pushes named events including experiment exposure, sent once per page view for campaigns with at least two variants or a control group — that at least puts exposure data in the customer's own analytics, where a result can be checked — with dataLayer support for tag management, webhooks, and a documented API with endpoints for campaign metrics and collected contacts plus stated call limits. We found no public information on visitor-level raw export or delivery to a data warehouse; the API is documented for reporting and lead export. 10 11
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where visitor data is processed and stored and who the contracting entity is. Independently sourced by the sovereignty pipeline; weighted higher here than in categories that hold only the customer's own data, because the script runs on every visitor to the customer's site and their behaviour is what the platform records.
0 — Vendor, contracting entity and processing of visitor data all shown to be outside the EU, with no transfer safeguard stated.
3 — A named contracting entity and a privacy policy or data processing agreement; EU data residency offered as an option or add-on, or the hosting location not stated.
5 — EU hosting or EU processing of visitor data stated as standard, together with an EU contracting entity or a published subprocessor list, and a data processing agreement offered.
8 — EU contracting entity, EU hosting on named infrastructure including the delivery of the snippet, a subprocessor list published with locations, and a data processing agreement covering the visitor data the script collects.
10 — Sovereign end to end and evidenced: vendor, entity, hosting, snippet delivery and every subprocessor European, certification published, and no visitor data reaching a non-EU party at any point.
The Growth Lead
The contracting entity is Wisepops SAS on Boulevard Suchet in Paris under French law, with the CNIL named as supervisory authority and standard contractual clauses disclosed for providers located outside the EEA. We found no public information on where visitor data is hosted or processed, including snippet delivery, and the subprocessor list gives activity categories rather than named vendors with locations. 2
The E-Commerce Manager
The contracting entity is European — Wisepops SAS in Paris, registered in the Paris trade register, with the CNIL named as supervisory authority — and the privacy policy publishes subprocessor categories and standard contractual clauses for providers located outside the EEA in non-adequate countries. We found no public information on where visitor data is hosted or processed, no named subprocessor list with locations, and no data processing agreement. Since the script runs on every visitor to my site, I would want those hosting answers before signing. 2
The Product Engineer
The contracting entity is named and French — Wisepops SAS, 87 Boulevard Suchet, 75016 Paris, registered with RCS Paris — with a privacy policy naming CNIL as the supervisory authority, but the same policy states providers may be located outside the EEA in non-adequate countries under standard contractual clauses, and subprocessors are published only as activity categories without names or locations. We found no public information on hosting or data-residency options for visitor data, on where the script and its data are delivered from, or on a data processing agreement offer, so the residency claim I care about is unproven. 2
The CRO Consultant
The contracting entity is named and European — Wisepops SAS at 87 Boulevard Suchet, Paris, with a Paris trade-register number — and the privacy policy is framed under the GDPR and French data protection law, naming the CNIL as supervisory authority. Beyond that, the hosting location and data residency are not stated, and the policy itself says providers may be located outside the EEA with standard contractual clauses as the safeguard; we found no public information on a data processing agreement. 2
The Data Protection Officer
The contracting entity is Wisepops SAS in Paris, the CNIL is named as the supervisory authority, and standard contractual clauses plus additional measures are stated for providers located outside the EEA. The privacy policy publishes subprocessor categories only — hosting, online analytics, CRM and the like — without names or locations, and I found no statement of where visitor data is hosted, no named EU infrastructure including snippet delivery, and no data processing agreement on the captured pages. 2
The Skeptic
The contracting entity is European and named — Wisepops SAS, registered in Paris — with French data protection law and the CNIL referenced as the supervisory authority. The same policy states that providers may be located outside the EEA in non-adequate countries under standard contractual clauses; subprocessors are listed by activity category only, and we found no public information on hosting location or on a data processing agreement. 2
Pricing transparency
Show reasoningHide reasoning
How this is scored
A category priced by traffic — monthly tracked users, visitors or impressions — where the tier a site lands in depends on numbers the buyer has to estimate. Whether a buyer can compute the real annual cost including traffic limits, overage, server-side or personalisation modules and seats — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price, a free tier or one priced tier, while the other tiers or the traffic metric behind the price are not stated.
5 — Prices public per tier with the billing period and the traffic metric (tracked users, visitors or impressions) and its limits stated; modules such as server-side SDKs or personalisation, or overage, may still be "contact sales".
8 — Every tier and module priced publicly with the traffic metric defined, limits, overage rates, seats, minimum term and VAT treatment stated.
10 — Complete price computability: annual invoice derivable for a given traffic volume, set of modules and team size, with overage and every add-on published.
The Growth Lead
Publicly there is a free seven-day behavioural audit reviewed live with a strategist, and notes on which features require a 2025 plan, a 2026 Self-Serve plan or a custom plan for API access — but we found no public information on prices, the traffic metric behind tiers, limits, billing periods or VAT treatment, so I cannot compute an annual cost for my traffic from the captured pages. 1 3 10
The E-Commerce Manager
The only public pricing fact is a free seven-day behavioural audit reviewed live with a strategist, and plan gating is visible in the documentation (detailed results and control groups require the newer plans), but we found no public information on any tier price, the traffic metric behind it, billing period, seats or overage. I cannot begin to estimate what my December invoice would look like from these pages. 1 3
The Product Engineer
No price appears on any captured page: the only public signals are a free 7-day behavioral audit and plan names that gate features — detailed results on a 2026 Self-Serve plan, control groups and notification testing on a 2025 plan, and the API available in Custom plans. We found no public information on tier prices, the traffic metric behind them, limits, seats or overage, so an annual cost is not computable from these pages. 1 3 10
The CRO Consultant
No price figure appears on any page I read — no amounts, no "from" price, no traffic metric and no limits — so an annual cost for a client cannot even be estimated publicly. What is documented is a free seven-day behavioural audit, plan names gating features (detailed results on a Self-Serve plan, control groups and journey analytics on a 2025 plan, API capabilities on custom plans), and an API usage limit of 1,500 calls per 30 days as standard. Everything monetary is a sales conversation. 1 3 10
The Data Protection Officer
The only pricing information on the captured pages is a free 7-day behavioral audit; the help pages name plan generations (a 2025 plan, a 2026 self-serve plan, custom plans for the API) without prices. I found no public information on the traffic metric, tier prices, overage or seats behind those plans. 1 3 10
The Skeptic
We found no public prices on any page read; feature gating refers to plan names — a 2025 plan, a 2026 Self-Serve plan, Custom plans for API access — without a stated price, traffic metric or tier structure. The only public offering is a free 7-day behavioural audit, which is a trial rather than a purchasable tier, so a buyer cannot begin to compute an annual cost from these pages. 1 3 10
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Wisepops
Is Wisepops European?
Not determined: the vendor’s pages as captured do not say where Wisepops is based.
Where does Wisepops store data?
Not stated on the vendor’s pages as of 10 Nov 2026.
Does Wisepops have a free plan?
Not stated on the vendor’s pages as of 10 Nov 2026.
What are the best alternatives to Wisepops?
As of 19 Nov 2026, the panel rates Convert Experiences (3.5/5), Varify.io (3/5) and Webtrends Optimize (3/5) highest among the other 45 Conversion Optimization products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Varify.io (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Wisepops alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 10 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 19 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 6 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page wisepops.com Checked 10 Nov 2026 Details →
- 2 Privacy policy — found from the homepage wisepops.com Checked 10 Nov 2026 Details →
- 3 Experiment types & delivery — found from sitemap support.wisepops.com Checked 10 Nov 2026 Details →
- 4 Experiment types & delivery — found from sitemap support.wisepops.com Checked 10 Nov 2026 Details →
- 5 Statistical method & guardrails — found from sitemap support.wisepops.com Checked 10 Nov 2026 Details →
- 6 Statistical method & guardrails — found from sitemap wisepops.com Checked 10 Nov 2026 Details →
- 7 Consent & visitor tracking — found from sitemap support.wisepops.com Checked 10 Nov 2026 Details →
- 8 Consent & visitor tracking — found from sitemap support.wisepops.com Checked 10 Nov 2026 Details →
- 9 Snippet performance & flicker — found from sitemap support.wisepops.com Checked 10 Nov 2026 Details →
- 10 Analytics, data export & integrations — found from sitemap support.wisepops.com Checked 10 Nov 2026 Details →
- 11 Analytics, data export & integrations — found from sitemap support.wisepops.com Checked 10 Nov 2026 Details →