Platform · Learnings
Every test makes the next one smarter
Learnings reads every finished test on your website, finds what they show together and suggests what to test next. Code computes every number. The AI only puts the findings into words.
Knowledge that compounds
What your tests already know
A card for every finished test, patterns pooled across them, a map of what has never been tried, and a chat that answers from your own evidence.
- A learning card for every finished test: what changed, what it taught and whether the hypothesis held
- Patterns across tests, each with an honest evidence level
- Statistics adjusted for the many patterns checked at once, so a lucky streak is not presented as a rule
- Opportunities that open as a pre-filled draft experiment in one click
- Answers drawn from your own tests, never from generic best practice
Learning cards
One card per test, written when it ends
When a test concludes, Pertento reads the changes each variant actually made and writes a short card about it. The team’s own debrief sits beside it, always labelled as the team’s view, so a reading of the result is never mistaken for the result.
- Each variant described in plain words, read from the changes made in the test
- The outcome, and what the test taught in one sentence
- Whether the hypothesis held: supported, contradicted, or the test says nothing either way
- A possible reason and a suggested next test
Patterns
What several tests show together
A single test proves very little. Pertento pools the tests that share something, such as the same kind of change on the same page, reports what they show together, and says how far that is worth trusting.
- Five evidence levels: consistent across three or more tests, early signal, small effect, not enough evidence yet, or mixed
- When two patterns are really the same tests seen twice, it says so instead of counting extra proof
- Tests with a known problem, such as a tracking issue, are left out unless you include them
- Filter by device to see what works on mobile on its own
Evidence
What has been tested where, and what never has
The Evidence view lays every page type against every type of change. Each cell carries the pooled lift and the number of tests behind it, and an empty cell is ground nobody has tested yet.
- Page types against change types: layout, copy, navigation, trust, forms and more
- A cell resting on one test is marked as one, so a lone result never reads as a trend
- Every combination nobody has tried, listed as a gap
- Each test labelled by change type, page, element and expected mechanism
Opportunities
From result to next test in one click
The evidence raises questions, and Opportunities turns each one into a concrete next test. Draft experiment, after a confirmation, creates a new draft that already carries the reasoning, so nobody has to rebuild it from memory.
- Grouped by purpose: explain a surprise, replicate, resolve a mixed picture, isolate, or fill a gap
- The draft opens with the hypothesis and the expected mechanism already written
- Page targeting taken from the tests behind it
- Links to the evidence, and the current estimate as the baseline to beat
Ask about your learnings
Put a question to your own evidence
A chat built into the Learnings page answers in plain language from this website’s tests and nothing else. Every claim names the tests it rests on, and each reference opens that test’s details.
- Ask “What hurts sign-up?” or “What should we test next?”
- It looks up a test’s measured results when a question needs real figures
- The conversation is shared with the team and saved
- Ask about this experiment, on every experiment page, now knows what earlier tests showed as well
Foundation check
Learnings are only as good as the tests behind them
The foundation check shows how well past tests were documented: a clear hypothesis, an expected mechanism, a debrief. Better documentation means sharper learnings, and the check nudges the team towards better testing habits.
- Hypothesis, description, mechanism and debrief, checked for every test
- A gap marked missing, or weak when boxes were ticked and nothing was written
- Fix opens the test where the gap is
- Writing learnings for past tests is a separate step that shows its cost first
Built not to overclaim
Learnings you can trust
This is a product that says “not enough evidence yet” rather than oversell a result. These are the rules that keep it honest.
Code computes every number
Lifts, ranges and evidence levels are computed by code from the measured results. The AI reads those figures and puts them into words. It never produces a number of its own.
Cautious by design
The statistics are deliberately sceptical, so a pattern has to earn its evidence level rather than be handed one by a single good result.
Adjusted for many checks at once
Checking dozens of patterns at the same time makes a few of them look strong by luck alone. The ranges are adjusted for that, so a lucky streak is not presented as a rule.
The same tests are not counted twice
When two patterns rest on the same tests, Pertento says so, instead of presenting one result seen from two angles as two pieces of proof.
Problem tests left out
A test with a known problem, such as a tracking issue or a site release during the run, is left out of the pooling. The team can choose to include it anyway.
Honest about a small programme
It works with a few tests and becomes more useful with every one that finishes. With only a few, it says how little they can prove rather than stretching them into a strategy.
Running it
How it fits your programme
Learnings is switched on per website, reads only that website’s tests, and is paid for in the account’s AI credits.
Off until you switch it on
Learnings is opt-in per website and off by default. Once it is on, it covers every test that finishes from then on.
Past tests, when you choose
Writing learnings for tests that finished earlier is a separate step you confirm, and it shows what it will cost before it runs.
Your own evidence only
Everything comes from that website’s own tests, never from generic best practice. An agency’s clients each keep their own learnings, separate from one another.
One record for the whole team
Cards, patterns and the conversation in Ask about your learnings are shared and saved, so what the programme has learned survives people moving on.
Tell it what you already knew
Mark a pattern as already known or not useful, and the page adapts to what your team has told it.
Paid for in AI credits
Writing cards, Ask about your learnings and the experiment chat use the account’s AI credits. Accounts not billed by card have a monthly AI allowance instead.
Questions
Before you switch it on
How is this different from asking a chatbot about our results?
In two ways. The numbers are not the AI’s: lifts, ranges and evidence levels are computed by code and adjusted for the number of patterns checked at once, and the AI only describes them. And the answers come only from this website’s own tests, with every claim naming the tests it rests on, so you can open each one and check. A general-purpose assistant can sound confident about anything. This one is built to say “not enough evidence yet” when that is the honest answer.
Will it tell us which variant is going to win?
No, and it is built not to. It summarises the evidence your finished tests produced and suggests what to test next. It does not predict winners or guarantee a result, and when the evidence is weak it says so in as many words.
We have only run a handful of tests. Is it worth switching on?
It works with a few, and it is honest about how little a few tests can prove: most patterns will read as an early signal or as not enough evidence yet, which is the correct reading. The value grows with every test that finishes. The foundation check and Opportunities are useful from the start, because they show what to document better and what to test next.
Does it learn from other companies’ tests?
No. Learnings is strictly per website: it reads that website’s tests and nothing else, and it does not compare you with other sites or with an industry benchmark. For an agency, each client’s learnings are kept separate.
What does it cost?
It uses the account’s AI credits: writing learning cards, Ask about your learnings and the experiment chat all draw on them. It is off by default, and once switched on it covers tests that finish from then on. Writing learnings for past tests is a separate step that shows its cost before you confirm it. Accounts not billed by card have a monthly AI allowance instead.
What language are the learnings written in?
English. Learning cards, patterns and opportunities are written in English, whichever language your team reads this page in.
Everything in the box
The full feature set
Experimentation
- Visual multi-variant tests
- URL redirect tests
- Server-side tests
- No-code visual editor
- AI editor
- Chrome extension launcher
- Component library
- Dynamic content
- Data feeds
- Custom CSS and JS
- Replace, insert, append, before and after
- URL targeting on seven conditions
- Device targeting
- Cookie targeting
- Activation targeting
- Traffic weights per variant
- Automatic weight rebalancing
- Concurrent tests without splitting traffic
- Variant screenshots
- Duplicate an experiment
- Test runs before launch
- Sticky variant assignment
- Anti-flicker rendering
- One-click winner deployment
- Implementation hand-off
- Hypothesis tracking
- PXL prioritisation scoring
- Run length plan
- Pipelines of staged experiments
- Library search, filter and results
- Library timeline
Statistics
- Frequentist results
- Bayesian results
- Lift and confidence intervals
- Probability variant is best
- Expected loss
- Sequential testing
- Multiple-comparison correction
- Holm-Bonferroni, Benjamini-Hochberg and Šidák
- Sample-ratio-mismatch alarms
- Primary and secondary goals
- Revenue per variant
- Average order value per variant
- Multi-currency
- Power analysis
- Minimum detectable effect
- Days-remaining projection
- Combination reporting
- Per-variant time series
- Plain-English explainers
- Ask about this experiment
Monitoring
- Health monitor
- Attention queue across accounts
- Program report
- Experiment debrief
- Scheduled starts and stops
- Stop on significance
- Minimum runtime guard rails
- Trust gates on broken data
- Collision detection
- Interaction detection
- Overdue and no-data alarms
- Email alerts
- Slack alerts
- In-app alerts
- Per-event preferences
- Activity log
- Client roster view
- Saved console layouts
- GA4 and Matomo tracking
- Roles and permissions
Voice of customer
- On-site NPS
- CSAT
- CES
- Custom surveys
- Guided survey builder
- Score, choice and text questions
- Custom texts and scale labels
- Page and device targeting
- Share of visitors
- Page-view and delay triggers
- Exit-intent triggers
- Scroll triggers
- Event triggers
- Four widget positions
- Frequency capping
- Per-question results
- Responses over time
- AI sentiment analysis
- Surveys inside experiments
- Results by variant
- Answers tied to variant
- Validated responses
- Free-text themes
- Response export
- Loaded only where a survey runs
Learnings
- Learning cards
- Patterns across tests
- Five evidence levels
- Adjusted for multiple comparisons
- Same-test patterns merged
- Problem tests left out
- Results by device
- Evidence grid
- Opportunities
- Draft experiment
- Ask about your learnings
- Foundation check
- Mark as known or not useful
Pertento is a conversion-rate-optimisation platform for websites and online stores, built for both in-house teams and CRO agencies running experimentation programmes across a client roster.
Integrations
Works with the stack you already run
One snippet drops into any site, or go fully server-side. Nothing to re-architect.
One-line snippet
Paste one tag in your head and you are live: a 0.9 KB loader, no build step, no dependencies.
Google Tag Manager
Deploy and manage experiments straight through GTM. No developer time required.
Server-side API
Run tests beyond the browser: pricing, search and routing, flicker-free.
- Shopify
- BigCommerce
- Shopware
- Centra
- Geins
- Saleor
- WordPress
- Optimizely CMS
- Storyblok
- Next.js
- Vue
- Astro
- Matomo
- Amplitude
- RudderStack
- Slack
- WooCommerce
- Salesforce
- Wix
- Litium
- commercetools
- Medusa
- Drupal
- Contentful
- Webflow
- Nuxt
- Angular
- Remix
- Piwik PRO
- Mixpanel
- Tag Manager
- Webhooks
- Adobe Commerce
- PrestaShop
- Squarespace
- Norce
- Shopify Hydrogen
- Vendure
- Umbraco
- Sanity
- Framer
- React
- SvelteKit
- GA4
- Adobe Analytics
- Segment
- Klaviyo
Not on the list? If it renders HTML, Pertento can test it:read how each one connects.