Product Analytics

Product Usage Rate

Product Usage Rate is the percentage of an eligible user population that meets the product’s active-use definition in a period. It converts an active-user count into a proportion of the available user base.

Business context

Why Product Usage Rate matters

An increase means activity is spreading across more of the eligible base. A decrease can come from fewer active users, a growing unused user pool, seasonality, or a definition change.

Business question
What share of eligible users actually uses the product during this period?
Teams that use it
Product, customer success, growth, operations, and leadership teams.
Decisions it supports
Adoption programmes, licence allocation, product education, customer outreach, and account health.
Calculation

Product Usage Rate formula

(Active Users ÷ Total Users) × 100

Formula components

Active users
Distinct users who complete the defined meaningful-use event in the period.
Total users
Distinct users eligible and able to use the product during the same period.
Usage window
The interval in which a user must complete the active event.

How to calculate Product Usage Rate

  1. Define meaningful product use and which users are eligible.
  2. Count distinct eligible users in the period.
  3. Count eligible users who complete the active event at least once.
  4. Divide active users by total eligible users and multiply by 100.
Worked example

Product Usage Rate example

A workplace product has 8,000 enabled users in September. During the month, 6,600 distinct users complete at least one core workflow.

  1. Active users = 6,600.
  2. Total eligible users = 8,000.
  3. Product Usage Rate = 6,600 ÷ 8,000 × 100 = 82.5%.

Product Usage Rate is 82.5%.

Just over four-fifths of enabled users used the product meaningfully during September.

How to interpret the result

Segment by account, role, plan, tenure, and use case. Account-wide averages can hide teams with strong adoption and others with many unused licences.

No universal target applies. Required usage frequency, product role, seasonality, seat provisioning, and the active-event threshold all affect the rate.

Common mistakes and limitations

Including users without access
Disabled, expired, or ineligible users distort the denominator.
Counting shallow activity
A login may not represent meaningful use.
Mixing user and account rates
An account with one active seat can be active at account level but weak at user level.
Ignoring user-base growth
The rate can fall when eligible users grow faster than active users.

Turn metric definitions into answers your team can use.

Vizma helps teams understand and track business metrics using their data. Bring your Product Usage Rate definition, underlying data, and reporting questions to a Vizma demo.