Usage model

The usage model stores time-series measurements of how accounts consume dimensions defined on plans and subscriptions (for example seats consumed, API credits, storage). It powers utilization views such as license utilization percentages when those features are enabled.

Prerequisites

• Accounts model
• Plans and Subscriptions should define dimension keys so usage rows align with entitlements

Field reference

Model keys

Property	Type	Description
account_id	string	Account being measured.
dimension	string	Name of the dimension being reported; must match a key from plan or subscription dimensions for consistent rollups.
timestamp	timestamp	Time the measurement applies to (sample time, period end, etc.).

Default properties

Property	Type	Description
value	json	Measured usage. Often a number; JSON type allows structured payloads if your pipeline requires it. Parse expectations follow your workspace configuration.

Configure

1. Add model → Usage.
2. Provide a query that emits one row per account, dimension, and timestamp (or grain you use).
3. Map columns exactly to account_id, dimension, timestamp, and value.
4. Validate, save, refresh.
5. Confirm utilization or usage-driven widgets on Accounts for test accounts.

Tips

• Keep dimension strings stable across plan, subscription, and usage models.
• If you aggregate usage in the warehouse, ensure timestamp reflects the period your charts expect (for example daily buckets).

Related

• Plans
• Subscriptions
• Data models overview