Connect AppLovin to Rig

Sync your mobile user-acquisition campaigns, installs, spend and in-app events into the warehouse. Cost per install is the easy metric and the least useful one on its own, so the point of landing this next to your product data is measuring what those installed users go on to do.

Requirements: An AppLovin account that can reach Keys
Time required: 3 mins

Before you start

An AppLovin login that can open the Keys page.
Know that AppLovin shows you two different keys on that page, and only one of them is a reporting credential. See the callout below before you copy anything.

Get your reporting key

Log into AppLovin.
Click your account name in the top right.
Select Keys from the dropdown.
Copy the reporting key.

The reporting key, not the SDK key
Both sit on the same page and they are not interchangeable. The SDK key is what gets compiled into your mobile app so the AppLovin SDK can identify it at runtime. It authenticates an app, not an analyst, and it will not read a reporting API. The reporting key is the one Rig needs. Taking the wrong one is the single most common way this connection fails on the first try.

Connect it in Rig

In Rig, open Connections and go to Sources & actions.
Search for AppLovin and open the card.
Reporting key: paste the key you copied.
Click Test, then Sync.

What Rig pulls in

Campaigns and ad performance
Installs, spend and impressions, the inputs to cost per install
In-app events and revenue, which is what lets you measure past the install

Troubleshooting

Authentication fails: you have the SDK key. Go back to Keys under your account name and take the reporting key instead.
ROAS does not match your own numbers: AppLovin reports the in-app revenue it can attribute, which is not the same thing as revenue recorded in your billing or product systems. Comparing the two is a job for both sources sitting in the same warehouse, not a sync fault on either.