A version is what one part of your pages says to one segment: for example, the hero’s headline for retailers. In a Personal pages campaign, Personyze writes them once it has read your site and you have chosen the parts in What changes. This page covers the Versions step, where you approve them and choose how they compete; publishing; the link for each segment on the QA step; and By segment, where each version is measured against the original — your page as it is. Versions is the campaign’s third step, QA the fourth and By segment the last.
How versions are written
For every part with words — switched on or not — Personyze writes each segment its version from what your site already says: its facts, its offers, its words. A version that adds a number, a price, a plan name, a customer’s name, a deadline or any claim your page does not make is dropped. A hero’s picture is never written: it is one you give it.
A hero and a pricing table get two versions per segment, each around its own idea, named under it. A message bar, a list’s order, your form, a meeting booking and your header’s button get one per segment. All of them arrive as Waiting for you.
Approve, edit, write again or reject
The list groups the versions Per segment or Per change; each group opens into its versions. Segment, Change and Show (Waiting for you, Approved or All) narrow the list. To approve:
- Approve on a version’s line, or tick several — or Select all shown — and click Approve selected.
- Approve all waiting (n): every waiting version the Segment and Change filters hold, after one confirmation. Versions written since your click, and any that say a word you ruled out, that you took back or whose segment was removed, keep waiting; a line under the band says how many.
Show it opens a drawing of a version and its buttons: Edit its words, then Save (a list’s order has no Edit); Write it again for new words around the same idea, read from the page as it is today, which wait for you; Reject, and it is never shown.
A live version written again stays on your site. Its new words wait beside it as New words to replace the live version, and replace it once you approve them and publish.
How the versions compete
The box at the top of Versions, How the versions compete, shares each segment’s sessions between your page as it is and the versions you approved:
| Card | What it does |
|---|---|
| Auto-optimize (Recommended, the default) | Sessions shift to the version that converts best. Once a day it also retires losers, writes replacements and pauses a part the original wins. |
| A/B test | Every version gets the same share. You read By segment and pick the winner: nothing is retired, written or paused for you. |
The original’s share — 5%, 10% (the default), 20%, 30% or 50% — is the share of each segment’s sessions that keep seeing your page as it is: the group every version is measured against, whichever card you choose (see A/B testing).
Auto-optimize works from each part’s last 14 days in each segment. It:
- shares each hour’s sessions by every version’s chance of being the best — evenly until they have 300 sessions between them, and always a little to each. A session keeps its version for the whole visit;
- retires a version with 1,000 sessions or more and under a 5% chance of being the best, never the last one;
- writes a hero or a pricing table a new version when there is room, around an idea not tried yet. It waits for you unless publishing by itself is on;
- pauses a part for a segment when the original has a 95% chance or more of beating every version over 2,000 sessions or more: that segment sees the original there.
Publishing by itself
Publish new versions by themselves is off unless you switch it on. On, choose Up to n a day — 5, 10, 20 (the default), 50 or 100 — and each day the oldest waiting versions are approved for you: never in a part your original wins, never one you took back or one that says a word you ruled out. On a campaign already published they reach your site with no Publish, and the bell says how many. Each is marked Published by itself for 14 days, with Undo: it goes back to waiting, is never published by itself again, and leaves your site with the next publish.
Words never to use
Type them under Words never to use, separated by commas, and click its own Save. A word that starts with one you list counts too. A version that says one is never written, approved or published by itself; a live one that says one goes back to waiting and leaves your site when you publish the campaign. Your own edits are not checked as you save them, but a waiting version with a listed word cannot be approved.
When your site changes
Personyze checks each hero again on its pages, once a day. When they changed and the hero is no longer where it was read, the hero stops by itself — visitors see the original there — and its card in What changes asks you to point at it again. It comes back once you do, or by itself once a later check finds it where it was. After a redesign, read your site again with Read it again on the Segments step.
What reaches visitors, and when
A change made by hand stays the campaign’s draft until you publish the campaign from the editor’s header. Publish to staging shows it only to browsers switched to staging — yours and your colleagues’, through the QA links — and Publish to live to your visitors. The settings with no Save of their own say Not saved yet – kept when you save the campaign. On a live campaign, save them with Publish to live: Save as draft takes a campaign off your site, as for every campaign.
| You change | It reaches visitors |
|---|---|
| A version approved, edited, written again or rejected; how the versions compete; the original’s share | When you publish the campaign. |
| Serve the versions again | On a live campaign, when you publish it live; otherwise within hours. |
| A version published by itself; Auto-optimize’s own work; a hero stopped because its page changed | On its own. |
QA: a link for each segment
The QA step starts with A QA link for each segment. Pick a segment under See your site as — or Everyone else, a visitor no segment fits — and its row says what changes for it: Changes for them: …, Nothing to see yet – its words wait for you in Versions. or Nothing changes for them yet.
- Open opens your site in a new tab as that segment sees it. The whole visit in that tab is seen as that segment.
- Check runs the campaign for real as that segment, and the QA bar says what it did and why.
- Copy link copies the Open link, for a colleague or a client.
A link starts on a page where that segment has approved words; Start on picks another, and the row then says what changes there. Open and Copy link give the clean page, as a visitor sees it, unless you tick Show the QA bar on the page.
The links show the published campaign, never the draft: until it is published the step says Publish it to staging first, and a version approved since the last publish shows after the next one. On staging, the links open your site on staging — you see the changes, your visitors do not — and your browser stays on staging for that site until you open a live link or click Back to live. The rest of the step is every campaign’s QA: see Testing & QA.
By segment: each version against the original
At the top, one line sums up how the versions compete, with Change in Versions. Then a row per segment, with its counts and one plain sentence — which version converts better than your page and by how much (confident from a 95% chance of being the best, likely from 80%), that your page still converts best, or that it is too early to tell. Open a segment for a table per part:
| Column | What it shows |
|---|---|
| (first) | The original, then each version by its number and idea; With it for customer logos or reviews. |
| State | Live: shown to this segment. Challenger: a new idea waiting for your approval. Retired: it lost. Paused: the original won here. Shown: logos or reviews, against the page without them. |
| Sessions | Sessions of this segment that reached a page with this part, last 30 days. |
| Conversions, Rate | How many of them converted, and conversions per session. |
| Lift | How much higher — or lower — the rate is than the original’s. |
| Chance of being best | The chance, from the counts so far, that it converts best of the original and the live versions. |
A paused part says Paused: the original converts better than every version here, so this segment sees the original. Serve the versions again puts its versions back; with Auto-optimize, the daily check may pause it again while the original still wins.
Results are counted once a day over the last 30 days, and start the day after the campaign goes live — until then the step says No results yet. A session counts once, in its segment; a visit no segment fits is not counted here.
Related
- Personal Pages — the overview
- Personal Pages: Segments — who sees which version
- Personal Pages: What Changes — the parts that get versions
- Testing & QA — every way to check a campaign
- A/B Testing
- Performance Metrics