Signals · Beta

AI powered hypothesis generation, ranked and falsifiable.

Signals reads your page and your GA4, then generates a ranked, evidence graded backlog of A/B test hypotheses. Every idea is grounded in real behavior and argued against before it reaches you.

In beta. It runs on the Anthropic commercial API and never trains on your data.
how a scan works

Three evidence streams. One ranked backlog.

Seven stages with a shape. Three evidence streams converge into one multimodal payload, then Signals generates hypotheses, argues against its own work, and ranks what survives. Tap any stage to see inside it.

Evidence in · three parallel streams Reasoning · narrowed to a ranked backlog
01 · Intake
Site & business context
URL plus contextconnect GA4sets the tier
02 · Capture
DOM, renders, funnel walks
20 plus DOM signalsdesktop and mobilethrottled view
03 · Behaviour
GA4 funnel and drop off
device CVR and channelsfunnel drop off
04 · Payload
Multimodal payload assembled
Three image blocks plus structured evidence, combined into one prompt.
3 images + textvision reconciled
05 · Generation
Grounded hypotheses
Each tied to a behavioral mechanism and a citation; thin evidence is labeled, not inflated.
23 fieldsPXL 0 to 145 CRO pillarstwo signal gate
06 · Falsification
Argued against itself
Failure mode, confounder, alternative, and the test that settles it.
adversarial second pass
07 · Output
23 field hypotheses, ranked
Ordered by PXL, each with its tier, opportunity size and a tracking spec.
PXL ranked6 confidence tiersready to build
Tap any stage to see what happens inside it
into 01 · Intake from 07 · Output
Outcomes feed back as priors for the next scan
A few minutes · end to endIt produces the backlog · it never runs your test

Read how each stage works in the docs →

why it is different

Three things a best practice checklist will not do.

Anyone can print a list of ideas. The work is deciding what is worth your traffic, and being honest about how sure it is.

Behavioral gating The two signal rule

A finding on the page is not a hypothesis until behavior agrees.

Signals needs two signals before anything reaches your backlog, a structural finding on the page and a behavioral pattern in your GA4. A small mobile CTA is not an issue until your mobile conversion rate says so too.

Adversarial falsification The second pass

Before a test slot is spent, the agent argues against itself.

A second pass names the strongest failure mode, the likeliest confounder, the alternative explanation, and the single test that would tell them apart. You get the argument against the recommendation, attached to the recommendation.

The closed loop It owns both ends

A standalone audit guesses once. Signals hears back.

Because Signals runs inside ABTestly, the audit and the test engine are one system. Once a linked experiment concludes, its outcome feeds back automatically as a prior for the next scan of that domain. The learning is in context, not model training.

the honesty floor

Test ready is earned, never assumed.

The point of Signals is telling you what it does not know. These behaviors are built in, not bolted on.

01

The qualification gate

It tells you when your traffic cannot reach significance, and refuses to fake confidence about it.

02

Six confidence tiers

Every hypothesis carries one of six tiers. The tier reflects what Signals actually got from your data, not what you hoped for.

03

It never invents a number

Thin evidence is labeled, not inflated. When a claim rests on page structure alone, Signals says so and names the cheapest action that would confirm it.

the learning loop

Every shipped test makes the next scan sharper.

Signals does not hand off a backlog and forget it. Ship a hypothesis in ABTestly, and when the experiment concludes its result returns as a prior for the next scan. Nothing to log by hand.

Scan the page Ranked backlog Ship the test in ABTestly Exact ledger verdict Outcome returns as a prior
Note

Signals runs on the Anthropic commercial API. Your data is never used to train models, so this is a data feedback loop, not model fine tuning. Signals produces the backlog and the test plan; you stay in control of what ships.

pricing

Signals is free for every paid plan, while it is in Beta.

No extra charge and nothing to switch on. If your ABTestly plan is paid, Signals runs today at no cost.

After Beta

Signals will be priced by scans per month. One scan is one full audit run. These prices are not live yet, Signals stays free until Beta ends.

Lite
$49/mo

5 scans per month.

Growth
$149/mo

25 scans per month.

Scale
$399/mo

100 scans per month.

see it on your site

See what Signals finds on your own site.

Point it at a page, connect GA4, and read the backlog it returns. Free to start, no card.