AppLovin

Forward resolved purchase events to AppLovin, so app-install and re-engagement campaigns optimise against revenue rather than installs.

DestinationAd platforms

Request a demo Start free trial

About AppLovin

What AppLovin is, and why identity matters to it.

AppLovin reaches people inside mobile apps and games, a surface where the browser conventions most tracking depends on barely apply.

In-app traffic hands off to a web checkout, and identity almost always breaks at that boundary.

How it works

How AppLovin works.

AppLovin optimises against events reported through its SDK and API, and is very good at driving installs and in-app actions. A purchase that happens later in a mobile browser or on a desktop sits on the other side of a handoff it cannot see.

With Upstack Data

Get more out of AppLovin with Upstack Data.

Upstack resolves the purchase against the device graph before forwarding it, so an in-app tap and a web checkout — same device or not — resolve to a single customer. AppLovin then optimises toward revenue rather than toward installs, the two things easiest to confuse on this channel.

What you can do with it

Three jobs this connector does inside AppLovin.

Send complete conversions
Conversions reach AppLovin through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival — and the conversions you never saw stop being invisible.
Optimise on the customer you want
Map any order attribute to the conversion AppLovin receives — profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout — so the platform learns from the buyers worth acquiring.
Optimised on revenue, not installs
Purchases are forwarded with their full value attached, so bidding trains on customers who spend rather than on people who install.