What is a Mobile Measurement Partner (MMP)?

A Mobile Measurement Partner (MMP) is a third-party platform for mobile-app attribution: it matches ad clicks and impressions to installs and in-app events and produces one report across networks. The short query mmp is noisy (in Russian search it often means the MMPI personality test). In marketing the letters only mean Mobile Measurement Partner.

An MMP is a category, not a brand. AppsFlyer, Adjust, Branch, Singular, and Kochava are examples of the same product class; they do not need separate glossary pages. The advertiser ships one SDK, connects ad networks, and reads installs, events, and cost in one model instead of ten dashboards with different windows.

Why an MMP exists

App stores and ad networks each count installs in their own favor. The MMP is the referee: the network click is logged on a tracking URL, the install and events arrive from the in-app SDK, then an attribution rule runs — usually last-click across every connected source. The result is posted back to Meta, Google, TikTok, and in-app networks for optimization, not only for reporting.

For user acquisition this is the measurement layer for CPI and post-install KPIs: registration, D1, purchase, deposit. Optimizing raw installs with no events attracts incent and junk traffic. An arbitrage tracker attributes click → conversion on the web and in the affiliate network; an MMP attributes install → event inside the app. On app offers they are often reconciled, not substituted for each other.

How an install is attributed

Typical flow: the user clicks an ad → the network or MMP stores the engagement (click ID, timestamp, campaign) → after install the SDK reports a device ID and first-open → the MMP looks for a match inside the attribution window.

  • Deterministic — IDFA matched (if the user allowed tracking under ATT), GAID on Android, or a store click ID / referrer. Hardest match.
  • Aggregated — on iOS without IDFA the main paid path is SKAdNetwork: Apple sends a delayed postback with campaign ID and conversion value, without a user-level click in the classic CPA sense.
  • Probabilistic (fingerprint: IP + UA + time) — once filled gaps between click and install; after ATT and Android restrictions its role shrank, and some networks no longer accept it as the only signal.

Impressions can receive view-through credit with a short window, separate from click-through. User-level multi-touch is uncommon in mobile UA: networks and MMPs default to one source per install so the same install is not paid twice.

IDFA, GAID, and privacy

IDFA (iOS) and GAID (Android) are advertising device IDs. After ATT the app does not get IDFA without opt-in; allow rates vary by vertical. Paid iOS attribution mostly lives in SKAN and in Apple Ads (AdServices) signals that MMPs also ingest. Android IDs remain more available, but regulation and Privacy Sandbox shrink fingerprinting. The MMP is the normalization layer: one SDK, different privacy regimes, one report.

Web pixel tracking is not an MMP. Web-to-app (browser click → install) is a separate setup: deferred deep links and, where supported, SKAN web-to-app. That is not a landing-page pixel.

Fraud and reconciliation

Common schemes: click injection (a click inserted before an organic install), click spam, SDK spoofing, device farms. MMPs cut some of this with filters and holds; buyers still reconcile the network dashboard, the MMP, and a tracker if one exists. Window and model mismatches are normal, not automatically “lost” installs. For affiliate payouts on an app offer, the advertiser postback remains the source of truth — not the MMP chart.

Category examples

AppsFlyer and Adjust cover most UA demand (network integrations, antifraud, SKAN schemas). Branch is often chosen when deep links and web-to-app are the product core. Singular and Kochava provide the same attribution job with a different emphasis (creative analytics or enterprise contracts). Picking one MMP is sticky: swapping SDK and rewiring networks costs more than swapping a web tracker. The brand on the invoice does not change the category definition.

See also: tracker, attribution window, deep link, CPI, SKAdNetwork, iOS ATT.