# Tweakwise — Conversion Optimization

Tweakwise by Tweakwise B.V. holds a panel rating of 2/5 from 6 AI judges (category median 2/5), as of 2026-11-19. Provenance: provenance unknown; sovereignty: not determined.

- Vendor: Tweakwise B.V. (https://www.tweakwise.com)
- Category: [Conversion Optimization](https://whats-best.ai/software/conversion-optimization.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/conversion-optimization/tweakwise
- Alternatives: https://whats-best.ai/software/conversion-optimization/tweakwise/alternatives ([markdown](https://whats-best.ai/software/conversion-optimization/tweakwise/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-19 · oldest source captured 2026-11-17

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## 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

## 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

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v2). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The Growth Lead | The E-Commerce Manager | The Product Engineer | The CRO Consultant | The Data Protection Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Experiment types & delivery | 2/5 | 2.5/5 | 2/5 | 2/5 | 2/5 | 2/5 |
| Statistical method & guardrails | 1/5 | 1.5/5 | 1/5 | 1.5/5 | 1/5 | 1.5/5 |
| Consent & visitor tracking | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 |
| Snippet performance & flicker | 3/5 | 3/5 | 3/5 | 3/5 | 3.5/5 | 3/5 |
| Analytics, data export & integrations | 1/5 | 1/5 | 1/5 | 1/5 | 1/5 | 1/5 |
| European sovereignty | n/r | n/r | 1/5 | 1.5/5 | n/r | n/r |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **2/5** | **2/5** | **1.5/5** | **2/5** | **2/5** | **1.5/5** |

### The judges

- **The Growth Lead** (v1.0): Runs the testing programme for a German marketing team and reports uplift to the board. Wants a visual editor the team can use without a developer, targeting that goes beyond the URL, and results she can defend when finance asks where the promised revenue went.
- **The E-Commerce Manager** (v1.0): Owns a shop where a tenth of a second of load time shows up in the conversion rate. Wants personalisation that can be tested against a control, a snippet that does not flicker the product page, and a traffic-based price that does not jump a tier every December.
- **The Product Engineer** (v1.0): Ships experiments behind feature flags and would rather not ship a third-party script at all. Wants server-side SDKs for the stack in use, edge delivery, metrics computed in the warehouse the team already trusts, and an API good enough to build internal tooling on.
- **The CRO Consultant** (v1.0): Sets up testing programmes for several clients and has to recommend a platform each can afford and defend. Reads for multi-project management, clean analytics integration, a consent setup a client's DPO will sign off, and a traffic metric she can estimate before the contract.
- **The Data Protection Officer** (v1.0): Has to answer whether the test script may run before the consent banner is answered, and usually finds the vendor has not said. Wants the storage keys listed, a documented consent-pending mode, visitor data processed in the EU, and a published subprocessor list that includes the CDN.
- **The Skeptic** (v1.0): A statistician who has watched too many "winners" regress to zero. Reads for the method by name, what stops a team from peeking, sample ratio mismatch checks and multiple-comparison corrections — and treats a "probability to beat" without documented assumptions as marketing.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: not determined.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Not determined | — | — |
| Hosting location | Not determined | — | — |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- GDPR no personal data: yes · no [S6]
- GDPR profile keys: personal information prohibited as profile keys for GDPR compliance [S8]
- Privacy policy disclosure: clearly inform users in privacy and cookie policies how data is collected and for what purposes [S5]
- Profile key anonymity: profile keys must be anonymous and never include personal identifiers such as email addresses [S5]
- Profile key restriction: anonymized data such as ID numbers or hashed values · yes [S6]
- Tracking consent best practice: place tracking events behind cookie consent framework to comply with GDPR and ePrivacy [S5]

**Data**
- Profile retention: profiles retained up to account limit; oldest inactive profile deleted when limit reached [S8]

**Integrations**
- Analytics authentication: query parameter instanceKey [S8]
- Analytics base URL: https://navigator-analytics.tweakwise.com [S8]
- Analytics openapi: https://navigator-analytics.tweakwise.com/openapi/v1.json · yes [S8]

**Product**
- Ab test attribution: ProfileKey linked to A/B group via Analytics JS [S3]
- Ab test builder templates: yes · A/B testing with Builder templates as test type [S2]
- Ab test category scoping: yes [S2]
- Ab test consistency requirement: profilekey must be consistent across all events and API requests [S2]
- Ab test extend stop: yes [S3]
- Ab test metrics: Revenue · CR (Conversion Rate) · AOV (Average Order Value) · UPT (Units per Transaction) [S3]
- Ab test min duration: 3 [S3]
- Ab test off revert: yes [S3]
- Ab test one variable: yes [S3]
- Ab test publish required: yes [S3]
- Ab test requirement: Tweakwise Event Tag implementation [S3]
- Ab test scope: all categories linked to Control Template A [S3]
- Ab test significance status: Significant · Inconclusive · No Change [S3]
- Ab test single category supported: yes [S2]
- Ab test statistics refresh: daily at midnight CET [S3]
- Ab test types: Builder templates · filter templates · sorting templates [S3]
- Ab test verification: Demoshop with notification and personalization key switching [S3]
- Ab test visual consistency: visual layout identical between variants except product order [S2]
- Ab testing personalization: Personalization and A/B testing present tailor-made results [S9]
- Analytics API purpose: Analytics API lets you push storefront visitor/customer events to Tweakwise, used to personalize listing pages [S8]
- Authenticated tracking: account-specific ID such as hashed customer ID for cross-device tracking [S6]
- Automatic profile key: yes [S6]
- Customer identification: profile key (customer id, visitor id, IP hash, etc.) [S8]
- Event tag collection: Event Tag collects key events like product views and purchases [S9]
- Event verification dashboard: green check in Tweakwise App dashboard for session_start and purchase [S2]
- Nonauthenticated tracking: storage-based ID (visitor ID or IP hash) [S6]
- Personalization data maturity: 2 · 4 [S2]
- Personalization description: Personalization tailors search, listing, and recommendation results to individual shoppers [S6]
- Personalization fallback: organic product when user has no history [S2]
- Personalization navigation param: tn_profilekey · navigation/merchandising requests [S9]
- Personalization pixel alternative: Personalization Pixel JavaScript plugin offered as easier alternative to Analytics API [S8]
- Personalization profilekey bucketing: automatic, based on profilekey in API requests [S2]
- Personalization recommendations param: tn_profilekey · product recommendations [S9]
- Personalization required events: purchase · session_start [S2]
- Personalization search param: tn_profilekey · search requests [S9]
- Personalization steps: Personalization requires three steps: Identify, Collect, Apply [S9]
- Personalization suggestions param: tn_profilekey · product suggestions [S9]
- Pm API time share: Tweakwise Navigation API call ~53–57% of uncached list time (~60–72 ms) [S7]
- Pm cold cache latency: Cold cache incurs +0.35s to +0.45s overhead [S7]
- Pm diag core threshold: Flag if Magento core execution time exceeds ~50 ms [S7]
- Pm diag esi modification: Custom ESI endpoints yield negligible gains (~10 ms) and increase risk [S7]
- Pm diag TLS handshake: TLS/TCP handshake ~40 ms on cold connections [S7]
- Pm diag tools: Use Blackfire.io or Magento's built-in profiler for profiling [S7]
- Pm dynamic sorting: Personal Merchandising provides dynamic real-time product sorting per visitor [S7]
- Pm instance scaling caveat: Larger instances with big catalogs or complex rules have higher API processing times [S7]
- Pm list block noncacheable: category.products.list bypasses Varnish cache; product cards cached as ESI fragments [S7]
- Pm magento time share: Magento core/layout rendering ~43–47% (~53–54 ms) [S7]
- Pm network latency: Enable keep-alive connections and minimize latency to Tweakwise endpoints [S7]
- Pm optimize baseline benchmark: Benchmark Tweakwise API response time from production server before going live [S7]
- Pm optimize minimize payload: Optimization: request only necessary attributes, bypass unused facets/filters [S7]
- Pm partner research: Guide based on performance research by partner Emico [S7]
- Pm scale php workers: Ensure adequate PHP workers and CPU capacity for un-cached requests at peak [S7]
- Pm storefront comparison: Luma ~140 ms vs Hyvä ~130 ms PM overhead [S7]
- Pm throughput impact: Throughput drops from ~850–975 to ~47–50 req/s per node at 10 concurrent users [S7]
- Pm varnish limitation: Category product lists cannot be fully cached in Varnish with PM enabled [S7]
- Pm warm cache latency: Warm cache adds ~100–150 ms PHP execution per category page view [S7]
- Profile key: A profile key (unique identifier) recognizes returning visitors and personalizes results [S6]
- Profile key category: Functional [S5]
- Profile key first party cookie: first-party · no · yes · no [S5]
- Profile key max length: 128 [S8]
- Profile key options: Customer ID · Visitor ID · IP hash · Other anonymized identifiers [S6]
- Profilekey identification: Customers identified via a profile key unique identifier [S9]
- Task statistics module: Statistics & report module in the sidebar, Tasks · yes · start time · end time · duration · issues [S4]
- Tracking event types: search · item click · view item (pageview) · purchase · add to wishlist · add to cart · session start · page impression [S5]
- Tracking events category: Analytics / Performance [S5]
- Tracking events consent: Analytics / Performance · searches · clicks · views · purchases · Yes, unless you have a lawful basis (e.g. legitimate interest, or if events are strictly necessary for providing the service). [S5]

## Questions

### 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)](https://whats-best.ai/software/conversion-optimization/convert-experiences), [Varify.io (3/5)](https://whats-best.ai/software/conversion-optimization/varify) and [Webtrends Optimize (3/5)](https://whats-best.ai/software/conversion-optimization/webtrends-optimize) 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](https://whats-best.ai/software/conversion-optimization/varify) (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [Tweakwise alternatives](https://whats-best.ai/software/conversion-optimization/tweakwise/alternatives).

## What this page leaves out

- 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.
- 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.
- 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.
- 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.

## Sources

- [S1] Vendor page: https://www.tweakwise.com (checked 2026-11-17)
- [S2] Experiment types & delivery — found from sitemap: https://docs.tweakwise.com/docs/ab-testing-personalization-with-builder (checked 2026-11-17)
- [S3] Experiment types & delivery — found from sitemap: https://support.tweakwise.com/en/articles/626879-setting-up-and-using-a-b-tests (checked 2026-11-17)
- [S4] Statistical method & guardrails — found from sitemap: https://support.tweakwise.com/en/articles/627028-can-i-see-any-statistics-on-my-tasks (checked 2026-11-17)
- [S5] Consent & visitor tracking — found from sitemap: https://docs.tweakwise.com/docs/event-tag-tracking-consent (checked 2026-11-17)
- [S6] Consent & visitor tracking — found from sitemap: https://docs.tweakwise.com/docs/gdpr-for-personalization (checked 2026-11-17)
- [S7] Snippet performance & flicker — found from sitemap: https://docs.tweakwise.com/docs/how-to-optimize-diagnose-performance-when-using-tweakwise-personal-merchandising-in-magento (checked 2026-11-17)
- [S8] Analytics, data export & integrations — found from sitemap: https://docs.tweakwise.com/reference/analytics-api-introduction (checked 2026-11-17)
- [S9] Analytics, data export & integrations — found from sitemap: https://docs.tweakwise.com/docs/api-personalization-insights (checked 2026-11-17)

---

Cite as: whats-best.ai, "Tweakwise — Conversion Optimization", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/conversion-optimization/tweakwise

Corrections: https://whats-best.ai/correct/1957?target=page
