On a website, the page can read the tags in the link and keep them. An app store passes almost nothing to the app about the ad that sent the person there. So apps need their own measurement tool.
What an MMP does
- Matches installs to ads. It connects an install to the click or view that came before it.
- Records events in the app: registration, purchase, subscription.
- Reports back to ad networks, so that their optimisation sees the same installs and events.
- Gives one count. Each ad network claims its own installs, so their totals overlap. An MMP is a third party that applies one rule to all of them.
Well-known examples are AppsFlyer, Adjust, Singular and Branch.
How it differs from web attribution
| Web attribution | MMP | |
|---|---|---|
| Where it starts | A visit with tags in the link | An install from a store |
| What joins the steps | First-party cookie and a visit ID | Store and platform data, a device ID when allowed |
| Main limit | Consent and browsers | Apple’s privacy rules on iOS |
On iOS, matching a person to an ad needs their permission. Without it, Apple reports installs through SKAdNetwork and AdAttributionKit, later and in less detail. So iOS numbers are often rougher than Android ones.
When you need one
You need an MMP if paid installs are a real part of your budget and people install straight from a store. If the app is an add-on and users first come through your website, web attribution can carry most of the load.
Where KO fits
KO is not an MMP. It does not match installs to ad clicks by device. If most of your users install straight from a store, use a mobile attribution tool for that part.
KO can follow money when the user comes through your website first. The site sends the KO visit ID, the app writes it into a customer attribute in RevenueCat, and purchases and renewals are linked to the campaign. This connection is available on request.