Use this Reporting API to get aggregated campaign data in either JSON or CSV format.
Request Format
Make report requests by sending HTTP GET requests to one of the following base URLs:
https://r.applovin.com/reporthttps://r.applovin.com/probabilisticReport(For advertising only. All values derived from installs and spend are based on probabilistic install data.)
Required Parameters
| Parameter | Purpose |
|---|---|
api_key |
the advertiser’s API key for Reporting (a.k.a. Report Key) You can find this Report Key in the Keys tab of the account page in your AppLovin dashboard. If the value is missing, please send an email to support@applovin.com and include the email address associated with your account. |
start |
the start date of the report Accepts a date in YYYY-MM-DD format or a Unix timestamp. For example, |
end |
the end date of the report Accepts date in YYYY-MM-DD format or a Unix timestamp. For example, |
format |
the format for the report Accepts |
columns |
a comma-separated list of columns for the report See the allowed columns below. For example, |
report_type |
tells the API to respond with If this parameter is omitted, the API will default to |
Optional Parameters
| Parameter | Purpose |
|---|---|
limit |
the limit on the number of rows returned, for example, 500 |
offset |
the offset to begin fetching rows at, for example, 100 |
having |
allows complex filtering on numeric values This parameter accepts URL-encoded values of numeric columns, comparison operators, and logical operators, for example: Note: This will slow down the response and increase the likelihood of timeouts. |
Allowed Publisher Columns
| Column Name | Contains |
|---|---|
day |
date of reporting data |
hour |
hour of reporting data (only available for the past 30 days) |
impressions |
number of impressions |
clicks |
number of clicks |
ctr |
number of clicks ÷ number of impressions |
revenue |
money earned |
ecpm |
money earned per 1000 impressions |
country |
two letter country code |
ad_type |
GRAPHIC, PLAY, VIDEO, REWARD, or MRAID |
size |
ad size (INTER, BANNER, MREC, LEADER, or NATIVE) |
device_type |
phone, tablet, or other |
platform |
android, ios, fireos, or tvos |
application |
app name |
package_name |
apps package name or bundle ID |
store_id |
the numeric portion of the iTunes ID on iOS, and the package_name otherwise |
placement |
placement name |
application_is_hidden |
is the app hidden in the dashboard |
zone |
Zone name, if available to your account |
zone_id |
Zone ID, if available to your account Please contact your account manager if you are interested in using Zones. |
bidding_integration |
the integration that AppLovin is bidding through to serve ads (e.g. MAX or Admob Open Bidding) If you have a traditional integration, this column will contain |
Allowed Advertiser Columns
| Column Name | Contains |
|---|---|
day |
date of reporting data |
impressions |
number of impressions |
clicks |
number of clicks |
ctr |
number of clicks ÷ number of impressions |
conversions |
number of conversions (installs) |
conversion_rate |
number of conversions ÷ number of clicks |
average_cpa |
average cost per conversion |
average_cpc |
average cost per click |
ad |
ad name |
country |
two letter country code |
campaign |
campaign name |
app_id_external |
hashed application ID (commonly referred to as “site ID”) |
traffic_source |
AppLovin, or the name of the exchange |
ad_type |
GRAPHIC, VIDEO, REWARD, or PLAY |
cost |
advertiser spend |
sales |
count of attributed sales events (requires setting up revenue postbacks) |
first_purchase |
count of users that made their first purchase (requires setting up revenue postbacks) |
size |
ad size (INTER, BANNER, MREC, LEADER, or NATIVE) |
device_type |
phone, tablet, or other |
platform |
android, ios, fireos, or tvos |
campaign_package_name |
package name or Bundle ID of the app being promoted |
campaign_store_id |
the numeric portion of the iTunes ID of the promoted app on iOS and the camaign_package_name otherwise |
campaign_id_external |
unique reference to a campaign This doesn’t change when the campaign is renamed. It is the same value as the |
campaign_ad_type |
ua for user acquisition, or rt for retargeting |
Filtering Columns
You can filter reports by any column. When you do so, you search for a direct match to any of the filters.
To filter by a column, add the following URL parameter: filter_columnname=onefilter,anotherfilter,thirdfilter
For example, if you want to see data only for the Android platform, set the following URL parameter: filter_platform=Android
See the table above for a list of all columns.
Sorting Columns
You sort reports in a similar way to how you filter reports.
For example, to sort a report by campaign_name, add the following URL parameter: sort_campaign_name=ASC
The accepted values are ASC for ascending or DESC for descending. All sorts are lexicographical sort.
Report Formats
You can request reports in two formats: JSON or CSV.
Time Zone
All data in the reporting API is in UTC (Coordinated Universal Time).
Example Requests
Example advertiser request:
https://r.applovin.com/report?api_key=YOUR_API_KEY&start=2015-04-20&end=now&columns=day,campaign,impressions,clicks,ctr,conversions,conversion_rate,app_id_external,cost,sales&format=json&report_type=advertiser
Example publisher request:
https://r.applovin.com/report?api_key=YOUR_API_KEY&start=2016-07-01&end=2016-07-07&columns=day%2Cplatform%2Ccountry%2Capplication%2Cpackage_name%2Csize%2Cad_type%2Cimpressions%2Cclicks%2Crevenue,device_type&having=impressions%20%3E%200%20AND%20revenue%20%3E%200&format=csv