Surface 01 · CampaignsReplaces the job of: Webflow · Shopify · VWO · Statsig · MutinyLive in all deployments

Ten tests. Ten channels. Ten personas. Running before standup.

Brief the move once. Lyberty helps build and launch the page, email, ad, offer, automation, or test across the channels involved. The result comes back with revenue, spend, evidence, and a next action.

Read the docs
What this view gives you

Any touchpoint, any channel

Landing pages, emails, ads, push, popups, and on-site flows can be planned and shipped from the same brief.

Parallel funnel coverage

Top-of-funnel, checkout, post-purchase, and lifecycle tests can run at the same time without losing which result belongs to which move.

Audience variants without re-keying

Use the same audience definition for the page, email, ad, and report instead of rebuilding it in each tool.

Winner, loser, or keep running

Each result gets a clear decision and a next action, not a Slack thread that disappears.

Tied to revenue, not CTR

Each launch reports orders, revenue, spend, and margin where the data is available, not just click-through.

Work this can reduce
TaskSimilar toolsLyberty
Build a pageWebflow ($300+/mo)included
Run an A/B testVWO + Statsig ($1k+/mo)included
Email/SMS testKlaviyo Tests + Litmusincluded
PersonalizationMutiny / Dynamic Yield ($3-15k/mo)included
Revenue readoutmanual or Northbeamincluded
01 · Tests tied to revenue

Every test should end with a trusted readout and a next move.

Brief · launch · measure · decide

market.funnel · last 30d · vs. prior 30d
visit
248,204+3.2%
sign_up_start
58,412+1.1%
sign_up_complete
42,108+4.8%
activated
24,884+11.2%
first_commit
14,218+9.4%
experiment · #44
Homepage hero v4.2
● 96% confidentship recommended
Control (A)
4.1%
n = 12,108
Variant (B)
4.4%
n = 12,010
Suggested next action:
▸ ship variant B -> update landing page -> record reason -> assign follow-up
02 · The difference

Segment · Amplitude · Statsig · VWO gives you the tool. Lyberty ties it to the rest of the business.

Under the hood

Segment · Amplitude · Statsig · VWO
A testing tool, a winner in Slack, and a document nobody opens again.
TrackingEvents in a product-analytics silo
ExperimentsA test runs · a report appears
WinnersShipped · then quietly forgotten
AttributionReconcile later against billing
HistoryWho remembers last year's tests?
Lyberty
Every test ends with revenue, evidence, a decision, and a next action.
TrackingEvents tied to orders, customers, and revenue
ExperimentsA test runs · the winner becomes a decision
WinnersPromoted with a reason and follow-up
AttributionCustomer, order, and revenue stay connected
HistoryPrior tests and decisions are searchable

The surface is just the view.

All six surfaces share the same record. Adopt one, and the others are already reading from what you wrote — no sync, no export, no reconcile.

See every surface