Tweakwise
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Tweakwise B.V. · www.tweakwise.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.
Tweakwise at a glance
- Vendor
- Tweakwise B.V.
- Headquarters
- Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 17 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 17 Nov 2026
- Panel verdict
- The AI panel rates Tweakwise 2/5, the mean of 6 judges. Tweakwise, from vendor Tweakwise B.V., is a conversion optimization product whose documented A/B testing covers its own merchandising surfaces — Builder, filter and sorting templates — with automatic bucketing on a profile key, scoping by category, and variants served server-side through the merchant's backend. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 19 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Tweakwise, from vendor Tweakwise B.V., is a conversion optimization product whose documented A/B testing covers its own merchandising surfaces — Builder, filter and sorting templates — with automatic bucketing on a profile key, scoping by category, and variants served server-side through the merchant's backend. Persona-weighted totals run 3.4 to 4.4, the high end from the e-commerce manager. It scores best on performance impact, where the vendor publishes partner-measured figures including a Navigation API call of roughly 60–72 ms and about 100–150 ms of extra PHP per warm category page view; consent and tracking scores cluster at 4 on documented consent placement and an anonymous profile key in a first-party cookie. Weakest are pricing transparency, scored 0 — we found no public pricing on the captured pages — and data and integrations, scored 2 for an inbound-only Analytics API with no public information on export. Statistical rigour sits at 2-3 on an unnamed method. The genuine split is sovereignty, ranging 0 to 3: two judges credited the named entity and GDPR claims; the rest found no public information on hosting or residency.
Speaks for it
- Publishes partner-measured server-side overhead, from a Navigation API call of roughly 60–72 ms and ~100–150 ms extra PHP per warm category page view to a throughput drop from ~850–975 to ~47–50 requests per second per node
- Documents tracking events behind the shop's cookie consent framework, with the auto-generated profile key described as a functional first-party cookie that cannot be linked to personal data
- Serves variants server-side through the merchant's backend, so client-side flicker is sidestepped by design
- Provides a documented Analytics API with a published OpenAPI specification, plus a JavaScript Personalization Pixel offered as an easier alternative
- Recommends a three-week minimum run and one variable at a time, with per-group Revenue, Conversion Rate, AOV and UPT reporting
Held against it
- We found no public information naming the statistical method behind the Significant, Inconclusive or No Change status, on confidence intervals, or on peeking, multiple-comparison or sample ratio mismatch protection
- Experiments are confined to Builder, filter and sorting templates with scoping by category, and we found no public information on multivariate, split-URL or feature-flag tests or audience targeting
- The documented Analytics API pushes storefront events in, and we found no public information on exporting experiment results or visitor-level data, or on analytics and tag-management integrations
- We found no public pricing information — no tiers, prices, billing period or the traffic metric behind them appear on the captured pages
- Sovereignty details — legal entity jurisdiction, data residency, hosting options, open source, a data processing agreement and a transfer impact assessment — are all listed as unknown
Best for
- You run a Magento storefront and want to A/B test listing-page merchandising — Builder, filter and sorting templates — with the visitor split handled automatically on a profile key
- You want concrete performance expectations before go-live, with published partner figures to benchmark your own instance against
- You need consent-conscious tracking, with events placed behind your cookie consent framework and anonymous profile keys enforced
- You are an e-commerce merchandiser running one template change at a time on category pages
Avoid if
- Your programme needs multivariate, split-URL or feature-flag experiments, or audience targeting beyond product categories
- You must verify experiment winners against your own analytics or warehouse data before acting on them
- You have to defend a winner with a named statistical method, confidence intervals and peeking protection
- You need to estimate annual cost from public pages before engaging sales
The scores
| Criterion | Panel median |
|---|---|
| Experiment types & delivery | 2 of 5 |
| Statistical method & guardrails | 1.5 of 5 |
| Consent & visitor tracking | 2 of 5 |
| Snippet performance & flicker | 3 of 5 |
| Analytics, data export & integrations | 1 of 5 |
| European sovereignty | 1.5 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
What is documented is A/B testing confined to the vendor's own builder, filter and sorting templates: the Builder editor, automatic bucketing on the profile key and scoping by product category are all there, and a personalisation variant can run against a control. But the captured pages show no multivariate or split-URL tests and no audience targeting on behaviour or attributes, which my team would need for anything beyond merchandising layouts. 2 3 9
The E-Commerce Manager
They run A/B tests on their own builder, filter and sorting templates with the visitor split handled automatically from the profile key, scoping by category, and a personalisation variant that runs against a control template — exactly the kind of test I want on my listing pages. What the documentation does not show is multivariate or split-URL testing (the advice is explicitly to change one thing at a time), audience targeting beyond categories, or feature-flag style experiments and holdouts. 2 3 9
The Product Engineer
The A/B module tests only Tweakwise's own output — builder, filter and sorting templates — with bucketing done automatically on the profile key inside the API requests, so variants are served server-side and a personalisation variant can be run against a control with an organic fallback. Scoping is by category rather than audience attributes or URLs, and we found no public information on a visual page editor, multivariate or split-URL tests, feature flags, holdouts or mutually exclusive experiment groups. 2 3 9
The CRO Consultant
The split-and-measure engine is real: A/B tests on Builder, filter and sorting templates with automatic bucketing on the profile key, scoping to one or more categories, and a personalisation variant that can run against the organic fallback as a control. But the documented test types are confined to the platform's own merchandising configurations — we found no public information on multivariate or split-URL tests, behavioural audience targeting, or feature-flag experiments. 2 3 9
The Data Protection Officer
The documentation shows A/B tests of merchandising configurations — builder, filter and sorting templates — scoped to one or more categories, with traffic distribution handled automatically from the profile key, and a personalisation variant that can itself be tested against a control with an organic fallback; variant delivery runs through the navigation and analytics APIs rather than a visual editor. We found no public information on multivariate or split-URL tests, feature flags, holdouts, mutually exclusive experiment groups or experiment lifecycle tooling. 2 3 9
The Skeptic
Tweakwise runs A/B tests on its own merchandising surfaces — builder, filter and sorting templates — with automatic bucketing on the profile key, scoping by category, and a personalisation variant that can be tested against a control with an organic fallback. We found no public information on multivariate testing, audience targeting on visitor attributes or behaviour, or experiments beyond the vendor's search-and-listing context; the guidance itself advises testing one variable at a time. 2 3
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
A per-group report shows revenue, conversion rate, average order value and units per transaction with a Significant, Inconclusive or No Change status, plus a three-week minimum runtime and a one-change-at-a-time recommendation. But the pages never name the statistical method, show no confidence or credible intervals, and document no protection against peeking or sample ratio mismatch, so I could not defend the winner to finance. 3
The E-Commerce Manager
Results come back per group with Revenue, conversion rate, average order value and units per transaction, each test is labelled Significant, Inconclusive or No Change, and a three-week minimum runtime is recommended before reading anything. The captured pages do not name whether the method is frequentist or Bayesian, show no confidence intervals, and say nothing about peeking, multiple comparisons or sample ratio mismatch. 3
The Product Engineer
Results show Revenue, Conversion Rate, Average Order Value and Units per Transaction per group with a three-state reliability label — Significant, Inconclusive or No Change — refreshed daily at midnight CET, plus guidance to run at least three weeks and test one variable at a time. We found no public information naming the statistical method, showing confidence or credible intervals, or covering peeking protection, multiple-comparison correction or sample ratio mismatch detection. 3 4
The CRO Consultant
Results report Revenue, Conversion Rate, AOV and UPT per group with a three-state reliability status (Significant, Inconclusive, No Change) refreshed daily, plus sound practice guidance: run at least three weeks and test one variable at a time. I cannot defend a winner to a client on this alone — we found no public information naming the statistical method, showing confidence or credible intervals, or handling peeking, multiple comparisons or sample ratio mismatch. 3
The Data Protection Officer
The results report shows revenue, conversion rate, average order value and units per transaction per group with a Significant, Inconclusive or No Change status, alongside a recommended minimum run of three weeks and advice to test one variable at a time. The captured pages do not name the statistical method, show confidence or credible intervals, or address peeking, multiple comparisons, sample ratio mismatch or guardrail metrics. 3
The Skeptic
Each test is graded Significant, Inconclusive or No Change, with a stated three-week minimum run and a one-variable-at-a-time rule, but the method behind those verdicts is never named and we found no public information on intervals, sample-size planning or correction for multiple metrics. The documented workflow invites adjusting or stopping a test at any time against statistics that refresh daily — peeking with no documented sequential protection, and nothing on sample ratio mismatch or guardrail metrics. 3
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
The documentation places tracking events behind the customer's cookie consent framework as stated best practice, classifies the auto-generated profile key as a functional first-party cookie the vendor describes as not requiring consent, prohibits personal data as profile keys, and offers IP hashes and hashed customer IDs as identifiers. We found no published storage lifetimes on the device, no named consent management platform integrations and no explicit §25 TDDDG mapping. 5 6
The E-Commerce Manager
The consent guidance is real: tracking events are to sit behind my cookie consent framework, consent is required unless there is a lawful basis, and the profile key is documented as a functional, first-party cookie that cannot be linked to personal data, with profile retention explained via the account limit. We found no public information on cookie lifetimes, consent-platform integrations, or a documented mode that keeps serving variants while consent is pending. 5 6 8
The Product Engineer
The documentation tells implementers to place tracking events behind their own cookie consent framework, states consent is required for analytics events unless a lawful basis applies, and describes the auto-generated profile key stored in a first-party cookie as a functional, non-traceable identifier, with anonymous identifiers enforced in place of personal data and profile retention tied to an account limit. We found no public information on integrations with common consent management platforms, cookie lifetimes, IP anonymisation or per-visitor deletion. 5 6 8
The CRO Consultant
The consent documentation is genuinely useful for a DPO conversation: customers are told to place tracking events behind their cookie consent framework for GDPR and ePrivacy, tracking events are classified as Analytics/Performance requiring consent absent a lawful basis, and the profile key is described as a functional first-party cookie with an auto-generated anonymous identifier, with profile retention tied to the account limit. The gaps sit between mid anchors — we found no public information on integrations with named consent management platforms, cookie lifetimes, or documented behaviour of the script before consent. 5 6 8
The Data Protection Officer
The vendor documents that tracking events such as searches, clicks, views and purchases require consent unless a lawful basis applies, advises placing them behind the customer's cookie consent framework, categorises the automatically generated profile key as a functional first-party cookie that cannot be linked to personal data, and states profile retention. However, the captured pages do not say whether the A/B test script itself may run before the consent banner is answered, and we found no published list of cookie and storage key names with their lifetimes, no consent-pending mode, and no named consent management platform integration or written mapping to §25 TDDDG. 5 6 8
The Skeptic
The vendor documents that tracking events belong behind the shop's cookie consent framework and need consent unless a lawful basis applies, while the auto-generated profile key is classed as a functional first-party cookie requiring no consent and profile keys must stay anonymous. Retention is stated as an account profile limit; we found no public information on storage lifetimes, named consent-platform integrations, or a consent-pending mode that still serves variants, and the guidance is framed under GDPR and ePrivacy rather than the German telemedia rules. 5 6 8
Snippet performance & flicker
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
This vendor publishes unusually concrete partner research: the Navigation API call measured at roughly 60–72 ms, warm-cache overhead of about 100–150 ms per category page view, cold-cache penalties of 0.35–0.45 seconds, and throughput dropping from roughly 850–975 to 47–50 requests per second per node, alongside diagnostic tooling advice. The figures cover server-side Magento latency rather than a client-side snippet, and we found no public information on snippet weight, flicker handling or Core Web Vitals impact. 7
The E-Commerce Manager
This is the most honest performance documentation I have seen from a vendor: warm-cache category pages take roughly 100 to 150 milliseconds of extra PHP execution, the navigation API call is about 60 to 72 milliseconds, and per-node throughput drops from roughly 850–975 to 47–50 requests per second under load with personalisation enabled. Those are server-side Magento figures though, and we found no published impact on Core Web Vitals, no script weight figures, and no discussion of flicker handling on the client side. 7
The Product Engineer
Unusually candid server-side figures: the Navigation API call is ~53–57% (~60–72 ms) of uncached list time, warm cache adds ~100–150 ms of PHP execution per category view, and enabling personal merchandising drops throughput from ~850–975 to ~47–50 requests per second per node, with full-page cache ruled out for personalised lists. Because variants are served through the merchant's backend, flicker is not part of the delivery model — but we found no public information on the weight or Core Web Vitals impact of the client-side Event Tag or Personalization Pixel, or on a self-hosting option. 7 8
The CRO Consultant
Rare candour here: the vendor publishes partner-measured figures — the Navigation API call at roughly 60–72 ms (about 53–57% of uncached list time), warm cache adding 100–150 ms of PHP execution per category view, cold cache adding 0.35–0.45 s, throughput falling from roughly 850–975 to 47–50 requests per second per node with Personal Merchandising enabled, and the caveat that category lists cannot be fully cached in Varnish — plus diagnostic methodology for benchmarking your own instance. That is most of the way to the published-figures band, but we found no public information on Core Web Vitals impact, client script weight, or a self-hosting or first-party-domain option. 7
The Data Protection Officer
A published performance research page, based on partner research, gives measured figures: the Tweakwise API call at roughly 53–57% of uncached list time (about 60–72 ms), about 100–150 ms extra PHP execution per warm category page view, an added 0.35–0.45 s on a cold cache, and throughput falling from roughly 850–975 to roughly 47–50 requests per second per node, together with benchmarking and diagnosis guidance so a customer can measure their own instance. We found no published figures on the impact on Core Web Vitals and no self-hosting or first-party-domain option; the delivery path shown is server-side, which sidesteps client-side flicker by design. 7
The Skeptic
Rare candour on the server-side path: the vendor publishes measured overhead for the Magento integration — a navigation API call of roughly 60 to 72 milliseconds, 100 to 150 milliseconds of extra PHP per category page view on warm cache, 0.35 to 0.45 seconds cold, and per-node throughput falling from roughly 850–975 to 47–50 requests per second — alongside storefront comparisons and profiling guidance. But the figures cover the API integration, not the client script: we found no public information on the event tag's weight or loading behaviour, flicker handling, or impact on Core Web Vitals. 7 8 9
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
A documented Analytics API with a published OpenAPI specification and an easier JavaScript pixel exist, but the documented flow pushes storefront events into Tweakwise for personalisation. We found no public information on export of experiment results, integration with a named analytics or tag management tool, or webhooks, so results appear to live only in the vendor's own dashboard and statistics module. 4 8 9
The E-Commerce Manager
There is a documented Analytics API with a published OpenAPI specification plus in-app reports with revenue and conversion metrics per test group, but the API's documented job is pushing my storefront events into Tweakwise. We found no public information on exporting results or visitor-level data out of the platform, or on integrations with analytics or tag management tools. 3 4 8
The Product Engineer
There is a documented Analytics API with a published OpenAPI specification and instance-key authentication, but it is inbound — for pushing storefront events to Tweakwise — alongside a JavaScript Personalization Pixel that feeds it. We found no public information on export of visitor-level or per-group results, warehouse or Google Analytics-class integrations, or an API for reading experiment results, so an A/B outcome here cannot be independently re-run against the customer's own data. 3 8 9
The CRO Consultant
The one documented API pushes storefront events into Tweakwise — with a published OpenAPI specification — while experiment results and task statistics appear to live in the vendor's own dashboard. An experiment result I cannot check in my client's own data is a claim, not a finding, and here we found no public information on exporting visitor-level results, integrations with Google Analytics, Adobe Analytics or tag managers, or any warehouse connection. 3 4 8
The Data Protection Officer
A documented Analytics API with a published OpenAPI specification and an easier JavaScript pixel let customers push visitor and customer events into Tweakwise, and an in-app statistics module shows task runs with timings and issues. We found no public information on exporting experiment results or visitor-level raw data to analytics or tag management tools, a data warehouse or a webhook, and no named analytics integration; the documented API is oriented to sending events in rather than reading findings out. 4 8 9
The Skeptic
There is a documented Analytics API with a published OpenAPI specification, but it carries events into the vendor's engine — an ingestion pipe for personalisation, not a way to check an experiment result against your own data. We found no public information on exporting results or visitor-level assignments, on integrations with analytics or tag-management tools, or on warehouse export; the A/B statistics we saw live inside the vendor's own dashboard. 3 8 9
European sovereignty
panel opinion
n/r
n/r
n/r
n/r
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 not rated — no public information
We found no public information on where visitor data is processed or hosted, on the contracting entity's jurisdiction beyond the vendor name, or on a data processing agreement or subprocessor list. The privacy pages we read state only that no personal information is stored and that personal data must not be used as profile keys. 5 6
The E-Commerce Manager not rated — no public information
We found no public information on where visitor data is processed or stored, on hosting options, on the contracting entity's jurisdiction, or on a data processing agreement. The GDPR and consent pages we read describe data handling practices, not locations or legal entities. 5 6
The Product Engineer
The vendor is named as Tweakwise B.V. and its documentation claims GDPR compliance on the basis that no personal information is stored, but the captured pages state nothing about where visitor data is processed or hosted. We found no public information on EU data residency, a data processing agreement covering the data the tracking collects, or a subprocessor list with locations. 5 6
The CRO Consultant
The contracting entity is named as Tweakwise B.V. — a Dutch company form — with GDPR compliance built around anonymous profile keys and no stored personal information, and daily statistics refreshing at midnight CET. But this only clears the entry band: hosting location, data residency, subprocessors and a data processing agreement are all unstated on the captured pages, so a buyer cannot yet verify where visitor data lands. 1 3 6
The Data Protection Officer not rated — no public information
We found no public information on where visitor data is processed or hosted, the contracting entity's jurisdiction, a data processing agreement, or a published subprocessor list including the network that delivers the snippet and API traffic. The GDPR page states that Tweakwise does not store personal information, but the captured pages say nothing about processing locations or transfer safeguards. 1 6
The Skeptic not rated — no public information
We found no public information on where visitor data is processed or stored, who the contracting entity is, or whether a data processing agreement is offered; the independently gathered sovereignty details all came back unknown. The vendor pages we read on GDPR cover anonymised profile keys and consent placement, not hosting, residency or subprocessors. 1 5 6
Pricing transparency
n/r
n/r
n/r
n/r
n/r
n/r
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 not rated — no public information
We found no public information on pricing: none of the captured pages, including the vendor homepage, states tiers, a traffic metric such as tracked users or impressions, limits, seats or a free tier, so I could not begin to compute an annual cost from public pages alone. 1 2 3
The E-Commerce Manager not rated — no public information
We found no public information on pricing — none of the captured pages, from the vendor homepage through the A/B testing, consent, performance and API documentation, stated tier prices, the traffic metric behind them, a free tier, or any sales-contact terms. 1 2 3 5 7 8
The Product Engineer not rated — no public information
We found no public information on pricing in the captured pages — no tiers, prices, billing period, or the traffic metric a tier would be priced on. The A/B testing and personalization documentation describes the modules without stating what they cost, so a buyer cannot compute an annual cost from public pages. 1 2 3
The CRO Consultant not rated — no public information
We found no public information on pricing — no price, tier, billing period or traffic metric appears on the vendor home page or the documentation pages I read. A buyer therefore cannot estimate the annual cost, including any traffic limits or the A/B test module, before a sales conversation. 1 2 3
The Data Protection Officer not rated — no public information
We found no public information on pricing: none of the captured pages states tier prices, the traffic metric behind them, a free tier, seats, term or overage. Whether a buyer can estimate an annual cost from public pages alone is therefore not determinable from what we read. 1
The Skeptic not rated — no public information
We found no public information on pricing: no tiers, no free tier, and no traffic or profile metric with a price attached anywhere we read. The closest cost-related detail is an account limit on stored profiles, described as a retention rule rather than a price. 1 8
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 Tweakwise
Is Tweakwise European?
Not determined: the vendor’s pages as captured do not say where Tweakwise is based.
Where does Tweakwise store data?
Not stated on the vendor’s pages as of 17 Nov 2026.
Does Tweakwise have a free plan?
Not stated on the vendor’s pages as of 17 Nov 2026.
What are the best alternatives to Tweakwise?
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: Tweakwise alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 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.
- We could not confirm any pricing information on the vendor’s own pages as captured, so this page shows none rather than a statement we cannot stand behind. Know more? Tell us
- 15 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
- 4 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
- 3 support 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
Sources (9)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.tweakwise.com Checked 17 Nov 2026 Details →
- 2 Experiment types & delivery — found from sitemap docs.tweakwise.com Checked 17 Nov 2026 Details →
- 3 Experiment types & delivery — found from sitemap support.tweakwise.com Checked 17 Nov 2026 Details →
- 4 Statistical method & guardrails — found from sitemap support.tweakwise.com Checked 17 Nov 2026 Details →
- 5 Consent & visitor tracking — found from sitemap docs.tweakwise.com Checked 17 Nov 2026 Details →
- 6 Consent & visitor tracking — found from sitemap docs.tweakwise.com Checked 17 Nov 2026 Details →
- 7 Snippet performance & flicker — found from sitemap docs.tweakwise.com Checked 17 Nov 2026 Details →
- 8 Analytics, data export & integrations — found from sitemap docs.tweakwise.com Checked 17 Nov 2026 Details →
- 9 Analytics, data export & integrations — found from sitemap docs.tweakwise.com Checked 17 Nov 2026 Details →