Skip to main content
The Stigg platform offers native high throughput usage metering and aggregation capabilities that can be used as the source of truth for measuring customer usage. Measuring customer usage accurately is critical when implementing usage-based and hybrid pricing models. Stigg processes changes to customer usage in real-time and allows the following:
  1. Visibility to customer’s current usage
  2. Access enforcement according to the defining pricing model
  3. Billing according to reported usage
  4. Customer notifications about changes to their usage, for example: limit is about to be exceeded
  5. Notifications to internal stakeholders (i.e. sales and CS reps) about changes to customer usage
  6. Triggering of additional actions in applications that are integrated with Stigg

​
Supported usage sources

Stigg supports metering of usage from the following data sources:
  1. Calculated usage - usage that has been aggregated and calculated by your application. This type is useful for features, such as: seats.
  2. 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).
The following table summarizes the differences between the two data source types:

​
Idempotency

Both raw events and calculated usage support idempotent reporting: you provide an idempotencyKey with each report, and Stigg deduplicates any retries so usage isn’t double-counted. This makes it safe to retry a request after a timeout, a dropped connection, or any other ambiguous failure, without risking inflated usage or incorrect billing. The exact behavior differs slightly by data source:
  • Raw events - idempotencyKey is required on every event.
  • Calculated usage - idempotencyKey is optional, and duplicates are deduplicated for 7 days.