Skip to content
Platform · Metrics

Metrics that match your stack.

Three types, primary plus additional, revenue tracked natively. Metrics live at the org or project level and attach per-experiment.

01 — Types

Three primitives. That’s it.

CLICK

Click

Listen on any selector. Fire when a user clicks the button, link, card, or custom component. Per-click revenue optional.

.checkout-cta
PAGEVIEW

Pageview

Match the URL with SIMPLE / EXACT / SUBSTRING / REGEX rules. Perfect for funnel steps and content-gated goals.

/thank-you
CUSTOM

Custom

Fire whatever your app already fires — call window.avsb.track.event() with a string event key and an optional payload of revenue or value.

window.avsb.track.event('add_to_cart')
02 — Primary vs additional

One primary. Many supporting.

Every experiment designates one primary metric. That’s the metric the stats engine reads when it calls the winner. No ambiguity, no cherry picking, no post-hoc “we were optimizing for this the whole time.”

Additional metrics come along for the ride — conversion funnels, guardrail metrics, secondary revenue lines. They appear in the results view without affecting the verdict.

PRIMARY
checkout-completed
calls the winner
ADDITIONAL
add-to-cart
ADDITIONAL
signup-completed
ADDITIONAL
revenue-per-visitor
03 — Revenue

Revenue, first-class.

Attach revenue to any event. The platform aggregates it into average revenue per visitor, total revenue lift, and revenue-weighted confidence intervals — so a 2% conversion lift that double the basket still wins the experiment.

  • Per-event revenue via { revenue: 49 }.
  • Continuous values too — pass { value: n } for quantile metrics.
  • Exports to your warehouse via integrations + webhooks.
javascript
1// After a successful checkout
2window.avsb.track.event('purchase', {
3  revenue: 49,
4});
5

6// That event feeds ARPV, revenue lift, and
7// revenue-weighted stats automatically.
04 — Attachment

Define once. Attach anywhere.

Metrics live at org or project scope. Define a metric like checkout-completed once, then attach it to any experiment in the project. No copy-paste, no drift.

Change a metric definition? Every experiment using it updates automatically. Change the primary for one experiment? Other experiments keep theirs.

Project scope
checkout-completedadd-to-cartsignup-completedbounce
exp · hero-copy
exp · checkout-cta
exp · pricing-layout

Measure what actually moves the business.

Revenue, clicks, pageviews, custom events — pick the ones that matter.

Start free — no cardBook a demo