Metrics and guardrails One definition, used everywhere.
Conversion means one thing in Plinth. Define each metric once, from your events or your monitoring tool, and every experiment, rollout and chart uses the same definition.
How it works
-
Define the metric
Build it from events, such as failed checkouts per checkout started, or import it from Datadog.
-
Mark guardrails
Give the metrics that must never get worse a limit.
-
Reuse it
Pick it as a goal in an experiment or a guardrail on a rollout.
The details
- A shared catalog
- Product, data and engineering read from the same list of metrics.
- Ratios and sums
- Rates, averages, totals and percentiles, from any event property.
- Version history
- See who changed a definition and which results it affected.
export const checkoutErrors = defineMetric({
event: 'checkout_failed',
per: 'checkout_started',
guardrail: { max: '1%' },
});More of the platform
-
Feature flags
Put every change behind a flag and decide who sees it, without a deploy.
Learn more: Feature flags -
Scheduled rollouts
Go from 1% to everyone over days, with automatic pauses when errors rise.
Learn more: Scheduled rollouts -
Experiments
Split traffic between variants and get a clear result, with the statistics done for you.
Learn more: Experiments
Try Metrics and guardrails today
Free for small teams. Set up in minutes.