You add one script. AXO reads your site and finds the parts of each page that can change: the headline, the proof, the button, the form.
One script, added the way you add any other. No developer project, no redesign, no new pages.
AXO works through your own sitemap, page by page, and learns what each page is for.
Visitors see the site exactly as it was until someone on your team approves a change.
Which options they compare. How long they sit on pricing. Whether they start the form and stall. That is available on every visitor from the first visit, before anyone tells you who they are.
Audience tools ask you to define the groups up front: write the rule, refresh the list, repeat. A hand-written rule catches the few visitors it describes and misses everyone else. AXO starts from the other end. It reads what each visitor does, from the first visit, and the groups form from that on their own.
The comparer, the form staller and the returning customer show up as groups because they act like groups, not because someone described them first.
AXO reads the behavior while the visitor is still on the page, so the version they get fits what they are doing now, not what a list said last night.
Add a campaign, a customer tier or a list from your CRM alongside the groups AXO finds. Each one gets its own version of the page.
The parts of the page that can change are swapped before the page paints, so they only ever see their version. No developer ticket per change.
The words that meet them, matched to what they are trying to do.
Reviews for the careful reader, a comparison for the comparer, a price for the bargain hunter.
A shorter form for people who stall. The next step that fits where they are.
Recommendations learned from your own catalog, and messages timed to what they just did.
AI writes the options ahead of time, in your brand voice. Which approved version each visitor sees is chosen by your rules and by statistics. No AI improvises in front of a visitor.
A slice of visitors never sees a change. Both groups reach the same finish line – the form, the order, the signup – and the gap between them is the lift.
That is the default. You can change the share. If you switch it off, the report says "no control group" instead of claiming lift.
You see which change helped which group, at the form or the order.
As results come in, more visitors see the versions that are working and fewer see the ones that are not.
AXO does not replace the CRM or the warehouse. It tells them what happened on the site, so the site, the email and the ad agree.
Salesforce sync in both directions, plus a built-in lightweight CRM if you do not have one.
Groups go to your email platform. Conversions are reported back to Meta and Google from the server.
Scheduled exports to your warehouse, and notifications to any other system when a profile changes.
Everything in the dashboard can also be done by the AI assistant your team already uses – Claude, ChatGPT and others – inside the permissions you give it. It can set up a page, draft the options and read the results. A person still approves what goes live.
Testing, personalization, customer data and forms usually arrive as separate products, each with its own contract and its own numbers. AXO is one.
AXO works from what happens on your own site.
It can personalize on behavior alone – nothing that names a person.
For sites and pages where nothing identifying should be collected at all.
For pages that must not change, AXO can send visitors to a different approved page instead.
This site runs AXO on itself. The panel below is not a picture: it is what AXO decided about your visit to this page, read live from the script running in your browser.
The tag loads deferred, after your analytics, so this takes a moment.