
- Visibility to customer’s current usage
- Access enforcement according to the defining pricing model
- Billing according to reported usage
- Customer notifications about changes to their usage, for example: limit is about to be exceeded
- Notifications to internal stakeholders (i.e. sales and CS reps) about changes to customer usage
- Triggering of additional actions in applications that are integrated with Stigg
Supported usage sources
Stigg supports metering of usage from the following data sources:- Calculated usage - usage that has been aggregated and calculated by your application. This type is useful for features, such as: seats.
- Raw events - raw events from your application, which Stigg filters and aggregates aggregate to calculate customer usage. This type is useful for features, such as: monthly active users (MAUs).
Calculated usage | Raw events | |
---|---|---|
Supports custom dimensions | ✅ | ✅ |
Aggregated by | Your application | Stigg |
Supported aggregation methods | Custom | Count; Count unique; Sum; Max; Min; Average |
Limit enforcement | Immediate | Near real-time (up to 10 seconds) |
Ability to bill according to reported usage | ✅ | ✅ |
Use when | Usage calculation is simple; Low throughput of usage changes; Limit enforcement must be immediate | Calculation is complex and/or distributed; High throughput of usage changes; Limit enforcement is not required or can be near real-time |
Example use-cases | Seats | Monthly active users (MAU), bandwidth, used storage |