No results for ""
EXPAND ALL
  • Home
  • API docs

GIVE DOCS FEEDBACK

Account usage metrics

Read time: 4 minutes
Last edited: Mar 25, 2024

Overview

This topic explains how to understand the billing and usage metrics visualized in the Account settings page. It also describes billing models based on contexts and monthly active users (MAU).

Understanding the Usage tab

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.

The Usage tab includes the following subtabs:

Overview

The Overview tab displays your plan usage, primary contexts, Experimentation keys or events, and Data Export events, as well as the server connections and service connections your organization is using.

The Overview tab shows the contexts at the account level, while the Client tab can show all the contexts from each named project or from each named environment. If the same context is present in multiple environments or projects, it still counts only once toward your context count.

Client

The Client tab displays contexts and client connections, depending on your billing model. You can narrow these charts by date range, SDK, and project/environment. You can also narrow the contexts chart by context kind.

Experiments

If you use Experimentation, the Experiments tab displays each day's cumulative number of Experimentation keys or events, depending on your billing model, for the current calendar month. You can narrow the views by context kind, project/environment, or date range.

Experimentation keys include the total number of unique context keys, from server-side, client-side, and edge SDKs, included in each experiment:

  • if the same context key is in one experiment multiple times, LaunchDarkly counts it as one Experimentation key
  • if the same context key is in two different experiments, LaunchDarkly counts it as two Experimentation keys

If you are on an annual billing plan, you commit to a certain number of Experimentation keys each month. If you consistently go over your plan limits, averaged over a quarter, we will "true forward" your contract based on your actual average use. To learn more about your Experimentation billing plan, contact your LaunchDarkly representative.

Data Export

If you use Data Export, the Data Export tab displays each day's cumulative number of events published in the current calendar month. You can narrow the views by project and environment or date range.

Server

The Server tab displays server MAUs and server connections. You can narrow the views by SDK, project, environment, and date range.

You can also use the REST API: Account usage

Calculating client-side billing

Depending on your billing model, you may be billed by contexts or by monthly active users (MAU). Click on each section below to understand how each is calculated:

Expand Billing by contexts

Some customers are billed by contexts. LaunchDarkly only charges for contexts from your primary context kind.

Unless otherwise specified in your agreement with LaunchDarkly, the primary context kind is the context kind with the highest volume of monthly activity. LaunchDarkly calculates this as the context kind with the largest number of unique contexts that evaluate, initialize, or identify any flag from a client-side SDK over a given calendar month. By default, the primary context kind is set to user. Only the client-side activity of a primary context kind is factored into billing.

Your usage is based on the total number of unique contexts of the primary context kind across your entire account, regardless of anonymity or whether the context is currently visible on the Contexts list.

Uniqueness is defined as unique context keys. If you change an existing context's key, LaunchDarkly considers the new context unique and counts it as an additional context instance of the given context kind. Custom attributes do not affect uniqueness. Each unique context of a particular context kind contributes the cardinality of that context kind. It does not matter whether the context is part of a multi-context.

Expand Billing by MAU

Some customers are billed by client-side monthly active users (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 calendar month. The amount of these user contexts 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. 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. Custom attributes do not affect client-side MAU uniqueness.

To learn more about your client-side usage billing model, contact your LaunchDarkly representative.

Understanding client-side MAU limits

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

Context instances live on the Contexts list for 30 days from their last evaluation, or until your account reaches 100,000,000 context instances. To learn more, read Context storage.

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