Account usage metrics

Usage metrics are located on the Usage tab under Account settings. These usage metrics tell you more about how your application and members of your organization are using LaunchDarkly.

Understanding project and account MCI

Project MCI and account MCI are not always the same number. LaunchDarkly counts unique context instances for a specific project or environment. Contexts can be active in multiple projects or environments, contributing to the unique context counts in each. The Overview tab shows the unique client MCI at the account level, while the Client tab can show all the unique MCI from each named project or from each named environment.

For example, you may have 10,000 contexts in Project A and 10,000 contexts in Project B, but if there is any overlap in the user base your account will have fewer than 20,000 total unique context keys.

Here's a diagram showing the overlap in contexts between Project A and Project B:

Here's how many keys each project might have:

• 3,000 unique context instances in Project A
• 3,000 unique context instances in Project B
• 7,000 context instances that exist in both Projects A and B
• 13,000 total unique context instances

Calculating client-side MCI

LaunchDarkly calculates client-side MCI as unique context instances that evaluate, initialize, or identify any flag from a client-side SDK over a rolling 30-day period. The amount of these context instances is designated per account.

Your usage is based on the total number of unique client-side context instances across your entire account, regardless of anonymity or whether the context is currently visible on the Contexts list. Uniqueness is defined as unique pairs of context kinds and keys. Custom attributes do not affect client-side MCI uniqueness. LaunchDarkly does not bill for server-side MCI.

MCI billing

LaunchDarkly bills for client-side context instances in the following ways:

• Each unique context instance counts as one client-side MCI.
• A context instance can be just one context, or a group of contexts that LaunchDarkly evaluates together as a multi-context. LaunchDarkly bills multi-contexts as one client-side MCI.
• If you add or remove a context from an existing multi-context, LaunchDarkly considers the new context instance unique and counts it as an additional client-side MCI.
• If you change an existing context's key, LaunchDarkly considers the new context instance unique and counts it as an additional client-side MCI.
• If a context contains a single context, such as a "user," but has multiple keys, each unique key counts as one client-side MCI.

To learn more, read Contexts and context kinds.

Here are examples of evaluation contexts, and how LaunchDarkly would count them toward client-side MCI:

// LaunchDarkly counts this as one client-side MCI
Context = {
  "kind": "user",
  "key": "context-key-123abc"
}
COPY

If contexts evaluate flags in your Relay Proxy, we also count each context instance as one client-side MCI over the 30-day period.

Understanding client-side MCI limits

Your LaunchDarkly plan includes a client-side MCI limit. We understand that a company's user base can grow unexpectedly over time. We never stop or throttle service if you exceed your client-side MCI limit, nor do we bill you for client-side MCI overages. All contexts will continue to receive feature flags correctly, regardless of the amount of your client-side MCI.

Context instances live on the Contexts list for 30 days from their last evaluation. If you exceed your client-side MCI limit, LaunchDarkly will begin deleting the oldest context instances on the list to make room for new context instances, even if they are not yet more than 30 days old. LaunchDarkly continues to delete old context instances as new ones are added to keep the list at no more than your contracted limit.

If you have configured LaunchDarkly to use anonymous contexts, that can impact your client-side MCI as well. To learn more, read Managing anonymous contexts and MCI.

Usage metrics are located on the Usage tab under Account settings. These usage metrics tell you more about how your application and members of your organization are using LaunchDarkly.

Understanding project and account MAU

Project MAU and account MAU are not always the same number. LaunchDarkly counts unique user contexts for a specific project or environment. User contexts can be active in multiple projects or environments, contributing to the unique context counts in each. The Overview tab shows the unique client MAU at the account level, while the Client tab can show all the unique MAU from each named project or from each named environment.

For example, you may have 10,000 user contexts in Project A and 10,000 user contexts in Project B, but if there is any overlap in the user base your account will have fewer than 20,000 total unique user context keys.

Here's a diagram showing the overlap in user contexts between Project A and Project B:

Here's how many keys each project might have:

• 3,000 unique keys in Project A
• 3,000 unique keys in Project B
• 7,000 keys that exist in both Projects A and B
• 13,000 total unique keys

Calculating client-side MAU

LaunchDarkly calculates client-side MAU as unique user context keys that evaluate, initialize, or identify any flag from a client-side SDK over a rolling 30-day period. The amount of these context instances or users is designated per account.

Your usage is based on the total number of unique client-side user contexts across your entire account, regardless of anonymity or whether the user context is currently visible on the Contexts list. Uniqueness is defined as unique user context keys. Custom attributes do not affect client-side MAU uniqueness. LaunchDarkly does not bill for server-side MAU.

MAU billing

LaunchDarkly bills for client-side monthly active users in the following ways:

• Each unique user context counts as one client-side MAU.
• If you change an existing user context's key, LaunchDarkly considers the new user context unique and counts it as an additional client-side MAU.

Understanding client-side MAU limits

Your LaunchDarkly plan includes a client-side MAU limit. We understand that a company's user base can grow unexpectedly over time. We never stop or throttle service if you exceed your client-side MAU limit, nor do we bill you for client-side MAU overages. All user contexts will continue to receive feature flags correctly, regardless of the amount of your client-side MAU.

User contexts live on the Contexts list for 30 days from their last evaluation. If you exceed your client-side MAU limit, LaunchDarkly will begin deleting the oldest user contexts on the list to make room for new user contexts, even if they are not yet more than 30 days old. LaunchDarkly continues to delete old user contexts as new ones are added to keep the list at no more than your contracted limit.

If you have configured LaunchDarkly to use anonymous user contexts, that can impact your client-side MAU as well. To learn more, read Managing anonymous contexts and MCI.