Conversion Optimization
Unbounce
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Unbounce · unbounce.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.
Unbounce at a glance
- Vendor
- Unbounce
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 13 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 13 Oct 2026
- Panel verdict
- The AI panel rates Unbounce 1.5/5, the mean of 6 judges. Unbounce, a conversion platform since 2009, pairs a drag-and-drop landing-page builder with unlimited A/B tests, Smart Traffic routing, popups and sticky bars. how scores are made
- As of
- Vendor pages captured 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Unbounce, a conversion platform since 2009, pairs a drag-and-drop landing-page builder with unlimited A/B tests, Smart Traffic routing, popups and sticky bars. Strongest are statistical rigour and performance impact, flat at 4: automatic significance calculation, a recommended p-value of 5% or less within a 1–5% range, a duration and sample-size calculator, and delivery optimisations from code compression to seven-day browser caching. Data and integrations scored 4–5, crediting 60+ built-in integrations, webhooks and an MCP server exposing aggregate analytics. Judges split on experimentation scope at 3–4: client-side testing of page variants, one variable at a time, reads to some as a capable page-testing tool, to others as short of a full programme, with no public information on server-side delivery or feature flags. Weakest are consent and tracking, flat at 2, and sovereignty at 1–2: beyond Lead Data in a Frankfurt (Germany) database, we found no public information on the contracting entity, subprocessors or where visitor data is processed. Pricing stops at a 14-day full-feature trial; the 30% average lift claim for Smart Traffic carries no published methodology.
Speaks for it
- Statistical significance is calculated automatically, with documented guidance on a 1–5% significance range, a recommended p-value of 5% or less, and an A/B test duration and sample-size calculator.
- Concrete delivery optimisations are published — automatic code compression, gzip during transfer, seven-day browser caching, render-blocking removal, an Auto Image Optimizer and AMP support — plus a Landing Page Analyzer for checking one's own pages.
- Integration breadth is well evidenced, from 60+ built-in integrations, Google Analytics 4 and Google Tag Manager to webhooks, Zapier reaching 900+ apps, and CSV export of lead data for any date range.
- Smart Traffic offers AI routing with no variant limit that starts optimising in as few as 50 visits, alongside keyword-based dynamic text replacement.
- An MCP server exposes A/B test configuration and aggregate analytics to AI assistants such as ChatGPT and Claude, with lead data and personal identifiers stated to be out of scope.
Held against it
- Experimentation is client-side testing of whole landing-page variants one variable at a time, and we found no public information on server-side or SDK delivery, feature flags, holdouts or multivariate testing.
- We found no public information on what the test script does before consent, consent-management-platform integration, cookie lifetimes or IP anonymisation, though the privacy policy discloses log data including IP address and geolocation.
- Beyond Lead Data hosted in a Frankfurt (Germany) database, we found no public information on the contracting entity, ownership, subprocessors or where visitor behaviour data is processed.
- We found no published figures for script weight or Core Web Vitals impact, and no public information on flicker handling for variant delivery.
- Beyond the p-value approach, we found no public information on confidence intervals, protection against stopping tests early, or sample ratio mismatch checks, and the 30% average conversion lift claim for Smart Traffic carries no published methodology.
Best for
- You need to build and A/B test marketing landing pages without developers, changing one variable at a time against documented significance guidance.
- You want broad marketing-stack connectivity out of the box, from Google Analytics 4 and Google Tag Manager to 60+ built-in integrations, webhooks and Zapier, with lead data exportable as CSV for any date range.
- You manage campaigns through AI assistants such as ChatGPT or Claude, which can reach test configuration and aggregate analytics via the MCP server.
- You want to evaluate before committing, with a 14-day trial offering full feature access, cancellation any time, and an interactive builder preview requiring no signup.
Avoid if
- You need server-side or SDK-delivered experiments, feature flags, holdouts or multivariate programmes — the documented product is client-side testing of hosted landing pages.
- Your compliance sign-off requires documented script behaviour relative to consent, published cookie lifetimes, consent-platform integration or IP anonymisation.
- You must establish the contracting entity, subprocessors and where visitor behaviour data is processed before signing — the only stated location is the Frankfurt (Germany) database hosting Lead Data.
- You need visitor-level experiment data in your own warehouse or an API with stated limits — the documented MCP surface is aggregate analytics with lead data out of scope.
The scores
| Criterion | Panel median |
|---|---|
| Experiment types & delivery | 2 of 5 |
| Statistical method & guardrails | 2 of 5 |
| Consent & visitor tracking | 1 of 5 |
| Snippet performance & flicker | 2 of 5 |
| Analytics, data export & integrations | 2.5 of 5 |
| European sovereignty | 0.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 — Simple A/B split of one page element through a visual editor; no server-side option, no targeting beyond URL.
3 — Client-side A/B and split-URL tests with basic audience targeting, and no SDK or server-side delivery.
5 — Client-side and server-side experiments through documented SDKs for common languages, multivariate and multi-page tests, audience targeting on behaviour and attributes, and rule-based personalisation.
8 — Feature-flag-based experiments sharing one audience and metric model with web tests, mutually exclusive experiment groups, holdouts, edge or CDN delivery, 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 drag-and-drop builder that needs no developer and unlimited A/B tests are exactly my team's entry point, and Smart Traffic routing plus dynamic text replacement give targeting beyond the bare URL. Beyond that the captured pages show only client-side landing-page work: we found no public information on server-side delivery or SDK-run experiments, and A/B testing is framed as changing one variable at a time rather than multivariate or multi-page programmes. 1 3 4 7
The E-Commerce Manager
Unlimited A/B tests on landing pages, popups and sticky bars built in the drag-and-drop editor, with their own guidance that you change one variable at a time, so multivariate testing is off the table; Smart Traffic routing and dynamic text replacement give me personalisation, with lift reported against an even traffic split. We found no public information on server-side or SDK-based experiment delivery, feature flags, holdouts or mutually exclusive tests — the only SDK mentioned is a beta for app partners. 1 3 4 10
The Product Engineer
Testing here is whole landing-page variants built in their drag-and-drop editor — unlimited A/B tests of one variable at a time, popups and sticky bars, dynamic text replacement, and Smart Traffic routing that starts optimising in as few as 50 visits. We found no public information on server-side SDKs for my own stack, feature flags, holdouts, or multivariate testing — the guidance even states A/B testing changes one variable at a time — so this is a client-side page-testing tool rather than an experimentation platform; the only SDK surfaced is a partner-program beta for building app integrations. 1 3 4 10
The CRO Consultant
What the captured pages evidence is a client-side programme: unlimited A/B tests of whole landing-page variants with the explicit guidance that you change only one variable at a time, plus Smart Traffic, an AI router with unlimited variants that starts learning in as few as 50 visits, and keyword-based dynamic text replacement. We found no public information on server-side or SDK experiment delivery, multivariate or multi-page tests, feature flags, holdouts or mutually exclusive groups — the only SDK we found is Beta access for app partners building integrations. 1 3 4
The Data Protection Officer
Unlimited A/B tests across landing page variants, an AI Smart Traffic router with no variant limit that begins learning after fifty visits, and keyword-driven dynamic text replacement are documented. We found no public information on server-side or SDK-based experiment delivery, feature flags, multivariate testing, or mutual exclusion between experiments, and the vendor's own testing guidance is framed around changing one variable at a time. 1 3 4
The Skeptic
What the captured pages show is client-side testing of landing-page variants — one variable at a time — alongside AI routing of visitors to variants, popups and sticky bars. We found no public information on server-side delivery through SDKs, multivariate or multi-page tests, or feature-flag experiments, which keeps this in split-test territory rather than a full experimentation programme. 1 3 4
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 — A "winner" or "probability to beat" figure with no documented method, no stated sample-size guidance and no warning against stopping early.
3 — The method is named (frequentist or Bayesian) but its assumptions are not documented, and nothing prevents a test from being called while it is still underpowered.
5 — Documented method with confidence or credible intervals, a sample-size or test-duration calculator, and stated guidance on when a result may be read.
8 — Sequential testing or an equivalent documented protection against peeking, 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
Unbounce calculates statistical significance automatically, publishes guidance on significance levels of one to five percent with a recommended p-value of five percent or less, and offers its own A/B test duration and sample-size calculator — the basics I need before a board meeting. The rest is not documented: we found no public information on confidence intervals, on what stops a test being read early, on corrections for multiple variants, sample-ratio checks or guardrail metrics, and Smart Traffic's claim of optimizing in as few as fifty visits carries no method behind it. 3 4
The E-Commerce Manager
They calculate statistical significance automatically, publish guidance to aim for a p-value of 5% or less with a significance level between 1% and 5%, and offer a test-duration and sample-size calculator, which is real protection against calling an underpowered test. We found no public information on which statistical method produces the number, confidence intervals, or any documented handling of peeking or sample ratio mismatch. 3 4
The Product Engineer
Significance is expressed as p-values with a recommended significance level of 1-5%, there is an A/B test duration and sample-size calculator, and the tool claims automatic significance so you can conclude tests at the right time. Beyond that we found no public information on a named method with confidence or credible intervals, protection against peeking, multiple-comparison handling across unlimited variants, sample ratio mismatch detection, or guardrail metrics — the guardrails I would want before shipping a winner behind a flag are not evidenced. 3 4
The CRO Consultant
A/B significance is handled with p-values — the vendor recommends most tests aim for a p-value of 5% or less within a 1–5% significance range — and an A/B test duration and sample size calculator exists so a client can plan run length before starting. We found no public information on confidence or credible intervals, any protection against peeking, correction for multiple metrics or variants, or sample ratio mismatch detection, and the method behind Smart Traffic's 30% average lift claim is undocumented. 3 4
The Data Protection Officer
A p-value based approach is documented with a common significance level of 1 to 5 percent, a recommendation to read results only at a p-value of 5 percent or less, and a published test duration and sample size calculator. We found no public information on confidence intervals, protection against stopping a test early, correction for multiple variants or metrics, or sample ratio mismatch detection. 4
The Skeptic
A sample-size and test-duration calculator and a recommended significance level are documented, which is more than nothing, but the method is never named with its assumptions, and we found no public information on any protection against peeking, multiple-comparison correction or sample ratio mismatch checks. The claim of an average conversion lift of thirty percent for the AI routing carries no methodology at all, and I read an undocumented winning figure as marketing until shown otherwise. 3 4
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 — Nothing on the vendor's pages says what the script stores on the device or whether it runs before consent; consent is described as the customer's problem.
3 — Cookies or local storage are listed, and a consent integration is mentioned, but the documentation does not say what the script does before consent is given.
5 — Documented behaviour before and after consent, integration with common consent management platforms, a published list of cookies and storage keys with their lifetime, and IP anonymisation described.
8 — A documented consent-pending mode that holds tracking until consent while variants can still be served, a cookieless or first-party-only option, retention of visitor data stated, and guidance on the legal basis for testing in the EU.
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 privacy policy does say what is collected on visitors — IP address, geolocation, device type, cookie data — and states that first-party cookies on Unbounce pages are anonymous, which is more than nothing. But for §25 TDDDG we found no public information on when the tracking runs relative to consent, on consent management platform integration, on cookie lifetimes or IP anonymisation, and the GDPR-oriented pages we captured speak to lead data responsibilities rather than visitor tracking. 5 6
The E-Commerce Manager
The privacy policy describes first-party cookies on their landing pages as anonymous, lists log data including IP address and geolocation, and states the visitor IP is never used for marketing. We found no public information on when the script runs relative to consent, integration with a consent management platform, a published cookie list with lifetimes, or IP anonymisation — their GDPR page speaks to account security and form data, not to test-script behaviour before consent. 5 6
The Product Engineer
The privacy policy documents that first-party cookies on Unbounce pages are anonymous and lists what log data is collected — IP address, geolocation, cookie data, browser signatures — and states lead data sits in a Frankfurt database. We found no public information on what the script does before consent, a consent-management-platform integration, cookie lifetimes, IP anonymisation, or a cookieless mode, which is what I would need to run tests lawfully in Germany out of the box. 6
The CRO Consultant
The consent-relevant evidence is confined to the privacy policy: first-party cookies on Unbounce pages are described as anonymous, log data including IP address, geolocation and cookie data is collected, and accounts are deleted within one year of cancellation. We found no public information on what the test script does before consent is given, integration with consent management platforms, a published cookie list with lifetimes, or IP anonymisation — thin for a DPO sign-off. 5 6
The Data Protection Officer
The privacy policy describes first-party cookies as anonymous and discloses log data including IP address, geolocation and cookie data, yet the captured pages do not say when the test script runs relative to the consent banner being answered. We found no public information on a documented consent-pending mode, a published list of cookies and storage keys with their lifetimes, integration with consent management platforms, or IP anonymisation. 5 6
The Skeptic
The privacy policy states that first-party cookies are anonymous and lists log data including IP address, geolocation and cookie data, so something of what lands on the device is described. We found no public information on when the script runs relative to consent, integration with consent management platforms, cookie lifetimes, or IP anonymisation. 6
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 snippet with no stated size, no flicker handling and no mention of performance.
3 — An anti-flicker snippet that hides the page until the test loads, with a timeout, and no published figures for script size or load cost.
5 — Script size and loading behaviour documented, asynchronous loading option, flicker handling explained with its trade-off, and CDN delivery of the snippet.
8 — Published performance figures including 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
Real delivery optimisations are documented — automatic code compression, compression during data transfer, seven-day browser caching, removal of render-blocking elements, an image optimiser and AMP support — and the Landing Page Analyzer lets us check our own pages. What I could not find is measured evidence: we found no public information on published page or script weight figures, on the effect on Core Web Vitals, or on how variant flicker is handled. 7 8
The E-Commerce Manager
They publish real optimisation detail for their hosted pages: automatic code compression, gzip during transfer, seven-day browser caching, render-blocking removal, an Auto Image Optimizer, AMP support and a Landing Page Analyzer. We found no public information on script weight, flicker handling, measured impact on Core Web Vitals, or a self-hosting option — as someone whose conversion rate moves with a tenth of a second, I am being asked to take the speed story on faith. 7 8
The Product Engineer
Real optimisation work is published: automatic code compression, gzip during transfer, seven-day browser caching on all pages, render-blocking removal, AMP support, and a Landing Page Analyzer the customer can run on their own pages. We found no public information on published script-weight figures, measured Core Web Vitals impact, self-hosting the script, or per-project bundles, so the delivery cost is asserted through optimisations rather than measured and published. 7 8
The CRO Consultant
Unbounce hosts the pages it tests and documents concrete optimisations — automatic code compression, compressed data transfer, seven-day browser caching, removal of render-blocking elements, an Auto Image Optimizer and AMP support — plus a Landing Page Analyzer for checking one's own pages. We found no published figures for script size or Core Web Vitals impact, and no public information on flicker handling for variant delivery, self-hosting, or an edge alternative. 7 8
The Data Protection Officer
Automatic code compression, gzip during data transfer, seven-day browser caching and the removal of render-blocking elements are documented, alongside AMP support, an Auto Image Optimizer and a landing page analyser. We found no published figures for the snippet's script size or load cost, and no public information on flicker handling for variant delivery or measured impact on Core Web Vitals. 7 8
The Skeptic
Named optimisations are documented — automatic code compression, compression during data transfer, seven-day browser caching, render-blocking removal, an image optimiser and AMP support — together with a landing page analyser that lets a customer measure their own pages. We found no published figures for script weight or Core Web Vitals impact, and no public information on flicker handling. 7 8
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 — Results visible in the vendor's dashboard only; no export, no analytics integration, no API.
3 — CSV export of aggregated results and one analytics integration, with no visitor-level data and no documented API.
5 — Integrations with common analytics and tag managers, export of results, and a documented API for managing experiments and reading results.
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 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
Getting numbers out looks genuinely workable: Google Analytics 4 and Google Tag Manager integrations, sixty-plus connectors plus webhooks, an MCP server documented to expose A/B test configuration and aggregate analytics, and CSV export of lead data for any date range. For defending results in our own stack, we found no public information on visitor-level raw data export, warehouse delivery or API limits — the aggregate view is what we get. 6 9 10
The E-Commerce Manager
Google Analytics 4 and Google Tag Manager integrations, 60-plus built-in integrations with Zapier reaching 900-plus apps, webhooks, and a CSV export of lead data for any date range get results out of their dashboard; the MCP server exposes aggregate analytics such as traffic source, conversion rates and lead volume, with lead data and personal identifiers stated to be out of scope for compliance. We found no public information on visitor-level experiment data export, data-warehouse streaming, or a documented API with stated limits. 6 9 10
The Product Engineer
The integration catalogue is broad — 60+ built-in integrations, Zapier to 900+ apps, webhooks, and a GA4 integration documented in enough detail to say GA4 data is displayed but not stored, processed, forwarded or shared — and lead data exports to CSV for any date range. For the parts I care about, the only programmatic surface shown is the MCP server exposing page content, A/B test variants and aggregate analytics to AI assistants, and we found no public information on a versioned developer API with stated limits or on visitor-level raw data export into our warehouse. 1 6 9 10
The CRO Consultant
There is a broad catalogue — Google Analytics 4 with its data points displayed in Unbounce, Google Tag Manager, Hotjar, Hubspot, Salesforce and 60+ built-in integrations plus Zapier and webhooks — and lead data can be downloaded as CSV for any date range. The MCP server adds programmatic access to A/B test configuration and aggregate analytics such as traffic source and conversion rates, so results can be pulled and checked; we found no public information on visitor-level experiment data export, warehouse streaming, or stated API limits. 1 6 9 10
The Data Protection Officer
Google Analytics and Google Tag Manager sit among sixty-plus built-in integrations with webhooks and a nine-hundred-app Zapier reach, lead data can be downloaded as a CSV for any date range, and an interface for AI assistants exposes test variants and aggregate analytics while keeping lead data out for GDPR and CCPA reasons. We found no public information on export of visitor-level experiment assignment data, warehouse-native analysis, or a documented API with stated limits. 6 9 10
The Skeptic
Integration breadth is well evidenced with 60-plus built-in integrations, webhooks, Google Analytics and Tag Manager, and lead data can be exported as CSV for any date range. We found no public information on a documented API for reading experiment results, and the AI-assistant access that is documented offers aggregate analytics only with lead data removed — a result I cannot re-analyse at visitor level is a claim, not a finding. 1 6 9 10
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 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and visitor data leaving the EU without a stated safeguard.
3 — EU data residency offered as an option or an enterprise add-on while the contracting entity is non-EU, or the subprocessor list is absent.
5 — EU processing of visitor data as standard and an EU contracting entity, but parts of the chain — CDN, support access, analytics — are non-EU without an explained safeguard.
8 — EU hosting on named infrastructure including the delivery of the snippet, EU contracting entity, subprocessor list published, and a DPA 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 one European fact on the vendor's pages is that lead data sits in a Frankfurt database, which I appreciate. Everything my data protection officer will ask about — the contracting entity's jurisdiction, where visitor tracking data and page delivery are processed, the subprocessor list — we found no public information on, so for a script that observes every visitor this is not something I can take to compliance. 6
The E-Commerce Manager
The one European element I can find is that lead data is hosted in a Frankfurt database, and nothing more: the contracting entity, ownership and overall data residency are unstated in the captured pages. I found no published subprocessor list and no stated safeguard for the delivery and analytics chain that touches every visitor to my shop, so I cannot tell where visitor behaviour is processed. 6
The Product Engineer
The one concrete fact is that lead data is hosted in a Frankfurt database, and the vendor states visitors' personal data is never used for marketing. We found no public information on the contracting entity, ownership, where visitor behaviour recorded during tests is processed, or any subprocessor list — for a script that runs on every visitor, the chain is unverifiable from the vendor's own pages. 6
The CRO Consultant
The only concrete datum on the vendor's own pages is that lead data is hosted in Frankfurt, Germany; we found no public information on the contracting entity's jurisdiction, ownership, the residency of visitor tracking data, or any subprocessor list. The AI features are powered by OpenAI and Anthropic, and we found no public information on a data processing agreement covering the visitor data the pages collect. 6
The Data Protection Officer
Lead data is stated to be hosted in Frankfurt, Germany, which covers the form data visitors submit, but the captured pages do not state the contracting entity, where behavioural visitor data is processed, or where the snippet is delivered from. We found no public information on a subprocessor list, and AI-assisted features name OpenAI and Anthropic as processors of page content and aggregate analytics with no stated safeguard. 6
The Skeptic
The only location statement we found is that lead data is hosted in a Frankfurt database. We found no public information on the contracting entity's jurisdiction, ownership, subprocessors, or where the rest of the visitor data the platform records is processed and stored. 6
Pricing transparency
not rated — the vendor publishes no price
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 starting price or a free tier exists, but the traffic metric, the limits and what happens above them are unstated — the invoice is unknowable.
5 — Tier prices public with the traffic metric and its limits defined, but at least one commonly needed piece (server-side SDKs, personalisation, overage) is unpriced or "contact sales".
8 — Every tier priced publicly with the traffic metric defined, limits, overage rates, module prices, 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
All the captured pages offer on cost is a 14-day full-feature trial and a free way to start building. We found no public information on tier prices, the traffic metric plans are priced on, limits, overage or minimum term, so no annual invoice can be worked out without a sales conversation. 3
The E-Commerce Manager
A 14-day full-feature trial, cancellable any time, and a free build start are published, and that is the whole of it. We found no public information on tier prices, the traffic or conversion metric a tier is priced on, limits, overage treatment, term lengths or VAT — the December invoice is a sales conversation, not a number I can compute. 3
The Product Engineer
The captured pages show a 14-day full-feature trial with cancel-anytime and an interactive builder preview with no signup, but we found no public information on tier prices, the traffic metric tiers are priced on, limits, overage treatment, module pricing, or seats. An annual invoice cannot be estimated from the public pages alone. 3
The CRO Consultant
A 14-day free trial with full feature access, a free builder start, and an interactive builder preview with no signup are public, and that is where the pricing evidence stops: we found no public information on tier prices, the traffic metric a client would be billed on, traffic limits, or what happens above them. Without a published traffic metric I cannot give a client even a rough annual estimate before the contract. 3 8
The Data Protection Officer
A fourteen-day trial with full feature access and a "start building for free" offer are the only pricing information on the captured pages. We found no public information on tier prices, the traffic metric a tier is priced on, limits, or what happens above them, so an annual cost cannot be worked out from public pages. 3
The Skeptic
Beyond a 14-day trial with full feature access and the ability to start building for free, the captured pages publish no tier prices, no traffic metric or its limits, and no overage, term or VAT information — the annual invoice is not computable from public pages. A trial is not a price. 3
European sovereignty — proven facts
0 of 4 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 |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Questions about Unbounce
Is Unbounce European?
Not determined: the vendor’s pages as captured do not say where Unbounce is based.
Where does Unbounce store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does Unbounce have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to Unbounce?
As of 21 Oct 2026, the panel rates GrowthBook (3.5/5), Convert Experiences (3.5/5) and Webtrends Optimize (3/5) highest among the other 31 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 Webtrends Optimize (UK / wider Europe). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Unbounce alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 13 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data residency. Not confirmed on the vendor’s own pages as captured.
- 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.
- 18 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
- 2 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
- 1 compliance 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 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 integrations 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 subprocessors 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 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (10)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page unbounce.com Checked 13 Oct 2026 Details →
- 2 Experiment types & delivery — found from sitemap unbounce.com Checked 13 Oct 2026 Details →
- 3 Experiment types & delivery — found from sitemap unbounce.com Checked 13 Oct 2026 Details →
- 4 Statistical method & guardrails — found from sitemap unbounce.com Checked 13 Oct 2026 Details →
- 5 Consent & visitor tracking — found from sitemap unbounce.com Checked 13 Oct 2026 Details →
- 6 Consent & visitor tracking — found from sitemap unbounce.com Checked 13 Oct 2026 Details →
- 7 Snippet performance & flicker — found from sitemap unbounce.com Checked 13 Oct 2026 Details →
- 8 Snippet performance & flicker — found from sitemap unbounce.com Checked 13 Oct 2026 Details →
- 9 Analytics, data export & integrations — found from sitemap unbounce.com Checked 13 Oct 2026 Details →
- 10 Analytics, data export & integrations — found from sitemap unbounce.com Checked 13 Oct 2026 Details →