THE PRODUCT

Every visitor gets the page they came for.

Here is what AXO does, in order: from the first fifteen minutes on your site to the result landing in your CRM.

Start free trial →See pricing
AXO · Dashboard
The AXO dashboard: visitors, groups and results for one site
01 · SET UP

Live on your site in about fifteen minutes.

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.

THE CLOCK IS COMPRESSED. THE FIFTEEN MINUTES IS NOT.

Through your tag manager

One script, added the way you add any other. No developer project, no redesign, no new pages.

It reads your site first

AXO works through your own sitemap, page by page, and learns what each page is for.

Nothing changes yet

Visitors see the site exactly as it was until someone on your team approves a change.

02 · READ

It reads what each visitor does, while they are still there.

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.

AXO · Live
AXO live feed of visitors on the site right now
IN THE PRODUCTThe live view: who is on the site right now and what each of them is doing.
AXO · Visitor
AXO profile for a single visitor showing their visits and what they looked at
IN THE PRODUCTOne visitor: their visits, what they looked at, and what your CRM already knew.
03 · GROUP

Nobody builds the list. Visitors sort themselves.

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.

NO RULE TO WRITE, NO LIST TO REFRESH. A VISITOR IS SORTED WHILE THEY ARE STILL ON THE PAGE.

No rule to write

The comparer, the form staller and the returning customer show up as groups because they act like groups, not because someone described them first.

Sorted while they are there

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.

Your own groups still count

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.

AXO · Groups
AXO groups screen showing the groups visitors fall into
IN THE PRODUCTThe groups AXO found on one site, with how many visitors are in each and how each one converts. You can add your own rules alongside them.
04 · CHANGE THE PAGE

Same page. A different version for each group.

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.

Headline and copy

The words that meet them, matched to what they are trying to do.

Proof

Reviews for the careful reader, a comparison for the comparer, a price for the bargain hunter.

Button, form and offer

A shorter form for people who stall. The next step that fits where they are.

Product picks and pop-ups

Recommendations learned from your own catalog, and messages timed to what they just did.

05 · APPROVE

AI drafts. A person on your team approves.

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.

AXO · Editor
AXO editor with a drafted version of a headline waiting for approval
IN THE PRODUCTThe editor: point at the part of the page, review the draft, approve it. Every change and every approval is logged.
06 · PROVE

Measured at the conversion, not the impression.

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.

One in ten sees the original

That is the default. You can change the share. If you switch it off, the report says "no control group" instead of claiming lift.

Per page, per version

You see which change helped which group, at the form or the order.

Traffic follows what works

As results come in, more visitors see the versions that are working and fewer see the ones that are not.

AXO · Results
AXO results screen comparing personalized visitors with the control group
IN THE PRODUCTThe results screen. Your numbers, your control group.
07 · SEND IT BACK

What it learns goes back to the systems you already own.

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.

Your CRM

Salesforce sync in both directions, plus a built-in lightweight CRM if you do not have one.

Email and ads

Groups go to your email platform. Conversions are reported back to Meta and Google from the server.

Everything else

Scheduled exports to your warehouse, and notifications to any other system when a profile changes.

08 · RUN IT

Your team runs it. Or your AI assistant does.

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.

AXO · Toolkit
AXO toolkit screen listing what a team or an AI assistant can do
IN THE PRODUCTThe same jobs, whether a person clicks or an assistant asks.
The technical detail, for whoever sets it up →
09 · COST

Four tools, four contracts, four set-ups. Or one script.

Testing, personalization, customer data and forms usually arrive as separate products, each with its own contract and its own numbers. AXO is one.

See the whole price list →Compare AXO to the tools it replaces →
10 · PRIVACY AND CONTROL

Built on your own data. Under your own rules.

No third-party cookies

AXO works from what happens on your own site.

No personal data required

It can personalize on behavior alone – nothing that names a person.

An anonymous mode

For sites and pages where nothing identifying should be collected at all.

Route, do not rewrite

For pages that must not change, AXO can send visitors to a different approved page instead.

THIS PAGE IS DOING IT RIGHT NOW

Everything above is a claim. This part is the product.

LIVE ON THIS PAGE

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.

READING
Asking the tag what it decided for you.

The tag loads deferred, after your analytics, so this takes a moment.

AXO holds back 10% of visitors on every site it runs, this one included.
Whichever side of that you are on was decided before this section rendered.
WHAT THE TAG SAYSwindow.axo
VISITOR ID
–
SESSION ID
–
SEGMENT
–
HOLDOUT BUCKETED ON
–
Read from your browser. This panel sends nothing – the tag had already made these decisions before you scrolled here.
WHAT YOU ARE ACTUALLY WORRIED ABOUT

The awkward questions, answered first.

NOT ENOUGH TRAFFIC

What if we do not have enough traffic to prove anything?

Then AXO tells you that instead of showing you a lift number. The report says there is not enough evidence yet, and keeps saying so until the personalized group and the control group really separate. Smaller sites still get the reading of who is visiting and where they stall.

PAGE SPEED

What does the script do to page speed?

It is one script, loaded so that it never blocks the page from drawing. Changes are applied to the specific parts of the page that are set up to change, not by redrawing the page.

YOUR DATA

What data leaves our site?

What visitors do during the visit – pages, scrolling, time spent, where they came from – plus anything you choose to connect, such as your CRM. No personal data is required: AXO runs anonymously by default and you add identity later, on purpose, if it pays off.

IF IT DOES NOT WORK

What happens if the control group says it did not work?

You get told. The report can show a negative result or not enough evidence. The control group is one visitor in ten by default; you can change the share or turn it off, and if you turn it off the report says there is no control group rather than claiming lift.

ENGINEERING

How much engineering time does this take?

One script to install, and about fifteen minutes from the script being live to the first page that is ready to personalize. After that the work sits with whoever owns the copy. You point at the part of the page you want to change; nobody edits templates.

REPLACING TOOLS

Do we have to rip out our current tools first?

No. AXO reads behavior itself, so it does not need your warehouse or another tool to start. Teams usually run it alongside what they have and let the control-group results decide what stays.

See it on your own site. About fifteen minutes.

Add one script, watch who is really visiting, then turn on a few changes and read the lift against your own control group.

Start free trial →Talk to us