AI Personalization — Your Own Pages, Speaking to Each Visitor’s Segment

AI Personalization (called Personal pages before) makes your own pages speak to each visitor’s segment: your hero, a message bar, your header’s button, a menu item, your pricing table, your form and more, each in words written for that segment. Personyze reads your site, proposes the segments and writes each part’s version for each segment from what your site already says. Nothing changes on your site until you approve it and publish the campaign. Start one in New campaign: the AI Personalization card on Campaign types, also under Toolkits → Personalize your pages. An account has one: once yours exists, the card says You have one – opens its name, and Start opens it.

Watch the 2:00 walkthrough: the settings before it reads, Read my site, the segments it proposes and how a visitor gets one, turning the hero on, Review all with Show it and Approve, then Publish to staging.

How it works

1. You set it up on Your site: the site Personyze reads and, if you want, the settings it writes with.
2. Personyze reads your site (Read my site): what each kind of page shares — the hero, a pricing table, an FAQ, your header’s button — and the audiences your pages speak to.
3. You check the segments: rename, remove or add your own, say what puts a visitor in each, and which wins when two fit.
4. You choose what changes: switch on the parts it found, and add the ones you want.
5. Personyze writes the versions, one per segment for every part with words.
6. You approve them, in Review all.
7. You publish: Publish to staging, see each segment’s view on QA, then Publish to live.
8. Each visitor gets their segment’s version, measured against the original.

The steps

There is no Target, Content or Versions step: Which visits it runs on limits the whole campaign, the campaign makes its own actions, and the versions open in Review all. Each step’s Guide explains it in the panel.

Beside every step but QA, a box sums the campaign up: where it stands (Live since … · version 12), the line that reads your site (Read my site, later Read it again), what is About to go live, and what Needs you — a part not found, versions waiting, a segment nothing puts a visitor in — each a link to where it is fixed.

What can change

A part the reading found changes only once switched on, on its row or in its drawer; a part you add is on at once. Each row of Parts on your pages has Content (its versions) and Look (its drawer). Nothing else on the page changes — see AI Personalization: What Changes.

How a visitor gets a segment

As a visit starts, Personyze checks, in the order you set under How a visitor gets their segment: The page they landed on, The words of the ad they came from, The site that sent them and Targeting rules (a CRM field or a discovered audience among them). Then their answer to your question, and last Their company, through a segment’s company rule. Nothing fits: your pages as they are. More in AI Personalization: Segments.

With no priority set, the first that recognizes them wins, and a visit keeps its segment. Segment priority, highest first — Personyze proposes one when it makes the segments, and you can reorder it — decides when two segments fit one visitor: the higher one wins, and a company or an answer found during the visit that ranks higher takes over from the next page.

Remember a visitor’s segment (off to start; 30 days, or the days you set) starts a returning visitor in their last visit’s segment, and If a later visit points to another segment: chooses what happens then — move them only to a higher-priority segment (the default), keep them, or move them. Their company never moves a remembered visitor.

Their own pick has two switches, both off to start: Let every visitor switch their view puts “Viewing as:” in your site’s header — what they pick there comes before everything else, and they can change it on any page — and Ask the visitors nothing recognized asks once, as a pop-up, a side tab, a bottom bar or a corner button. See their own pick.

Versions and publishing

A fact your site does not say is never written. On Your site, How the versions are written sets the writer — Standard, Better or Best — and Keep each version close to the original’s length; a version that says one of your Words never to use is never approved, and adding a word writes again the versions that say it. Review all opens every version, to Approve, Edit, Write again or Reject each, or Approve all waiting; Rewrite all writes the versions shown again.

How they compete, a card on Your site and a line on What changes:

• Auto-optimize (recommended): sessions shift to the version that converts best; a clear loser is retired, and another written in its place for your approval.
• A/B test: every version gets the same share; you pick the winner.

The original’s share of sessions — up to 50%, 10% to start — sees your page as it is, and every version is measured against it; at 0% – no comparison, nothing is. With Auto-optimize, where the original beats every version of a part for a segment, that part is paused there — the original shows — until you Serve the versions again. An A/B test pauses nothing, nor does 0%. Auto-optimize never approves a version.

Only Publish new versions by themselves does: on, up to the number a day you choose publish without you, each marked Published by itself with Undo (it leaves your site at your next publish).

Changed your mind before publishing? In the count beside Save, Discard unsaved changes drops what is not saved, and Put back what is live (or Put back what is on staging) sets the draft back to what your site shows. More in AI Personalization: Versions and Results.

What you see, and what visitors see

• You, first. After Publish to staging, the QA step has a row for each segment and Everyone else (no segment): Preview opens your site as that segment sees it, and its link can go to a colleague. Visitors see none of it until you publish live.
• Your visitors, once live. Each sees their segment’s approved versions of the parts that are on; the original’s share, and visitors with no segment, see your page as it is. A session keeps its version. With Anti-flicker on (Site profile → Page loading), nobody sees a hero’s own words swap to their segment’s; after a part goes live, copy the tracking code again (Tracking Code) so it is held from the first moment too.
• Your numbers. Leads, bookings and orders are counted where they always are. Performance sets each version’s conversions against your page’s, from the day after the campaign goes live.

Limits

• No segment: the original page. A segment nothing puts a visitor in is never shown.
• One segment per visit, unless the visitor picks another in the switch, or a segment higher in your priority is found during the visit.
• Every hero is checked once a day. One no longer where Personyze found it stops, and its pages show the original, until a later check finds it again or you point at it again in its drawer in What changes; a hero found on only a few pages stops only after a second missed check. A part on but not found changes nothing until it is found.
• One AI Personalization campaign per account: its segments and pages are the account’s. A second one’s Read my site is refused, with a button to open the first.
• Nothing changed by hand reaches visitors before you publish. Publishing by itself goes out on its own, and so does Auto-optimize’s work — shifting sessions, retiring a loser, pausing a part — and a way in Personyze adds to a segment from your visits, which the segment marks as on your site.
• The switch needs a main button in your site’s header, such as “Book a demo”.
• It needs the Personyze tracking code; a goal is recommended.

Related

• AI Personalization: Segments — who sees which version
• AI Personalization: What Changes — the parts of your pages
• AI Personalization: Versions and Results — approve, compete, measure
• New campaign
• Testing & QA — staging and live
• Conversion tracking — the goals versions are measured by
• Audience Discovery
• Customer Logos
• Show Reviews
• Book a Meeting