How it works
- You send usage events to Hyperline or load them through a connector.
- An aggregator turns those events into a metric.
- The aggregator’s Visibility setting controls which customers can see that metric.
- Visible metrics appear on the customer overview and in the customer Usage tab.
- Thresholds can alert your team when a customer’s value crosses a configured limit.
Custom usage tracking uses the same aggregator system as usage-based billing. If you need to create the underlying usage events first, start with Send usage data or Usage data with connectors.
Configure a customer-visible usage metric
- Go to Usage > Aggregators.
- Create a new aggregator or open an existing one.
- Configure the metric:
- Name
- Event type
- Operation: Count, Sum, or SQL formula
- Unit name
- Optional filters
- In Visibility, choose where the metric should appear:
- All customers
- Specific segments and customers
- No customers
- If the metric is visible to customers, set a default aggregation interval.
- Choose the Displayed value:
- Total: shows the total over the selected period.
- Last complete period: shows the value from the last fully completed aggregation interval.
- Add thresholds if you want to trigger alerts.
- Click Save changes.
Visibility options
When using Specific segments and customers, add one or more segment or customer conditions. The metric appears only for customers that match the configured visibility conditions.
Where usage appears
Customer-visible aggregators appear in two places:- Customer overview: top usage metric cards summarize the most relevant customer-visible metrics.
- Usage tab: the full list of visible usage cards includes charts, filters, thresholds, and event drill-downs.
Click Explore on a usage card to inspect the underlying events for that customer and metric.
Use cases
Thresholds
Thresholds let you alert on customer-level usage changes. A threshold can trigger when a value is greater than or equal to a limit, or less than or equal to a limit. Thresholds are useful for:- Usage spikes that may indicate overages
- Usage drops that may indicate churn risk
- Low adoption after onboarding
- Customers approaching contractual limits
- Customers reaching usage levels that may justify an upsell or add-on discussion
Example 💡
You track monthly active users with an aggregator visible to all customers.
You set the displayed value to Last complete period and add a threshold
for fewer than
20 active users. When a customer’s active user count drops
below that limit, your team can review the account before renewal.Example 💡
You track storage usage in GB and set a threshold at
800. When the
threshold is crossed, the customer owner can review whether the account is
ready for a higher tier or an additional storage package.
