DSPs see their performance on AppLovin RTB by means of the same performance metrics that AppLovin uses. You access these metrics via the AppLovin DSP Report APIs.
All AppLovin numbers are final for billing. Please contact AppLovin immediately should you see discrepancies between numbers from your DSP and our API.
URL
Send report requests via an HTTP GET to the following base URL:
https://r.applovin.com/report
Example Final URL
https://r.applovin.com/report?api_key=api-key&start=2017-05-01&end=2017-05-01&report_type=dsp_report&columns=platform,country,impressions,spend&sort_impressions=DESC&limit=100&format=csv
Required Parameters
| parameter |
purpose |
usage |
| api_key |
API key. You obtain this from Account > General > Keys. |
api_key=api-key |
| start |
Dates |
start=YYYY-MM-DD |
| end |
end=YYYY-MM-DD |
| columns |
Columns. See Reporting Columns below. |
columns=api-columns |
| report_type |
Miscellany |
report_type=[dsp_report|dsp_latency] |
| format |
format=[csv|json] |
Optional Parameters
| parameter |
purpose |
usage |
| filter_x |
Filtering Columns. Replace x with the column name. Separate multiple filter values with commas. |
filter_country=us,gb |
| sort_x |
Sorting Columns. Replace x with the column name. |
sort_requests=[ASC|DESC] |
Basic Reporting Columns
| reporting column |
description |
| ad_type |
Ad type: BANNER, INTER, NATIVE |
| bundle |
|
| campaign_domain |
bid.adomain value in bid responses |
| country |
Country |
| day |
Date (MM/DD/YY) |
| device_type |
Device (Phone, Tablet, Other) |
| hour |
00:00–23:00 |
| impressions |
Impressions |
| platform |
Platform (iOS/Android/FireOS) |
| size |
Ad Size (BANNER, MREC, NATIVE, INTER, or LEADER) |
| spend |
Spend |
Latency Reporting Columns
| reporting column |
description |
| availability_zone |
Data center location |
| bids |
Successful bids by DSP |
| country |
Country |
| day |
Date (MM/DD/YY) |
| errors |
Number of unsuccessful bids by DSP + AppLovin throttled bids |
| latency |
Latency |
| platform |
Platform (iOS/Android/FireOS) |
| requests |
Requests Sent |
| response_code |
Response Code (see following table) |
| size |
Ad Size (BANNER, MREC, NATIVE, INTER, or LEADER) |
Response Codes
| code |
response text |
description |
* 200 (HTTP_OKAY) responses include bids that were filtered for the below reasons. Use the loss notification URL with the loss reason macro (AUCTION_LOSS) to get more granular details:
- invalid native markup
- invalid VAST
- bid with a blocked category
- bid with a blocked ad domain
- bid with a blocked package
|
| 100 |
HTTP_UNEXPECTED_RESPONSE |
Received an unexpected HTTP response code |
| 200 |
HTTP_OKAY* |
Successful bid response. See note below. |
| 204 |
HTTP_NO_CONTENT |
No bid response |
| 300 |
HTTP_UNEXPECTED_REDIRECT |
Temporary Redirect status response code indicates that the resource requested has been temporarily moved to the URL given by the Location headers. |
| 400 |
HTTP_BAD_REQUEST |
Request malformed |
| 403 |
HTTP_FORBIDDEN |
Forbidden response status code indicates that the server understands the request but refuses to authorize it. |
| 404 |
HTTP_NOT_FOUND |
Endpoint not found or invalid |
| 408 |
HTTP_REQUEST_TIMEOUT |
Timeout above required response time (150ms) |
| 500 |
HTTP_INTERNAL_SERVER_ERROR |
An error occurred on AppLovin’s service |
| 502 |
HTTP_BAD_GATEWAY |
Bad Gateway server error response code indicates that the server, while acting as a gateway or proxy, received an invalid response from the upstream server. |
| 503 |
HTTP_SERVICE_UNAVAILABLE |
Service Unavailable server error response code indicates that the server is not ready to handle the request. |
| 2000 |
NETWORK_ALLOCATION_ERROR |
Networking error |
| 2010 |
NETWORK_QPS_ERROR |
Networking error |
| 2020 |
NETWORK_SOCKET_ERROR |
Networking error |