Set up tax and store commission rates with the Net Revenue API

Premium
For:
Marketers
Last update:

At a glance: Configure how AppsFlyer calculates net revenue for in-app purchases and subscriptions by using the Net Revenue API to customize store commission rates and tax rules per app. This ensures that your reports accurately reflect actual earnings, including cases with non-standard commission fees or specific tax rules.

The ROI360 store revenue product calculates the net revenue of in-app purchases and subscriptions by automatically deducting store commission and tax from gross revenue. The default configuration reflects standard commission fees and tax rules applied by the App Store and Google Play. If your store commission differs or if you operate in a country with special tax treatment, use the Net Revenue API to override the default configuration.

The Net Revenue API is implemented through two REST APIs that let you configure store commission rates and tax rules for individual apps.

  • Store commission rates: Create, update, get, or delete store commission rates for one or more apps. Each app can have a specific commission rate based on various store programs.
  • Tax rate rules: Create or get custom tax rate rules for a specific app.

For more information about how net revenue is calculated, see Net revenue.

 Note

Net revenue is displayed in raw data reports only. The dashboards only display gross revenue of purchases and subscriptions.

Update tax rate rules

Tax is reported by default for any transaction measured by ROI360 using the default tax rate configuration. In tax-inclusive countries, where tax is included in the list price, net revenue is calculated after deducting tax. For example, in the UK, AppsFlyer deducts the sum of the tax and the store commission. In tax-exclusive countries, such as the US, where the list price does not include tax, the revenue and net revenue parameters do not include tax by default.

To set the tax rate rules using the Net Revenue API, follow these steps:

  1. Complete the following steps in your ROI360 store revenue settings:

    iOS

    Android

  2. Give your developer the following:
    • The API V2 token to use as the authorization key.
    • The parameters and values that specify which taxes to calculate are outlined in the table that follows.
  3. Instruct your developer to use the Tax rates REST API to create tax rate rules. The API accepts a JSON file in the body of the POST request. This JSON file includes all supported countries and their default tax rates. Your developer can edit the file or use it as-is in the API.

Tax Rate API parameters

Parameter Mandatory Remarks
tax_name Yes
  • Name appearing in the customer invoice that describes the specific type of tax. 
  • Example: Sales, VAT, GST
tax_rate Yes
  • Value must be greater than 0. <br>- Number up to 4 decimal places representing the tax percentage to be collected.
  • Example: 7.25
tax_exclusive No
  • Boolean parameter, either true or false. 
  • False means tax is included in the overall revenue. 
  • True means tax is in addition to the overall stated revenue. For example, in the USA or Canada, where the list price doesn't include sales tax.
  • Default is false.
country No
  • Two-letter ISO country code for which the tax is applied. 
  • Example: CA
  • Note: For United Kingdom, the code implemented is UK, not GB.
subdivision No
  • For some countries, there can be an additional state or subdivision. 
  • Handled according to ISO 3166-2 subdivision codes. 
  • Must include the country code and subdivision code. 
  • Example: US-CA
postal_code No
  • String of letters and/or numbers. 
  • Example: L4J8E3
deduction_order No
  • Enum, either 0, 1, or 2: 
    • 0 means store commission is deducted first from the gross revenue and tax is deducted from the remaining amount. 
    • 1 means tax is deducted first from the gross revenue and store commission is deducted from the remaining amount. 
    • 2 means that both tax and store commission are deducted from the total revenue.

Set up store commission rates

By default, AppsFlyer applies standard store commission logic when calculating net revenue. App Store defaults are region-specific (see About ROI360 store revenue for the current rates per storefront). If your app operates under reduced or non-standard store fees, use the Net Revenue API to override the store commission rate at the app level.

A few examples:

  • Your app qualifies for reduced store fees, such as:
    • Apple App Store Small Business Program (15% commission; 12% in China mainland (CN))
    • Google Play 15% service fee tier (first USD 1M in annual earnings)
  • Your store commission changes over time, and because AppsFlyer has no visibility into your store commission status, you need to update the applied rate manually using the Net Revenue API, for example:
    • Applying a reduced commission when your app becomes eligible for a lower store fee
    • Reverting to the default store commission logic when the reduced rate no longer applies

Update store commission with the Net Revenue API

You can use the Net Revenue API to manage store commission configurations in the following ways:

  • Review existing configurations by sending a GET request to retrieve store commission rates for apps under the account
  • Apply a custom commission by sending a POST request with the required commission rate
  • Revert to the default logic by sending a DELETE request for the relevant app

Before using the API:

  1. Complete the following steps in your ROI360 store revenue settings:

    iOS

    Android

  2. Prepare the following information:
    • API V2 token to use as the authorization key
    • Store commission rate to apply (supported values: 1%–30%)
    • App ID(s) to which the custom commission applies
  3. Note the following configuration details:
    • Store commission is configured per app
    • Supported values are 1%–30%
    • The configuration applies only to new incoming events
    • If no custom commission is set, AppsFlyer uses the default store commission logic

For full request structures and examples, see the Net Revenue API documentation.