Conversion Optimization
Leadpages
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Leadpages · www.leadpages.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.
Leadpages at a glance
- Vendor
- Leadpages
- Headquarters
- Not stated on the vendor’s pages as of 3 Nov 2026
- Data hosting
- Outside the EU by default source, captured 3 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 3 Nov 2026
- Starting price
- “Starting Price $49/mo” (vendor’s words) source, captured 3 Nov 2026
- Panel verdict
- The AI panel rates Leadpages 2/5, the mean of 6 judges. Leadpages is an AI landing page builder and conversion optimization platform whose tests run on pages published from its own editor. how scores are made
- As of
- Vendor pages captured 3 Nov 2026; evaluated by the panel 4 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Leadpages is an AI landing page builder and conversion optimization platform whose tests run on pages published from its own editor. The bench scores it highest on performance impact, pricing transparency and data and integrations: variants are assigned server-side before the page renders, delivery runs through Cloudflare over TLS 1.3, and three tiers are priced publicly — Grow $99/mo, Optimize $199/mo, Scale $399/mo — with no visitor caps and no overage fees on any plan. Experimentation scope scores 4-5 and statistical rigour 4: A/B/C/D tests with custom splits and a named method (two-proportion z-test with Bonferroni correction) are documented, but we found no public information on experiments outside the vendor's editor. The weakest scores are consent and tracking and sovereignty (1): the contracting entity is Leadpages (US), Inc., the privacy policy states personal data is processed outside the EEA and UK, including in the United States, and the cookie and GDPR pages read "Coming Soon". The flagged splits show nothing notable, and weighted totals span 2.7 to 4.4.
Speaks for it
- Variants are assigned server-side before the page renders — the vendor states there is no snippet and nothing flickers — with delivery through Cloudflare over TLS 1.3
- Grow at $99/mo, Optimize at $199/mo and Scale at $399/mo are priced publicly, with no visitor caps and no overage fees on any plan
- The testing method is published by name: a two-proportion z-test with Bonferroni correction, reported in three confidence bands
- GA4 and Google Tag Manager integrations are documented in detail — automatic page views, custom and e-commerce events, UTM passthrough — alongside webhooks, Zapier to 6,000+ apps and an API using OAuth 2.0
- A/B/C/D tests with 50/50, 70/30 or custom traffic splits and personalisation rules on ad source, device, location, time of day and CRM stage are documented
Held against it
- Sovereignty scores sit at 1: the contracting entity is Leadpages (US), Inc., the privacy policy states processing outside the EEA and UK including the United States, and we found no public information on a transfer safeguard or data processing agreement
- The cookie page and the GDPR compliance page are both marked "Coming Soon", and the vendor states it is unable to respond to Do Not Track signals
- Testing runs only on pages published from the vendor's editor, and we found no public information on split-URL or multivariate tests or a server-side SDK for a customer's own stack
- Confidence is reported in three bands, and we found no public information on sample-size guidance, protection against peeking, or sample ratio mismatch detection
- The Business tier carries no published price, seat counts are not stated, and the captured pages give different figures for the custom domains included per plan
Best for
- You run paid campaigns to landing pages and want a published monthly price with no visitor caps and no overage fees
- Flicker-free delivery matters to your conversion rate: the variant is decided server-side before the page renders on pages the platform hosts
- You push results into GA4 and Google Tag Manager and out via webhooks without manual tag setup
Avoid if
- You need EU data residency, a data processing agreement or a documented transfer safeguard; the privacy policy states processing outside the EEA and UK, including in the United States, and the GDPR page is marked "Coming Soon"
- Your testing programme must run on your own site or stack rather than pages published from the vendor's editor
- Your compliance review needs documented consent sequencing and a cookie list; the cookie page reads "Coming Soon" and the vendor states it is unable to respond to Do Not Track signals
The scores
| Criterion | Panel median |
|---|---|
| Experiment types & delivery | 2.5 of 5 |
| Statistical method & guardrails | 2 of 5 |
| Consent & visitor tracking | 1 of 5 |
| Snippet performance & flicker | 3 of 5 |
| Analytics, data export & integrations | 2.5 of 5 |
| European sovereignty | 0.5 of 5 |
| Pricing transparency | 3 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
Multi-variant testing (A/B/C/D, four variants per test) with 50/50, 70/30 or custom splits, goals from form submissions to purchases, and server-side assignment before render is documented, alongside rule-based personalisation targeting ad source, device, country and time of day — targeting that goes well beyond the URL. But everything runs inside the Leadpages editor on pages Leadpages publishes, and we found no public information on split-URL tests, multivariate tests or server-side experiments through an SDK. 5 6
The E-Commerce Manager
A/B tests with up to four variants, custom traffic splits, three testing modes, and rule-based personalisation on ad source, device, location, time of day and CRM stage are all documented, with the variant assigned server-side before render. I found no evidence of multivariate tests, a server-side SDK for my own stack, holdouts, or personalisation that can itself be tested against a control — Smart Traffic shifts traffic automatically, which is optimisation, not proof. 5 6
The Product Engineer
A/B tests with up to four variants, three testing modes including an automated optimisation loop, custom traffic splits and per-page conversion goals all run inside the visual page builder, with rule-based personalisation on ad source, device, geography and CRM stage. What caps it for me is the closed model: variants are decided on pages the platform itself hosts, and I found no public information on server-side SDKs for our own stack, multivariate or split-URL tests, holdouts or mutually exclusive groups. 5 6
The CRO Consultant
A/B and multi-variant tests (up to A/B/C/D with 50/50, 70/30 or custom splits) are built straight into the page editor with no developer required, and rule-based personalisation targets visitors by ad source, device, geography, day and time, and even CRM stage from HubSpot or Salesforce, with Smart Traffic machine-learning allocation on the upper plans. Everything runs only on landing pages published from the vendor's own editor, though, and I found no public information on split-URL or multivariate tests, feature flags, or a documented SDK for server-side experiments on a customer's own site. 5 6
The Data Protection Officer
A/B tests with up to four variants and configurable traffic splits are built into the page editor, with three documented testing modes including a continuous optimisation loop, and personalisation rules on ad source, device, geography, time of day and CRM lifecycle stage. We found no public information on multivariate testing, on SDKs for running experiments on the customer's own stack, or on mutually exclusive experiment groups or holdouts. 5 6
The Skeptic
A/B tests with up to four variants, custom traffic splits, conversion goals from form submissions to offsite conversions, rule-based personalisation on ad source, device, location and time of day, and an automated optimization loop on the top plan are all documented. We found no public information on multivariate or split-URL tests, server-side SDKs for the customer's own stack, mutually exclusive experiment groups or holdouts. That places it above a basic editor split test but well below a full experimentation programme. 5 6
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
The method is named in writing — a two-proportion z-test with Bonferroni correction, reported in three confidence bands — which is a frequentist approach I can actually defend when finance asks how the winner was called. For the board pack I would be missing the rest: we found no public information on sample-size or duration guidance, protection against peeking, sample ratio mismatch detection or guardrail metrics. 5
The E-Commerce Manager
The vendor names its method — a two-proportion z-test with Bonferroni correction, reported in three confidence bands — which is more than most landing-page tools publish. I found no sample-size or duration guidance, no intervals per variant, and nothing on peeking or sample ratio mismatch, and the continuous optimisation loop on the top plan runs unattended. 5 6
The Product Engineer
The vendor names its method — a two-proportion z-test with Bonferroni correction — and reports confidence in three bands, which is more method disclosure than most page builders give. I found no public information on protection against peeking, sample ratio mismatch detection, variance reduction, guardrail metrics, or a sample-size or duration calculator. 5
The CRO Consultant
The method is named and frequentist — a two-proportion z-test with Bonferroni correction across variants, reported in three confidence bands — so a client can at least see how a winner is declared. The banding hides the underlying numbers, and I found no public information on sample-size or test-duration guidance, protection against peeking, sample ratio mismatch detection, or guardrail metrics that could stop a harmful test. 5
The Data Protection Officer
The method is published by name: a two-proportion z-test with Bonferroni correction, reported in three confidence bands. We found no public information on confidence intervals per variant, sample-size or duration guidance, protection against peeking, or sample ratio mismatch detection. 5
The Skeptic
To the vendor's credit, the method is named precisely — a two-proportion z-test with Bonferroni correction across the up-to-four variants — which is more than most tools in this category publish. But confidence is reported in three bands rather than intervals per variant, and we found no public information on sample-size guidance, protections against peeking, or sample ratio mismatch detection. Without those guardrails a customer can still read an early look as a winner. 5
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 pages dedicated to cookies and to GDPR are both marked "Coming Soon", and the privacy policy states the vendor is unable to respond to Do Not Track signals — so I have nothing to hand our data protection officer about when the test script runs relative to consent or what it stores on the device. We found no public information on a cookieless mode, a list of storage keys, or integration with a consent management platform. 2 7 8
The E-Commerce Manager
The cookies page and the GDPR page are both marked "Coming Soon", and the privacy policy states the vendor is unable to respond to Do Not Track signals, so I cannot see when tracking begins relative to consent or which storage keys the pages set. An EEA/UK section with legal bases and a DPO contact exists, but no consent-pending mode or cookieless option appears on the captured pages. 2 7 8
The Product Engineer
The privacy policy states legal bases and has an EEA/UK section, but the cookie page and the GDPR page both read "Coming Soon", and the vendor states it cannot respond to Do Not Track signals while participating in interest-based advertising. I found no public information on holding tracking until consent, a cookieless mode, or a published list of cookies and storage keys with their lifetimes. 2 7 8
The CRO Consultant
The privacy policy carries an EEA and UK section with stated legal bases and a named Data Protection Officer contact, and mentions cookie preference management, but both the cookie page and the GDPR page read "Coming Soon" and the vendor states it is unable to respond to browser Do Not Track signals. I found no public information on a list of cookies and storage keys, consent-management-platform integration, or guidance on the legal basis for testing under §25 TDDDG — this is not a story a client's DPO can sign off today. 2 7 8
The Data Protection Officer
The GDPR compliance page and the cookie policy are both published as "Coming Soon", and we found no public information on when tracking runs relative to the consent banner, on any consent-pending mode, or on the cookies and storage keys set on the visitor's device. The privacy policy states that personal data is disclosed to third-party analytics providers and marketing companies and that the vendor is unable to respond to Do Not Track signals, which makes the missing documentation on consent sequencing the deciding fact here. 2 7 8
The Skeptic
The privacy policy states its legal bases and carries an EEA and UK section, but the page that would document cookies and similar tracking technologies promises preference management while its content is marked "Coming Soon", and the vendor writes that it cannot respond to Do Not Track signals. We found no public information on when tracking runs relative to consent, which storage keys are set, or any consent-pending or cookieless mode. 2 7 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
Because pages are built and published in the product itself — "no second tool, no snippet, no tag manager" — variant assignment happens server-side before the page renders, which the vendor states eliminates flicker, and delivery runs through Cloudflare's global CDN. That is an architectural answer rather than a measured one: we found no public information on published performance figures, Core Web Vitals impact, or tooling showing what a configuration costs the page. 3 5 6
The E-Commerce Manager
Flicker is handled where it matters to me: the variant is decided server-side before the page renders, pages are delivered through Cloudflare, and no second snippet or tag manager is added to the page. I found no published figures for load cost or Core Web Vitals, so the no-flicker claim rests on the architecture rather than on measurement. 3 5 6
The Product Engineer
There is no client snippet to weigh: the vendor states the variant is decided before the page renders so nothing flickers, pages are delivered through Cloudflare with TLS 1.3 and free SSL on custom domains. That is the architecture I'd want for flicker-sensitive work; what is missing is any published measurement of overhead or the effect on Core Web Vitals. 3 5 6
The CRO Consultant
There is no client-side snippet to weigh down the customer's page at all: the variant is assigned server-side before the page renders — in the vendor's words, "nothing flickers" — and pages are served through Cloudflare over TLS 1.3. That removes the blocking and flicker problem by architecture, but only for pages hosted on the platform, and I found no published measurements of Core Web Vitals impact, no self-hosting option, and no tooling that shows what a given configuration costs the page. 5 6 3
The Data Protection Officer
Variant assignment happens server-side before the page renders, the vendor states there is no second tool, no snippet and no tag manager, and all pages are delivered through the Cloudflare CDN over TLS 1.3, so flicker is handled by architecture rather than a client-side workaround. We found no public information on measured performance figures, Core Web Vitals impact, or script weight. 5 6 3
The Skeptic
The captured pages state there is no snippet at all — variants are assigned server-side "before the page renders, so nothing flickers", and pages are delivered through Cloudflare over TLS 1.3, which answers the flicker question by architecture rather than by a timeout trade-off. But we found no public figures on load cost, script weight or Core Web Vitals impact, so the performance story rests on description, not measurement. 3 5 6
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
GA4 and Google Tag Manager integrations are documented in real detail — automatic page views, custom and e-commerce events, UTM passthrough, container autoload and preview mode — alongside webhooks, Zapier with 6,000+ apps, HubSpot, WordPress and an API & Developers offering, with analytics retention stated per tier. Before I sign, I would want more on getting raw data out: the only warehouse mention is a "36 mo + data warehouse" line on the top plan, and we found no public information on visitor-level raw data export or stated API limits. 6 9 10 11
The E-Commerce Manager
GA4 with automatic page views plus custom and e-commerce events, a Google Tag Manager container that loads on every page, real-time webhooks, Zapier and an OAuth-secured API are all documented, and conversion data flows back to the ad platforms. I found no public information on visitor-level raw export or stated API limits, and warehouse access appears only as a feature line on the top plan. 3 9 10 11
The Product Engineer
GA4 with page views, custom and e-commerce events, Google Tag Manager with container autoload and triggers, real-time webhooks for form data, Zapier and a documented API using OAuth 2.0 and Bearer tokens cover getting results out to the tools we already run. I found no public information on visitor-level raw data export or warehouse-native analysis — the only warehouse mention is "Analytics (36 mo + data warehouse)" on the Scale plan, unexplained. 3 9 10 11
The CRO Consultant
GA4 page views, custom and e-commerce events and UTM passthrough work without manual tag setup, a GTM container can load on every published page with triggers on forms and clicks, form data streams out in real time over webhooks, and there is a developer API authenticated with OAuth 2.0 plus a Zapier bridge to 6,000+ apps. I found no public information on visitor-level export of experiment results, warehouse-native analysis (the Scale plan's analytics line mentions a data warehouse without saying what that means), or stated API rate limits — so results can be pushed to GA4, but re-checking the raw result in the client's own data is not something the pages show. 10 11 3 9
The Data Protection Officer
Documented integrations with Google Analytics 4 (automatic page views, custom and e-commerce events, UTM passthrough) and Google Tag Manager, real-time webhooks for form data, an API and Developers offering with OAuth 2.0, Zapier and MCP endpoints cover the analytics and tag-management path. We found no public information on export of visitor-level experiment results or warehouse-native analysis of a customer's own metrics. 10 11 9
The Skeptic
GA4 and Google Tag Manager integrations are documented in real detail — automatic page views, custom and e-commerce events, UTM passthrough, container autoload — alongside webhooks for form data, Zapier, an API behind OAuth 2.0, and MCP endpoints. The weak point is getting results out: we found no public information on visitor-level raw data export or warehouse streaming beyond a retention line mentioning a data warehouse on the top plan. 3 4 9 10 11
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where visitor data is processed and stored and who the contracting entity is. Independently sourced by the sovereignty pipeline; weighted higher here than in categories that hold only the customer's own data, because the script runs on every visitor to the customer's site and their behaviour is what the platform records.
0 — Vendor, contracting entity and processing of visitor data all shown to be outside the EU, with no transfer safeguard stated.
3 — A named contracting entity and a privacy policy or data processing agreement; EU data residency offered as an option or add-on, or the hosting location not stated.
5 — EU hosting or EU processing of visitor data stated as standard, together with an EU contracting entity or a published subprocessor list, and a data processing agreement offered.
8 — EU contracting entity, EU hosting on named infrastructure including the delivery of the snippet, a subprocessor list published with locations, and a data processing agreement covering the visitor data the script collects.
10 — Sovereign end to end and evidenced: vendor, entity, hosting, snippet delivery and every subprocessor European, certification published, and no visitor data reaching a non-EU party at any point.
The Growth Lead
The contracting entity is Leadpages (US), Inc. with a Minneapolis address, and the privacy policy states that personal data is processed outside the EEA and UK, including in the United States, with hosting on AWS and Cloudflare. The GDPR page that would carry DPA and subject-rights information is marked "Coming Soon", and we found no public information on an EU hosting option, a published subprocessor list or a transfer safeguard for visitor data. 2 3 7
The E-Commerce Manager
The contracting entity is Leadpages (US), Inc. with a DPO address in Minneapolis, the privacy policy states personal data is processed outside the EEA and UK including in the United States, and the platform runs on AWS and Cloudflare. No EU residency option, transfer safeguard or data processing agreement appears on the captured pages, and the GDPR page says "Coming Soon". 2 3 7
The Product Engineer
The contracting entity is Leadpages (US), Inc., the privacy policy states that personal data is processed outside the EEA and UK including in the United States, and the infrastructure is AWS and Cloudflare with no EU region named. I found no public information on a transfer safeguard or a data processing agreement, and the GDPR page itself says "Coming Soon". 2 3 7
The CRO Consultant
The contracting entity is Leadpages (US), Inc. of Minneapolis, and the privacy policy states that personal data is processed outside the EEA and UK, including in the United States, with the security page naming AWS and Cloudflare as the infrastructure. I found no public information on a data processing agreement — the GDPR page says "Coming Soon" — on a published subprocessor list, or on any transfer safeguard; for EU clients this is the deciding exposure, since the platform records the behaviour of every visitor to the customer's pages. 2 3 7
The Data Protection Officer
The contracting entity is Leadpages (US), Inc. with a data protection officer address in Minneapolis, and the privacy policy states that personal data is processed outside the EEA and UK, including in the United States, on AWS infrastructure fronted by a Cloudflare CDN — so visitor data is not processed in the EU. We found no public information on EU hosting options, a published subprocessor list covering the CDN, or a data processing agreement, with the GDPR page itself marked "Coming Soon". 2 3 7
The Skeptic
The contracting entity is Leadpages (US), Inc. and the privacy policy states "We process personal data outside of the EEA and UK, including in the United States", on AWS infrastructure with no region named and no transfer safeguard stated anywhere in the captured pages. The page that would carry GDPR compliance and DPA information is marked "Coming Soon". A US entity with stated US processing and no published safeguard sits at the bottom of this scale, softened only by the policy's EEA and UK disclosures. 2 3 7
Pricing transparency
Show reasoningHide reasoning
How this is scored
A category priced by traffic — monthly tracked users, visitors or impressions — where the tier a site lands in depends on numbers the buyer has to estimate. Whether a buyer can compute the real annual cost including traffic limits, overage, server-side or personalisation modules and seats — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price, a free tier or one priced tier, while the other tiers or the traffic metric behind the price are not stated.
5 — Prices public per tier with the billing period and the traffic metric (tracked users, visitors or impressions) and its limits stated; modules such as server-side SDKs or personalisation, or overage, may still be "contact sales".
8 — Every tier and module priced publicly with the traffic metric defined, limits, overage rates, seats, minimum term and VAT treatment stated.
10 — Complete price computability: annual invoice derivable for a given traffic volume, set of modules and team size, with overage and every add-on published.
The Growth Lead
Grow, Optimize and Scale are priced publicly at $99/mo, $199/mo and $399/mo with a capability matrix per tier, unlimited traffic with no overage fees, and monthly quotas for Visitor Intelligence and IP resolutions stated — the traffic-estimation game that makes this category hard to budget is largely absent. Gaps remain: the Business tier price is not stated, the captured pages give different figures for the custom domains included per tier, and we found no public information on seats, minimum term or VAT treatment. 5 6 9
The E-Commerce Manager
Three tiers are priced publicly — Grow at $99/mo, Optimize at $199/mo and Scale at $399/mo, from a starting price of $49/mo — and traffic is unlimited with "no visitor caps and no overage fees on any plan", which is exactly the December-proof pricing I want; the metered item is Visitor Intelligence at 1,000 to 10,000 resolutions per month. I found no public information on the Business tier's price, seats, minimum term or VAT treatment, and the captured pages give different custom-domain counts for the same plans. 5 6 9
The Product Engineer
Three tiers are priced publicly at $99/mo, $199/mo and $399/mo with features allocated per tier and a stated starting price of $49/mo, and the vendor states unlimited traffic with no caps and no overage fees on any plan — which removes the traffic-estimating guesswork that plagues this category. The Business tier in the capability table carries no price, seats and VAT treatment are unstated, and the captured pages give different figures for custom domains per tier. 5 6 9
The CRO Consultant
Three plans are priced publicly — Grow at $99/mo, Optimize at $199/mo and Scale at $399/mo, alongside a $49/mo starting price — with "Unlimited traffic" and "no visitor caps and no overage fees on any plan", so the traffic-estimation gamble that defines this category simply does not arise, and personalisation is priced into the tiers rather than sold as a module. The Business tier's price is not shown, I found no public information on seats, minimum term or VAT treatment, and the captured pages give different figures for how many custom domains each plan includes. The Visitor Intelligence quotas of 1,000 to 10,000 resolutions per month are at least stated per tier. 9 6 5
The Data Protection Officer
Grow at $99/mo, Optimize at $199/mo and Scale at $399/mo are public with monthly billing, unlimited traffic with no overage fees, and stated per-tier Visitor Intelligence quotas, which removes the traffic-estimation problem. We found no public information on the Business tier price in the capability comparison, seat counts, VAT treatment or minimum term, and the captured pages give different figures for the custom domains included per plan. 6 9 5
The Skeptic
Three tiers are priced publicly — Grow $99/mo, Optimize $199/mo, Scale $399/mo — with "Unlimited traffic No visitor caps and no overage fees on any plan" and the metered Visitor Intelligence quotas listed per tier. But the Business tier appears in the comparison without a price, seats, minimum term and VAT treatment are not stated, and the captured pages give different figures for custom domains on Grow (10 versus 25), so an exact invoice still needs confirmation with the vendor. 5 6 9
European sovereignty — proven facts
1 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 | Outside the EU ⚠ unverified | 0/4 pts | 2 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 Leadpages
Is Leadpages European?
Not determined: the vendor’s pages as captured do not say where Leadpages is based.
Where does Leadpages store data?
Leadpages stores customer data outside the EU by default, per the vendor’s page captured 3 Nov 2026.
Does Leadpages have a free plan?
Not stated on the vendor’s pages as of 3 Nov 2026.
What are the best alternatives to Leadpages?
As of 4 Nov 2026, the panel rates GrowthBook (3.5/5), Varify.io (3/5) and AB Tasty (3/5) highest among the other 37 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). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Leadpages alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 3 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location. The statement concerns processing of personal data and is hedged with "may be", and the security page names AWS Aurora and Cloudflare R2 as storage without naming a region, so no default hosting region for business customers' data is explicitly stated.
- 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.
- 53 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
- 12 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
- 8 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
- 4 legal 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 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 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 (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.leadpages.com Checked 3 Nov 2026 Details →
- 2 Privacy policy — found from the homepage leadpages.com Checked 3 Nov 2026 Details →
- 3 Security / trust page — found from the homepage leadpages.com Checked 3 Nov 2026 Details →
- 4 Code repository (open-source licence) — found from the homepage github.com Checked 3 Nov 2026 Details →
- 5 Experiment types & delivery — found from sitemap leadpages.com Checked 3 Nov 2026 Details →
- 6 Experiment types & delivery — found from sitemap leadpages.com Checked 3 Nov 2026 Details →
- 7 Consent & visitor tracking — found from sitemap leadpages.com Checked 3 Nov 2026 Details →
- 8 Consent & visitor tracking — found from sitemap leadpages.com Checked 3 Nov 2026 Details →
- 9 Snippet performance & flicker — found from sitemap leadpages.com Checked 3 Nov 2026 Details →
- 10 Analytics, data export & integrations — found from sitemap leadpages.com Checked 3 Nov 2026 Details →
- 11 Analytics, data export & integrations — found from sitemap leadpages.com Checked 3 Nov 2026 Details →