> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/feature-management-experimentation/management-and-administration/account-usage.md).

# Usage Data

Learn how to view and manage your usage, billing details, and account limits in Harness FME.

This page describes the usage reports, billing details, and service limits available in Harness Feature Management & Experimentation (FME). Navigate to the **Usage** and **Billing and limits** pages in **FME Settings** to access the following information:

* [Usage metrics](#view-usage-data) such as Monthly Tracked Keys (MTKs), impressions, and events
* [SDK usage](#view-sdk-usage-data), displaying which SDKs are actively sending traffic
* [Account-level billing information and service limits](#view-billing-and-service-limits)

{% hint style="danger" %}
**UPCOMING CHANGE TO USER-BASED BILLING**

Harness FME is transitioning away from seat-based pricing. **User seats** will be replaced with active users, defined as any user who accesses an FME capability (including view-only usage).

Until this update rolls out, the **Billing and limits** page will continue to show registered seats.
{% endhint %}

{% tabs %}
{% tab title="Usage" %}
Harness FME provides three primary usage metrics on the **Usage** tab, and usage data (MTKs, impressions, and events) updates daily.

#### Monthly Tracked Keys (MTKs) <a href="#monthly-tracked-keys-mtks" id="monthly-tracked-keys-mtks"></a>

Monthly Tracked Key (MTKs) are the number of unique [traffic type identifiers](/feature-management-experimentation/management-and-administration/traffic-types.md) (e.g. users) evaluated by an SDK in a calendar month.

* MTKs represent the number of unique keys evaluated for treatments.
* Keys are de-duplicated across projects, environments, traffic types, and feature flags.
* A key evaluated across multiple flags or traffic types counts once.
* MTKs do not represent impressions.
* MTKs typically approximate the number of unique end users interacting with your application.

#### Impressions <a href="#impressions" id="impressions"></a>

[Impressions](/feature-management-experimentation/use-fme/feature-management/monitoring-and-analysis/impressions.md) are unique event records generated each time an SDK evaluates a treatment for a tracked key.

#### Events <a href="#events" id="events"></a>

[Events](/feature-management-experimentation/use-fme/release-monitoring/events/index.md) capture user or system behavior.

For example:

* Page views
* Button clicks
* Transaction metadata
* Performance metrics such as response time

### View usage data <a href="#view-usage-data" id="view-usage-data"></a>

To access your usage data:

1. From the FME navigation menu, click **FME Settings**.
2. Under **Account Settings**, select **Usage**.

![](https://1473625385-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrT2RGHAjtBTaObzchfpb%2Fuploads%2Fgit-blob-4b91afdb0874ca5b6baf0ab03e0fa736579f6807%2Fusage-1.png?alt=media)

You can export each usage report as a CSV file by clicking the **Download CSV by environment and project** link under each chart.

{% hint style="info" %}
For additional usage data, contact [Harness Support](/feature-management-experimentation/troubleshooting-and-resources/fme-support.md).
{% endhint %}
{% endtab %}

{% tab title="SDK Usage" %}
Harness FME displays which SDKs are actively sending traffic over the last seven days on the **SDKs** tab.

This data helps you monitor:

* Which SDKs are integrated in your application
* The environment each SDK is reporting from
* The version that is currently detected vs. the latest available version

If a newer version is available, update the SDK to ensure compatibility and access to the latest features.

### View SDK usage data <a href="#view-sdk-usage-data" id="view-sdk-usage-data"></a>

To access your SDK usage and versioning data:

1. From the FME navigation menu, click **FME Settings**.
2. Under **Account Settings**, select **Usage** and click on the **SDKs** tab.

![](https://1473625385-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrT2RGHAjtBTaObzchfpb%2Fuploads%2Fgit-blob-be3df016afadd5862af6fe9f41701647e4f4e520%2Fusage-2.png?alt=media)
{% endtab %}

{% tab title="Billing and Service Limits" %}
On the **Billing and limits** page, you can view the following:

* Your current billing plan
* Plan expiration date
* Support plan
* Billing limits (for example, MTKs and user seats)

The **Service limits** section includes a table that displays your usage toward FME object-level limits and any feature-gated consumption thresholds. These limits help ensure platform reliability and prevent unexpected usage spikes.

### View billing and service limits <a href="#view-billing-and-service-limits" id="view-billing-and-service-limits"></a>

To access your billing and service limits data:

1. From the FME navigation menu, click **FME Settings**.
2. Under **Account Settings**, select **Billing and limits**.

![](https://1473625385-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrT2RGHAjtBTaObzchfpb%2Fuploads%2Fgit-blob-8f401cc83c1df46404efc37407cb9ad370ec33b1%2Fusage-3.png?alt=media)

{% hint style="info" %}
Service limits do not affect billing. Harness FME service limits require that you request limit increases manually by contacting [Harness Support](/feature-management-experimentation/troubleshooting-and-resources/fme-support.md).
{% endhint %}
{% endtab %}
{% endtabs %}

{% @harness-feedback/feedback %}
