AppLovin Ads [ARCHIVED]
This source syncs advertiser-side reporting data from AppLovin. It covers app campaign reporting, web campaign reporting, and asset (creative) level reporting.
MAX publisher and monetization reporting (/maxReport, /maxCohort) is not covered by
this connector, and neither are the campaign management or Conversions APIs — those use
different hosts and different credentials.
API documentation:
- Reporting API (app campaigns)
- Web Reporting API (web campaigns)
- Asset Reporting API
Prerequisites
- An AppLovin account with reporting access.
- A Report Key. In the AppLovin dashboard, click your account name in the top right and select Keys. The Management Key, Campaign Management Key, and CAPI Key are different credentials and do not work for reporting.
Configuration
| Input | Type | Description | Default Value |
|---|---|---|---|
api_key | string | Report Key. | |
start_date | string | UTC date to start replicating from (YYYY-MM-DD). | |
end_date | string | UTC date to replicate up to, inclusive (YYYY-MM-DD). | today |
lookback_window | integer | Days before the last synced date to re-request on each incremental sync. | 3 |
attribution_mode | string | Attribution mode for web_report_daily: click or click_and_view. | click |
num_workers | integer | Number of streams to sync concurrently. | 2 |
Streams
| Stream Name | Endpoint | Primary Key | Pagination | Supports Full Sync | Supports Incremental |
|---|---|---|---|---|---|
| advertiser_report_daily | /report | day.campaign_id_external.creative_set_id.country.platform.placement_type | Offset | ✅ | ✅ |
| web_report_daily | /webReport | day.campaign_id_external.creative_set_id.country.platform.placement_type | Offset | ✅ | ✅ |
| asset_report_daily | /assetAnalyticsReport | date.asset_id.campaign_id.creative_set_id | Offset | ✅ | ✅ |
Use advertiser_report_daily for app install campaigns and web_report_daily for campaigns
driving traffic to a website. They are separate AppLovin endpoints with different column
sets: only the web report exposes checkout, ROAS, and new-customer metrics such as
nc_d0_checkouts and chka_usd_7d, and only the app report exposes install metrics such as
conversions.
Incremental syncs and restated data
Every stream requests one day at a time, so each record belongs to a single date.
advertiser_report_daily and web_report_daily cursor on the API's native day column;
asset_report_daily has no day dimension, so the connector adds the requested date as
date and cursors on that.
AppLovin restates recent metrics as attribution data arrives, so the lookback_window
re-requests the most recent days on every sync. With a deduplicating sync mode, the
composite primary keys cause restated rows to overwrite the previously synced values.
Data for yesterday is stable after 06:00 UTC.
Request windows
AppLovin serves a limited history, and dates outside the window return an error rather than an empty result:
| Endpoint | Window |
|---|---|
/report | 45 days |
/webReport | 90 days |
/assetAnalyticsReport | 45 days |
The connector clamps start_date to the oldest day each endpoint still serves, so a
start_date further back than the window syncs the available history instead of failing.
Backfilling more history than the window allows is not possible through this API.
Requesting other columns
Each stream requests a fixed column set. AppLovin exposes many more columns, including
hourly and longer attribution windows. To add them, edit the stream's columns request
parameter and the corresponding schema in manifest.yaml; the schemas allow additional
properties, so extra columns pass through even if they are not declared.
Reference
No configuration specification is available for this connector.
Changelog
Expand to review
| Version | Date | Pull Request | Subject |
|---|---|---|---|
| 0.1.0 | 2026-07-30 | 83270 | Initial release: advertiser_report_daily, web_report_daily, asset_report_daily |