Trust and control
One script, and a very short list of what it does
A/Bee is split testing that rewrites copy on your pages and measures what works. Putting someone else's code on your site is a real decision, so here is exactly what changes, exactly what gets recorded, and the three controls that keep it inside your rules.
What it can change
A hypothesis, not a word swap. Each variation argues a different reason someone should act, and it lands as copy in whichever element the experiment targets, whether you picked that element or autopilot did.
- Headline and subHomepage heroes, landing copy, the first thing anyone reads.
- The call to actionIts wording, which is the part that moves.
- The whole pathA promise that wins the click has to survive the next page, so a variant can span every page it touches and still be measured on the goal at the end.
- Programmatic setsOne experiment across thousands of near-identical pages.
What it leaves alone
- Your layout and page design. Nothing moves and nothing gets reordered.
- Your styling. The engine writes copy, not CSS.
- Everything else on the page. Only the elements a running experiment targets ever change.
- Images and media, unless you put them in a variation yourself.
- Your visitors' data. Two things get recorded: which variation someone saw, and whether a goal fired. No form contents, no field values, no keystrokes, nothing typed into a checkout.
- Behaviour tracking of any kind. No heatmaps, no session recordings, no scroll or mouse tracking, no visitor profiles, and nobody followed from one site to another. This is not an analytics suite and does not try to be one.
- Your URLs. The page path is recorded, never the query string, so nothing carried in a link can leak through it.
A visitor is assigned once and stays on that variation, so your copy never changes under someone between one page and the next. That is held by a random first-party id which means nothing outside your own site.
Fully manual mode is the exception. You write the variation yourself, so you decide exactly what goes in it.
Compliance and control
If there are things your business is not allowed to say, the engine has to know them before it writes, not after. Three controls, and all three stick.
- Approval mode
- The hard stop. Nothing reaches a visitor until you have read it and said yes. The engine still drafts, plans and queues; it just cannot publish. Leave it on for as long as you like, on a per-experiment basis.
- The brief
- Standing rules every hypothesis is written against, alongside a profile of the business: what you sell, who buys it, and what makes you different. This is where lines like “we are not FCRA accredited” or “never promise a guaranteed outcome” live. A/Bee drafts one from the scan and you can rewrite it. One for the site, and one per experiment when a single test needs its own rules.
- Rejections, with a reason
- Turn down a hypothesis or a variation and say why. The reason is kept and every later draft is written against it, so an off-brand idea does not come back a month later in different words.
Try it on your own site
Paste a URL and A/Bee hands back its first hypotheses for that page. Free, and no signup.
Tear it down