---
title: Track app earnings and history with the Partner Dashboard
description: >-
  Export the list of merchants who have installed your app, understand how and
  when app earnings are paid out, and read the app history log of charge,
  credit, and install events.
source_url:
  html: 'https://shopify.dev/docs/apps/launch/distribution/track-app-usage'
  md: 'https://shopify.dev/docs/apps/launch/distribution/track-app-usage.md'
---

# Track app earnings and history with the Partner Dashboard

Your Partner Dashboard holds the business record for each of your apps: the merchants who have it installed, what you've earned, and a log of the events behind those charges. For an app's install counts, performance metrics, and logs, refer to [Monitor app performance](https://shopify.dev/docs/apps/build/dev-dashboard/monitoring-and-logs) in the Dev Dashboard.

***

## Export app data

For a more detailed list of the merchants who have installed your app, or a record of your earnings and app history, you can export the data as a CSV file:

1. From your [Partner Dashboard](https://partners.shopify.com), click **App distribution**.

2. Click the name of the app that you want to export data for.

3. Click **Export** and select what to export:

   * **Current merchants**
   * **Earnings**
   * **History**

4. Check your email inbox for a message indicating that the export was completed.

5. Open the email and click **Download CSV file** to save the CSV.

The current merchants export provides additional details, such as the type of plan merchants are on, when the app was installed, and whether it was organic or attributed to a paid ad campaign.

***

## Why install counts differ between the dashboards

The Dev Dashboard and the Partner Dashboard count installs differently, so the two sets of numbers can differ.

The **Installs** card on an app's **Overview** in the Dev Dashboard counts every store whose installation is still on record, which is installs minus uninstalls.

The Partner Dashboard's **Merchants with your app** metric counts only active stores: those on a paid or trial plan, staff stores, and development stores, but not stores that are canceled or frozen.

The two match when every store with your app is active. The Dev Dashboard number is the larger one when any of them isn't.

For definitions of **Installs**, **Install events**, and **Uninstall events**, refer to [Monitor app performance](https://shopify.dev/docs/apps/build/dev-dashboard/monitoring-and-logs#growth).

***

## Earnings

The earnings amount refers to how much an app developer has been paid. It includes both paid out amounts and pending payments, and it reflects the deduction of Shopify's revenue share and any application credits. Your share of the revenue is defined in the [Shopify Partner revenue share](https://help.shopify.com/en/partners/partner-program/how-to-earn#apps) agreement.

Payments occur after a merchant has paid their Shopify invoice. The payment schedule depends on the type of charges made by the app:

* For a `RecurringApplicationCharge`, it can take up to 37 days from the time a merchant agrees to the charge to the time that the charge appears as an earning in your Partner Dashboard.
* For an `ApplicationCharge`, merchants are invoiced immediately and the charge will appear as an earning in your Partner Dashboard within 7 days.

If your app uses [Shopify App Pricing](https://shopify.dev/docs/apps/launch/billing/shopify-app-pricing), Shopify creates the subscription and usage charges for you, and the same schedules apply to those charges.

***

## App history

Important user interactions with your app are tracked as events, which you can view in the app history log in your Partner Dashboard. The app history log displays all the tracked events for your app, with the most recent events appearing at the top. The following events are available:

* [Application charge events](#application-charge-events)
* [Application credit events](#application-credit-events)
* [Application install events](#application-install-events)
* [Recurring charge events](#recurring-charge-events)
* [Usage charge events](#usage-charge-events)

**Shopify App Pricing:**

These events also apply to apps that use [Shopify App Pricing](https://shopify.dev/docs/apps/launch/billing/shopify-app-pricing). When merchants subscribe to your plans, Shopify creates the underlying charges, and the matching events appear in your app history. You can also query these events programmatically with the Partner API's [historical events](https://shopify.dev/docs/api/partner/historical-events).

### View app history

1. From your [Partner Dashboard](https://partners.shopify.com), click **App distribution**.
2. Click the name of your app.
3. Click **App history**.

### Application charge events

The following table includes definitions of application charge events:

| Charge accepted | The `ApplicationCharge` has been accepted by the merchant but not activated by the developer. |
| - | - |
| Charge activated | The `ApplicationCharge` has been activated by the app developer and will appear on the merchant's next invoice. |
| Charge declined | The `ApplicationCharge` has been declined by the merchant. |
| Charge expired | The merchant has taken no action 48 hours after being presented with an `ApplicationCharge` (for example, the merchant has not accepted or declined the charge). |

### Application credit events

The following table includes definitions of application credit events:

| Credit applied | The `ApplicationCredit` has been added to the store. Funds are deducted from the app developer's upcoming payment. |
| - | - |
| Credit failed | The `ApplicationCredit` was not added. Reasons why a credit could not be added include:- `ApplicationCredit` amount exceeds the amount paid from the store owner to the app developer in the last 30 days
- App developer does not have available funds to credit the store (pending receivables is less than credit amount) |
| Credit pending | The `ApplicationCredit` has been created but it has either failed or not yet been applied. |

### Application install events

The following table includes definitions of application install events:

| Installed | The app was installed on the store. An install occurs after a merchant approves the permissions shown on the OAuth grant screen. |
| - | - |
| Uninstalled | The app was uninstalled from the store. An uninstall occurs after a merchant has removed an app from their store. |

### Recurring charge events

The following table includes definitions of recurring charge events:

| Recurring charge accepted | The `RecurringApplicationCharge` has been accepted by the merchant but not activated by the developer. |
| - | - |
| Recurring charge activated | The `RecurringApplicationCharge` has been activated by the app developer and will appear on the merchant's next invoice. |
| Recurring charge canceled | The merchant has canceled the existing `RecurringApplicationCharge`. Examples of a canceled charge event include:- merchant has uninstalled the app
- merchant has changed app plan type
- merchant no longer wants to pay for the app |
| Recurring charge declined | The `RecurringApplicationCharge` has been declined by the merchant. |
| Recurring charge expired | The merchant has taken no action 48 hours after being presented with a `RecurringApplicationCharge` (for example, the merchant has not accepted or declined the charge). |
| Recurring charge frozen | The `RecurringApplicationCharge` has been suspended. Future payments for the app are on hold until the charge is unfrozen. Examples of a frozen charge event include:- merchant no longer has an active Shopify subscription |
| Recurring charge unfrozen | The `RecurringApplicationCharge` has been reactivated. A new billing cycle will commence on the day the `RecurringApplicationCharge` is unfrozen. Examples of an unfrozen charge event include:- merchant has resumed an active Shopify subscription |

### Usage charge events

The following table includes definitions of usage charge events:

| Usage charge applied | After a merchant has agreed to a `UsageCharge`, a `UsageCharge` is applied after the charge is created. |
| - | - |

***
