> ## Documentation Index
> Fetch the complete documentation index at: https://docs.custral.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Usage by product

> On a customer's page: how much they use each of your products.

## Overview

Usage by product goes on a **customer** record's page and lists every product in the [usage module](/bi/reporting/usage), with how much this customer used each one:

* **Last 30 days**: their uses of the product, with a bar against their most-used product.
* **Change** on the 30 days before.
* **12 weeks**: a small trend line of their weekly uses.
* **Last used**: today, yesterday, a few days ago, a date, or **Never**.
* A **Slipping** tag when their last 14 days fell 30% or more on the 14 before.

Products they don't use are listed too, marked **Not used**, so gaps are as easy to see as usage. The line under the module name sums it up, for example "Uses 4 of 7 products · 9,916 uses · ▼ 6% on the 30 days before".

Product names open their record. ⌘/Ctrl-click opens it in a new tab.

## Configuration

There is nothing to configure. The block finds the usage module whose **customer object** is the object this record belongs to. When more than one module meters that object, tabs at the top of the block switch between them.

## How the rows are ordered

| Rows                                  | Order                                                                                     |
| ------------------------------------- | ----------------------------------------------------------------------------------------- |
| Products used in the last 30 days     | Most uses first. Always listed.                                                           |
| Products not used in the last 30 days | Most recently used first, then by name. Up to 25 rows in total, then "+ N more not used". |

Uses are the sum of each event's `quantity`, and Slipping uses the same rule as the usage-dropped signal, applied to one product. See [Usage by customer](/blocks/embedded/usage/usage-by-customer#how-the-numbers-are-counted) for the full definitions.

## Troubleshooting

| Symptom                         | Likely cause                                                           | What to check                                                                                                |
| ------------------------------- | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| "Usage isn't tracked for … yet" | No usage module uses this object as its customer                       | Create a module with this object as the customer side, or add the block to the right object's page.          |
| Every product reads "Not used"  | No event names this customer                                           | Confirm your product sends `customerRecordId` for this record, or the value its identifier property matches. |
| A product is missing            | It isn't a record in the module's product object, or you can't open it | Check the product object and the record's sharing.                                                           |

## See also

* [Usage by customer](/blocks/embedded/usage/usage-by-customer): the same events, seen from a product's page.
* [Usage Event Log](/blocks/embedded/usage/usage-table): the individual events.
* [Usage tracking](/bi/reporting/usage): modules, events, and the ingest endpoint.


## Related topics

- [The Usage module object](/dev/api-reference/usage-modules.md)
- [Usage of a customer, by product](/api-reference/usage-modules/usage-of-a-customer-by-product.md)
- [Usage by customer](/blocks/embedded/usage/usage-by-customer.md)
- [Usage of a product, by customer](/api-reference/usage-modules/usage-of-a-product-by-customer.md)
- [Usage](/data/properties/complex/usage.md)