Source: https://www.revvly.ai/docs/concepts/meter

Catalog

# Meter

The definition of something you meter — seats, GB, API calls, GMV.

## Overview

A Meter is the unit you measure — 'seat', 'gb', 'api-call', 'gmv'. It carries no money on its own. To bill on a Meter you attach a Variable Component, which adds a pricing model on top. One Meter can power many components (a 'seats' meter might back a flat-rate seat charge in one bundle and a tiered seat charge in another). You no longer need to create a Meter before creating a component — leave it unset and Revvly provisions one automatically from the component's name; binding to an existing Meter is available as an advanced option when you deliberately want to share usage-tracking identity across components. Meters live in Settings → Meters; the internal field and API parameter names (variableType, variableSlug, variableId) predate the rename and are kept for backward compatibility.

## How it connects

This concept highlighted in context. Click a peer to navigate.

Related

Bundle

Variable Component

Meter

Related

Subscription

Subscription Variable Usage

- Attached to by Variable Components
- Counted via Subscription Variable Usage

## Key fields

What you’ll see when creating or editing a Meter.

- **Meter type**: Stable key (e.g. "seat", "gb") — internal field name variableType

- **Display name**: How it appears in the UI and invoices

- **Unit label / plural**: For invoice line items

- **Reset behaviour**: Carries forward (default) / Resets each period

- **Billed value**: Highest observed (default) / Total over the period / Value at period end

- **Slug**: URL-safe key the usage API matches on — derived from the meter type if you do not set one

- **Status**: Active / Deprecated

## Example

User seats

Type

seat

Unit

1 seat / 5 seats

Measures

Carries forward, billed on the highest observed