Appbroda
Appbroda is an advertising/monetization reporting connector that extracts performance data from the Appbroda Reporting API and syncs it to your destination on a schedule.
Source Setup Guide
To connect Appbroda to Extract, you’ll need:
- API token (Bearer token)
Getting an API token
Obtain an API token from your Appbroda account/admin. The connector authenticates all requests using Authorization: Bearer <token>.
Connection Setup Guide
Once you connected Appbroda to a destination, you will also need to configure:
- Connection Pull Schedule: Determines how frequently data is extracted from the source.
- Backfill (Days): Specifies the duration for which historical data will be retrieved during each connection run.
- Destination specific settings: different settings such as "Dataset Name" or "Target Schema" (depanding on your destination)
- Schema Migration Policy: Controls how Extract will handle schema changes from the sourcee source.
Date range behavior (important)
This connector syncs data using a date cursor and your configured Backfill (Days).
To improve reliability and avoid overly large report requests, the connector splits the requested date range into 7-day chunks and requests/polls each chunk separately. This is internal behavior; you do not need to configure anything for chunking.
Authentication
- Method: Bearer token
- Header:
Authorization: Bearer <api_token>
Configuration Reference
Source configuration
| Field | Type | Required | Description |
|---|---|---|---|
api_token | string | ✅ | Appbroda API token used for Bearer authentication. |
Connection configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Pull schedule | — | ✅ | How often Extract runs the sync. |
| Backfill (Days) | integer | ✅ | Number of days of historical data to include on each run. |
| Destination settings | — | ✅ | Destination-specific options (dataset/schema, etc.). |
| Schema migration policy | — | ✅ | How schema changes are handled. |
Connector Information
Report request details
The connector requests a performance report with the following characteristics:
-
Metrics
AD_EXCHANGE_LINE_ITEM_LEVEL_IMPRESSIONSAD_EXCHANGE_RESPONSES_SERVEDAD_EXCHANGE_LINE_ITEM_LEVEL_CLICKSAD_EXCHANGE_TOTAL_REQUESTSAD_EXCHANGE_LINE_ITEM_LEVEL_AVERAGE_ECPMAD_EXCHANGE_ESTIMATED_PAYOUT
-
Dimensions
MOBILE_APP_NAMEMOBILE_APP_RESOLVED_IDDATEOPERATING_SYSTEM_VERSION_NAMEAD_UNIT_IDCOUNTRY_NAMECOUNTRY_CODE
-
Timezone handling
- The request uses
time_difference: 8(UTC timezone offset as implemented by the API request payload).
- The request uses
-
Result format
- The connector requests
data_format: FILEV2and downloads the results as a gzipped CSV file, which is then streamed into your destination.
- The connector requests
-
Chunking
- The connector submits and polls reports in 7-day date chunks across the overall
[start_date, end_date]window derived from your cursor + backfill.
- The connector submits and polls reports in 7-day date chunks across the overall
Schema ERD
Explore the interactive entity relationship diagram for Appbroda.
Data Streams
performance_report
The primary stream containing Appbroda performance metrics broken down by the dimensions listed above.