> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.solvimon.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.solvimon.com/_mcp/server.

# Details: UsageMeters

The **UsageMeters** tab under **Insights → Details** shows the usage events your platform sends to Solvimon: how many arrive, on which meters and from which customers. Use it to check that usage is flowing in as expected before it ends up on invoices.

---

## Filters

| Filter         | What it does                                                                                                                                                        |
| :------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Date range** | Limits the two charts to events whose event timestamp falls in the range. The event timestamp is the time you send on the event, not the time Solvimon received it. |

The three key figures ignore the Date range and always cover all events.

## Key figures

| Tile                 | Formula                                                   | Use it for                                                                 |
| :------------------- | :-------------------------------------------------------- | :------------------------------------------------------------------------- |
| **Unique meters**    | Count of distinct meters that received at least one event | Checking that every meter you set up actually receives data                |
| **Unique customers** | Count of distinct customers that sent at least one event  | Checking that every customer you expect to bill on usage is sending events |
| **Total events**     | Count of distinct events                                  | The overall volume of usage data                                           |

An event that carries several meter values counts once.

## Charts

### Count by meter

The number of events per meter in the selected range, for the 15 meters with the most events.

**`Formula`**

```text Formula
Count by meter = count of distinct events per meter, event timestamp in the range
```

Use it to spot a meter that suddenly drops to zero or spikes. A drop usually means an integration stopped sending; a spike can mean duplicates or a change in how events are sent.

### Count by customer

The number of events per customer in the selected range, for the 15 customers with the most events.

**`Formula`**

```text Formula
Count by customer = count of distinct events per customer, event timestamp in the range
```

Use it to see which customers drive usage, and to check a single customer's volume before their invoice is finalised.

## Things to know

* **Events, not amounts.** The tab counts events. What an event is worth depends on the meter values it carries and on the customer's pricing; see the [invoice usage report](/platform-guides/analytics-reporting/report-downloads/matched-events) for the events billed on one invoice, with their price.
* **Unbilled usage.** Events that couldn't be matched to a subscription aren't billed. See [Unbilled usage](/platform-guides/meter-and-event-design/unmatched-events) to find and fix them.
* **Empty tab.** The tab reads Solvimon's current event pipeline. If it stays empty while you're sending events, contact support to have it enabled for your platform.

---