Metered features

• Reported usage (Usage meters)
  Use this option when your application calculates usage and reports it directly to Stigg.
  This is commonly used for features such as seats.
• Raw events (Event meters)
  Use this option when your application emits raw events that Stigg aggregates to calculate usage.
  This is commonly used for features such as monthly active users (MAUs).

​

Usage meters

1. Open the Product catalog in the Stigg Console.
2. Navigate to the Features section.
3. Click + New feature.
4. In the modal that opens, provide the following details:
   1. Name — The display name of the feature.
   2. Description (optional) — A short explanation of what the feature enables.
   3. ID — Automatically generated by Stigg and used to reference the feature in your application.
      You can override this value by clicking Edit and linking an existing feature.
   4. Feature type — Choose Meter.
   5. Meter type - Choose Calculated usage.
   6. If required, edit the singular and plural unit names — for example, day and days.
   7. If you report usage in a higher granularity (for example, bytes) but want to present it to customers in a lower granularity (for example, GB), enable the Feature is sold in different units toggle. For details on configuring unit conversion and rounding behavior, see Reporting usage in one unit and presenting it in another.

5. Click Create to save the feature.

​

Event meters

1. Open the Product catalog in the Stigg Console.
2. Navigate to the Features section.
3. Click + New feature.
4. In the modal that opens, provide the following details:
   1. Name — The display name of the feature.
   2. Description (optional) — A short explanation of what the feature enables.
   3. ID — Automatically generated by Stigg and used to reference the feature in your application.
      You can override this value by clicking Edit and linking an existing feature.
   4. Feature type — Choose Meter.
   5. Meter type - Choose Raw events.
5. Click Next.
6. Define the event filters:
   1. Set the primary filter based on the reported event name.
   2. Add additional conditions to exclude unwanted events.
7. Select the aggregation method that Stigg will use to calculate each customer’s usage:
   • Count
   • Count unique
   • Sum
   • Max
   • Min
   • Average
   All aggregation methods except Count require specifying an event property that will be used for the aggregation. For example, when calculating a Sum, you must select which property should be summed.
8. Click Next.
9. If required, edit the singular and plural unit names, for example: “seat” and “seats”.
10. If you report usage in a higher granularity (for example, bytes) but want to present it to customers in a lower granularity (for example, GB), enable the Feature is sold in different units toggle. For details on configuring unit conversion and rounding behavior, see Reporting usage in one unit and presenting it in another.

11. Click Create.

​

Reporting usage in one unit and presenting it in another

• Usage is reported to Stigg in the original (high-granularity) unit, such as bytes.
• Throughout the Stigg app and SDKs, usage values are returned in the presented (lower-granularity) unit, such as GB.
• When integrated with a billing provider, usage in the presented unit is rounded up to the nearest integer.

​

Enable unit conversion for a feature

1. Open the feature configuration.
2. Toggle on Feature is sold in different units.
3. Enter the name of the unit that will be presented to customers (for example, GB).
4. Define the conversion rate between the reporting unit and the presented unit
   (for example: 1 GB = 1,000,000,000 bytes).
5. Save the feature.

​

Using the feature in plans

• Any plan that includes this feature will display usage in the presented unit.
• Usage reported in the original unit will automatically be converted and shown consistently across the Stigg UI, SDKs, and billing flows.