AI Personalization: Versions and Results — Approve, Compete, Measure

A version is what one part of your pages says to one segment — for example, the hero’s headline for retailers. In an AI Personalization campaign, Personyze writes them once it has read your site and you have chosen the parts in What changes. They have no step of their own: you set how they are written and how they compete on Your site, approve them in Review all, see them on the QA step and measure them on Performance, against the original — your page as it is.

Watch the 1:13 walkthrough of a campaign with a month of results: the segments and what each colour means, Needs you, Performance and lift against your page, Share now and Auto-optimize, and asking the AI assistant how it is doing.

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. The writer is told your words never to use, and a version that adds a number, a price, a name, a deadline or any claim your page does not make is dropped. A hero’s picture is never made up: it is one of the segment’s pictures, yours or found on your own pages.

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, your header’s button and a menu item get one per segment. All of them arrive as Waiting for you.

On Your site, How the versions are written holds two settings; set before Read my site, the first versions are written with them.

• The writer: Standard (where every campaign starts), Better or Best. A stronger writer writes longer text better and uses more of your AI allowance. It is saved at once, for new versions; Rewrite them writes the ones you have again.
• Keep each version close to the original’s length — on to start, within ±20% (10 to 50). Each headline, line and button is asked to stay that close to your page’s own words’ length; what still comes back longer is fitted to the original’s place. It waits for the campaign’s Save.

Review all: approve, edit, write again or reject

On What changes, Review all › heads the list of parts, and the step’s line counts the versions waiting for you; a part’s drawer lists its own under Waiting for you (Approve, Edit, Write again, Reject, or Approve all n); a segment’s card on Segments has n wait for you › and n approved ›. Review all versions opens as a page over the editor, grouped by segment. Segment, Part and Show (Waiting, Approved, All or Rejected) narrow it, and Show all opens every group. Then:

• Approve on a version’s line; or tick several — or Select all — and use the bar that appears: Approve selected, Write again selected, Reject selected (it asks first), or Bring back selected for rejected ones.
• Approve all waiting (n): every waiting version the Segment and Part filters hold, once you confirm with Approve all. Any left waiting are counted, with why.

Show it opens a drawing of a version, with Edit (then Save), Write again — new words around the same idea, which wait for you — and Reject. A rejected version has Bring back or Write again. 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.

Each Write again writes at your campaign’s writer; its arrow (How it is written) picks another, with what each costs. Rewrite all, from its arrow, writes every version the filters hold again, up to 1,000 a day, keeping the words before for Compare before and after ›; versions you edited by hand are left as they are. While it works, its place shows how far it is, with Stop.

How the versions compete

One setting, shown in three places: a card on Your site; the line How they compete on What changes, whose Change opens it in place; and the same line at the top of Performance, whose Change takes you there. The line names the way and your page keeps n% or no comparison.

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, which every version is measured against (see A/B testing). 0% – no comparison: every visitor sees their segment’s version, nothing measures the lift, and no part is paused for the original — choosing it serves again every part that was paused. These choices wait for the campaign’s Save (Not saved yet – kept when you save the campaign.) and reach your site when you publish it; a session keeps the version it started with.

Auto-optimize, from each part’s last 14 days in each segment:

• shares each hour’s sessions by each version’s chance of being the best — evenly until 300 sessions, always a little to each;
• retires a version with 1,000 sessions or more and under a 5% chance of being the best — never the last one, nor one you switched off;
• writes a hero or a pricing table a new version when there is room, around an untried idea — waiting for you unless publishing by itself is on;
• pauses a part for a segment when your page, shown 200 times or more, has a 95% chance of beating every version over 2,000 sessions: that segment sees the original there.

Publishing by itself

Publish new versions by themselves, under How the versions compete, 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 paused part, never one you took back or that says a word you ruled out. On a published campaign they reach your site with no Publish; the bell says how many. Each is marked Published by itself in Review all for 14 days, with Undo: it goes back to waiting, is never published by itself again, and leaves your site with the next publish. Nothing else approves a version for you — Auto-optimize never does.

Words never to use

Words never to use is one list, shown in two places: the last card on Your site and a line on What changes, each opened with Change. Type a word or a phrase, then Enter or a comma: each is a chip, × removes it, and the list’s own Save keeps them (Not saved yet – press Save here until then) — up to 50, 40 characters each, in any case, a word that starts with one counting too.

No version that says one is written, approved or published by itself. A word you add checks your versions (Checking your versions): those that say it are written again without it, by themselves, and wait for you in Review all. A live version that says one goes back to waiting and leaves your site when you publish the campaign. In Review all, a version that still says one is marked Says “…”, with Write it again without it in place of Approve.

When your site changes

Personyze checks every hero on its pages once a day, whether it is on or off. A hero no longer where it was read stops by itself — visitors see the original there — and in What changes it says Needs you, its drawer asking you to point at it again. A hero found on only a few pages is given a second look first: missed once, it stays on your site and its drawer says so in amber, and only a second missed check, at a later daily check, stops it. Every hero’s drawer has 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 (see Segments).

What reaches visitors, and when

A change made by hand is the campaign’s draft until you publish it from the editor’s header: Publish to staging shows it only to browsers switched to staging — yours, through the QA links — and Publish to live to your visitors. On a live campaign save with Publish to live: Save as draft takes a campaign off your site.

Beside Save as draft, a count says what waits (3 changes to publish); point at it or click it for the list, in two groups: Not saved yet – lost if you leave the page — settings with no Save of their own say Not saved yet – kept when you save the campaign. — and Saved – not on your site yet (Saved – not on your staging site yet on staging). Under each group, one button, which asks first:

• Discard unsaved changes drops what is not saved yet.
• Put back what is live (or Put back what is on staging) sets the campaign’s draft back to what your site serves: its parts, versions and settings. Segments stay as they are; a part added since is switched off. Anything it could not put back is listed after.

QA: each segment’s view

The QA step opens your site as each segment sees it, with the versions you approved. Under Each segment’s view, a row per segment and one for Everyone else, a visitor no segment fits. Each row says how many of its versions are approved (n approved or None approved) and what changes for it: Changes for them: …, Nothing to see yet – its words wait for you in What changes. or Nothing changes for them yet.

• Preview opens your site in a new tab as that segment, with the QA bar at the bottom saying who you are seen as and what changed — the whole visit in that tab.
• Its arrow: Open without the bar; On a phone; and Open in the simulator, which says rule by rule why each version shows or not.
• The link icon copies a clean link, without the bar, for a colleague or a client.

A link starts where that segment has approved words; Start on picks another page. A segment opened on Segments has the same clean page as Preview as segment ↗.

The links show the published campaign, never the draft: until then the step says Publish it to staging first. On staging, your browser stays on staging for that site until you open a live link — the row’s Preview then reads Back to live. If your site renders its own pages, the step links to the API docs for each visitor’s words as data. The rest of the step is every campaign’s QA.

Performance: each version against your page

Performance is the one place for the campaign’s results. Its first tab, Segments, is the last 30 days segment by segment; the tabs after it are the campaign’s own report, as on every campaign. Guide, at the end of the tabs, explains the step.

Segments opens on the totals — Sessions, Conversions and Lift vs your page, every segment together — then the How they compete line, and how many visitors answered their own pick, where it is on. Then a row per segment, the busiest first: its name, one plain sentence, Sessions, Your page and Best version (conversion rates), Lift, and where it stands — No sessions yet, Too early – n sessions, Learning, Leading by n%, Winner · +n%, Your page leads or No comparison. The sentence says which version converts better than your page and by how much, confident or likely, or that your page still converts best, or that it is too early to tell. No version beats your page before your page was shown 200 times. Open › shows a table per part:

Switch a version off and that segment stops seeing it — its share goes to the others; with every one off, the segment sees your page. It is kept when you save the campaign and reaches your site when you publish it live.

A paused part says Paused: the original converts better than every version here, so this segment sees the original., and its segment’s row counts it (n paused). Serve the versions again puts its versions back; with Auto-optimize, the daily check may pause it again while the original still wins.

Results start the day after the campaign goes live — until then, No results yet. A session counts once, in its segment; a visit no segment fits is not counted. What counts as a conversion, at the foot, holds the campaign’s goals.

Related

• AI Personalization
• AI Personalization: Segments
• AI Personalization: What Changes
• Testing & QA
• A/B Testing
• Performance Metrics