A/B testing, analytics and SEO
A/B and split URL tests judged by sequential or Bayesian statistics, including on revenue per visitor. Web analytics with session replay and heatmaps, scheduled SEO audits, funnels and automation across every team. Run the test, see what converts, fix what doesn't and automate the wins.
Running their teams on Landing
What it replaces.
The testing tool, the SEO tool and the automation glue that holds everything else together. Replaced by one layer that can see every team's data.
Page and offer experiments.
Server and client-side tests.
Watching what visitors actually do.
Site audits and technical SEO.
Glue between separate tools.
Multi-step workflows.
A system you can tune.
Analytics deep enough to prove the result rather than argue about it, and the tools to act on what it shows.
A/B, split URL and multipage tests
Change pages in a visual editor or with code, target by page, device, location, source and behaviour, then ship the winner without a developer.
ScaleStatistics you choose per test
Sequential frequentist, safe to check every morning, or Bayesian on conversion and on revenue per visitor. Sample-ratio checks and false-positive control on secondary goals, so a lucky week doesn't become a redesign.
ScaleWeb analytics
Sessions, sources, UTM, funnels, cohorts and conversion tracking, plus a tag manager, on every page and form you publish.
Core and upAttribution to revenue
Which channel, campaign and page led to each order and deal, across email, social, search and ads.
Growth and upSEO crawler and site audits
Crawl your site for broken links, missing tags and slow pages, with PageSpeed and Search Console data alongside, fixes listed in order of impact and any finding turned into a task card in one click.
Growth and upFunnels and automation
Funnel playbooks and cross-team workflows that act on what the numbers show, with an activity log of every run.
Growth and upBuilt by people who read the statistics.
The testing engine goes further than most dedicated testing tools, and it sits on the same record as your orders and deals.
Sequential testing, safe to peek
The frequentist method is always valid, so checking results every morning doesn't inflate false winners. Sample size and duration estimates before you launch.
Bayesian on conversion
Probability to beat the control and expected loss for every variation, in plain numbers anyone on the team can read.
Bayesian on revenue per visitor
Models whether people buy and how much they spend, so the expected gain and the risk of shipping a variation are shown in pounds, with an honest "too close to call".
Sample-ratio mismatch checks
Flags a broken traffic split before you trust the result, and re-baselines when you change the split on purpose.
False-positive control
Corrects for testing many secondary goals at once, so ten goals don't hand you a winner by chance.
Split URL, multipage and A/A tests
Redirect tests between whole pages, tests that run across a journey, and A/A tests to prove your setup before it matters.
Consent gating
Tests wait for consent through Google Consent Mode, Convert's consent signal or your own banner, and Global Privacy Control counts as a no.
Preview without the flicker
A preview that follows you from page to page with a QA banner, and never counts as traffic. Live tests load through a snippet that hides the page until the change is applied, with a timeout so a slow network never blanks your site.
Reach estimates and auto-stop
See how many of last month's visitors an audience would have matched before you launch, and let a test stop itself overnight once a winner is significant.
The Convert importer
Tests, variations, goals, audiences and locations come across with images re-hosted, and Convert's own code keeps running. Imports stay switched off until you put them live.
Session replay and heatmaps
Recordings plus click, move and scroll heatmaps inside your analytics, with inputs masked, recording gated on consent and JavaScript errors rolled up. No separate Hotjar.
Test to revenue, not to a form fill.
Optimisation measures what the other teams produce. Because it sits on the same record, a test can be judged on the deals it wins and the orders it brings, not just the clicks.
Which plan unlocks what.
Measurement is in every plan. Attribution, audits and automation come with Growth. Experiments and visitor identification come with Scale.
Core
£29 per Builder · £4 per Member a month
- UTM and conversion tracking
- A tag manager
- Reports on every page, form and email
- Web analytics, funnels and cohorts
Growth
Most teams£69 per Builder · £6 per Member a month
- Everything in Core, plus
- Attribution to revenue
- Scheduled SEO audits
- Playbooks that run across every team
- Session replay and heatmaps
- Dashboards that refresh themselves
Scale
Yearly£119 per Builder · £9 per Member a month
- Everything in Growth, plus
- A sandbox to try changes
- A named manager and same-day fixes
- Website visitor identification
- A/B testing with Bayesian and sequential stats
A three-person growth team on Scale. Three people run tests, audits and reporting as Builders. Everyone else sees the dashboards they share.
One plan for the whole company. Every product is in every plan, and the plan decides how far each one goes. Prices ex VAT.
Work out your priceQuestions growth teams ask.
Anything else, ask us on the demo. We'll have your price worked out before you hang up.
Is Optimisation a separate product?
No. It's the layer across the other six, and it's in the price. Web analytics is on every plan, attribution and automation on Growth, and testing on Scale.
How are experiments judged?
On the goal you choose, including orders and deals rather than just clicks. You pick the method per test: sequential frequentist, which stays valid however often you look, or Bayesian on conversion or on revenue per visitor, which shows the expected gain and the risk in pounds. Sample-ratio checks and false-positive control on secondary goals run before a winner is called.
Can we move tests over from Convert or VWO?
Yes. Convert tests import directly: variations, goals, audiences and locations, with images re-hosted and a compatibility layer so Convert's own code runs unchanged. Everything imported stays switched off until someone on your team chooses to put it live. Landing vs Convert.
Does automation replace Zapier entirely?
For work between Landing's own teams, yes: there's nothing to connect because it's one record. And a playbook can call any other tool by webhook, with no per-task meter running.
Bring a test you've been meaning to run.
Thirty minutes on what you measure today and what you'd test first, with your price worked out before you hang up.