Skip to main content

AppLovin

AppLovin is a mobile marketing platform whose MAX mediation and advertising products help app developers monetize and grow. This connector pulls MAX mediation revenue reports and advertising/UA campaign performance reports from AppLovin's Reporting APIs, letting you bring impressions, revenue, eCPM, fill rate, and campaign metrics into Nexla for analysis and reporting.

AppLovin icon

Power end-to-end data operations for your AppLovin API with Nexla. Our bi-directional AppLovin connector is purpose-built for AppLovin, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to AppLovin or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your AppLovin workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

AppLovin's Reporting APIs authenticate with a Report Key, which is passed as the api_key query parameter on every request. Before creating an AppLovin credential in Nexla, retrieve your Report Key from the AppLovin dashboard.

  1. Sign in to the AppLovin dashboard at https://ads.applovin.com with your account credentials.

  2. Navigate to your API keys page, found under Account > Keys (Report Key), or go directly to https://ads.applovin.com/account/api-keys.

  3. Copy the Report Key shown for your account. This single key authenticates both the MAX revenue reporting and advertising reporting endpoints.

  4. Store the Report Key securely — you will paste it into Nexla when creating the credential. Treat it as a secret, since it grants read access to your reporting data.

AppLovin's Reporting APIs enforce a rolling 45-day request window, so report start and end dates must fall within the last 45 days. Data from the most recent 1–2 hours may still be processing and can be incomplete.

For details on request parameters, available columns, and window limits, see the AppLovin Revenue Reporting API documentation.

Authenticate​

Credentials required​

FieldRequiredSecretDescription
Report KeyYesYesYour AppLovin Report Key, found in the dashboard under Account Settings > Report Key. Passed as the api_key query parameter on every API call.

Create a credential in Nexla​

  1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  3. Enter your AppLovin Report Key in the Report Key field. This is the key you obtained in Prerequisites, and it is sent as the api_key query parameter on every request to the AppLovin Reporting APIs.

  4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.

Use as a data source​

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the AppLovin connector tile, then select the credential that will be used to connect to AppLovin, and click Next; or, create a new AppLovin credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common AppLovin endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

MAX Revenue Report

Aggregated MAX mediation revenue/performance stats (impressions, revenue, eCPM, fill rate) by day, app, country, platform, network, within a rolling 45-day window.

  • Set the Start Date (report start date in YYYY-MM-DD format, inclusive). AppLovin retains reporting data for a rolling 45-day window, so this date must be within the last 45 days.
  • Set the End Date (report end date in YYYY-MM-DD format, inclusive).

This endpoint returns MAX mediation reporting rows from the results array. Because AppLovin enforces a 45-day request window, keep the requested date range within the last 45 days, and note that data from the most recent 1–2 hours may still be processing.

For available columns and parameter details, see the AppLovin Revenue Reporting API documentation.

Advertising (UA) Campaign Report

Advertiser-side UA campaign performance (impressions, clicks, conversions, cost, revenue) by day and campaign for apps promoted via AppLovin's ad platform.

  • Set the Start Date (report start date in YYYY-MM-DD format, inclusive).
  • Set the End Date (report end date in YYYY-MM-DD format, inclusive).

This endpoint returns advertiser (UA) campaign reporting rows from the results array. For available columns and parameter details, see the AppLovin Advertising Reporting API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration​

AppLovin data sources can also be manually configured to ingest data from any valid AppLovin Reporting API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new AppLovin data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.