AppLovin Integration

Beta

The AppLovin integration is still being verified with live advertiser accounts. If the numbers in adstage differ from the AppLovin dashboard, please let the adstage support team know.

In adstage, you can automatically collect spend, impressions, clicks, and installs per AppLovin (Axon) campaign and review them in reports. All you need is the Report Key issued in the AppLovin dashboard — there is no review process and no sign-in approval. The integration is performed in the Cost Integration tab under Integrations > Ad Channel Integration > AppLovin.

1. Integration Overview

2. Getting Your Report Key

The Report Key is an account-level key used to call the AppLovin Reporting API. The official documentation describes the following location.

1. Sign in to the AppLovin advertiser dashboard (ads.applovin.com; the former address ads.axon.ai leads to the same place) with the master account. You can also open it from the Open AppLovin key page button in adstage.

2. Click your account name at the top right and open Keys.

3. Copy the Report Key.

The same steps are shown in the How to get your AppLovin key box in the adstage dashboard.

Please note

The Keys screen also lists other keys, such as the Axon Event Key. Enter the Report Key in adstage; any other key is rejected during integration. If you cannot see the Keys menu, make sure you are signed in with an account that manages the AppLovin account, and ask your AppLovin representative if it is still missing.

3. Connecting Your Account

1. In Integrations > Ad Channel Integration, select AppLovin and open the Cost Integration tab.

2. Turn on the AppLovin Cost Integration switch. The Add Integration Account button stays disabled while the switch is off.

3. Click Add Integration Account to open the AppLovin Cost Integration dialog.

4. Enter an Account Label to identify this account in adstage, and paste the key into Report Key. The key is masked as you type, and leading or trailing spaces are removed automatically.

5. Click Integrate. Before saving, adstage calls the Reporting API once for the previous day to verify the key (the button shows Verifying...). Once verified, the key is stored encrypted and the first collection of the last 30 days starts immediately.

Right after connecting, the account status shows Preparing, and changes to Success when the first collection finishes. This usually takes a few minutes.

4. Managing Connected Accounts

Connected accounts are listed in the Cost Integration tab with Account Name, Status, Last Data Update, and Management (delete) columns.

• Status is Preparing (first collection in progress), Success (last collection was fine), or Failed (for example, AppLovin rejected the key). Hover over Failed to see the error. Failed accounts are retried on every update and return to Success automatically once the cause is resolved.
• Even with a Success status, no data arrives if no ads are running. If no cost data is stored for more than 3 days, a warning appears next to the status with the message "No cost data has been collected for N days."
• To change the Report Key, delete the account with the trash icon in the Management column and add it again with the new key. A stored key cannot be edited in place.
• Turning the AppLovin Cost Integration switch off stops collection for every AppLovin account in this organization. The accounts remain, so collection resumes when you turn it back on.

Please note

Deleting an account stops collection for it. Data already collected stays in adstage, but no new data is added.

5. Collected Data

In reports, metrics reported by the ad platform are suffixed with (Channel).

Good to know

• Campaigns are keyed by AppLovin's external campaign ID (campaign_id_external). It does not change when a campaign is renamed, and it is the same value as the {CAMPAIGN_ID} click macro.
• When the same day and campaign arrive as several rows (for example Android and iOS), they are summed. A per-platform breakdown is not provided.
• Days where spend, impressions, clicks, and installs are all zero are not stored.
• The AppLovin Reporting API only covers the last 45 days, so data older than 45 days at the time of integration cannot be retrieved.

6. Tracking Links and Conversion Sending

AppLovin's documentation states that campaigns must be tracked through one of its designated measurement partners (Adjust, AppsFlyer, Kochava, Tenjin, Singular, Branch). adstage therefore does not provide an AppLovin tracking link template, and AppLovin does not appear in the ad channel list under Deep Links > Create.

The macros AppLovin fills in on click ({CAMPAIGN_ID}, {CAMPAIGN_NAME}, {IDFA}, {EVENT_ID} and others) are published. Ask your AppLovin representative whether a link from a measurement tool outside that list can be used in a campaign. adstage has also asked AppLovin to confirm this and will update this page once we hear back.

If your representative allows it, clicks and conversions arriving through a custom link whose channel name is applovin or axon are reported under the same applovin.ads channel as the cost data.

Conversion sending is not offered. AppLovin does not publish a postback specification for measurement tools, so there is no AppLovin preset in network postback either. Cost collection works without tracking links or conversion sending, so we recommend leaving your existing MMP setup in place for AppLovin install and conversion measurement and using adstage alongside it for cost.

7. Cautions

Please note the following.

• Numbers may differ between AppLovin and adstage. AppLovin reports in UTC, and aggregation timing and currency conversion also differ.
• If the Report Key is regenerated or deleted in AppLovin, collection with the old key stops and the status turns Failed. Delete the account and register it again with the new key.
• A Report Key belongs to one AppLovin account. If you have several AppLovin accounts, issue a key for each one and register them separately.
• If your AppLovin account is billed in a currency other than USD, please let the adstage support team know.
• adstage only reads AppLovin reports; it never changes campaign settings.

8. Troubleshooting

The account cannot be added

1. Check the key type: make sure you copied the Report Key from the Keys screen, not the Axon Event Key or another key
2. Check for a truncated copy: make sure the key was not cut off (leading and trailing spaces are removed automatically)
3. Check the switch: the AppLovin Cost Integration switch must be on for Add Integration Account to be enabled
4. Temporary outage: if you see "Could not reach AppLovin", try again a little later

The status is Failed

1. Check the error: hover over the status to see the error
2. Authentication failure: "Authentication failed — reconnect or check the key" means the key was revoked or regenerated; delete the account and register the new key
3. Rate limit or temporary error: these retry automatically, so wait for the next update

No data is collected

1. Check that the integration is on: confirm the AppLovin Cost Integration switch is enabled
2. Check that ads ran: days where spend, impressions, clicks, and installs are all zero are not stored, so confirm that campaigns actually ran in AppLovin
3. Check the update cycle: the first collection starts right after connecting, then repeats every 4 hours. The current day is never collected, so today's numbers appear tomorrow
4. Check the window: data older than 45 days at the time of integration cannot be retrieved

The numbers differ from the AppLovin dashboard

1. Timezone: set the AppLovin dashboard to UTC and compare the same dates
2. Currency: adstage values are converted into your organization's base currency
3. Aggregation timing: AppLovin values can change retroactively and are picked up when the last 30 days are re-fetched
4. Granularity: adstage stores campaign totals only, so do not compare them directly with AppLovin views split by platform or country

Contact the adstage support team if you need further help.

9. FAQ

Is there an AppLovin sign-in (OAuth) integration?

No. The AppLovin Reporting API is called with the Report Key alone, so there is no sign-in or permission approval step.

Why does Conversions (Channel) differ from installs in adstage?

Conversions (Channel) are installs counted by AppLovin, while adstage installs are measured by the adstage SDK and tracking links. While an adstage tracking link cannot be used with AppLovin, installs from AppLovin are not attributed to the applovin.ads channel in adstage, so the two numbers will differ.

Can more historical data be collected at integration time?

The last 30 days are fetched right after connecting. The AppLovin Reporting API only covers the last 45 days, so anything older cannot be retrieved.

10. Reference Documents

• AppLovin Reporting API — Report Key location, 45-day window, UTC basis, column definitions
• Set up MMP tracking — AppLovin's list of designated measurement partners
• Tracking URL macros — AppLovin click macros
• AppLovin advertiser dashboard