Short answer: The reliable way to track app installs across Meta, Google and other ad networks is a mobile measurement partner (MMP). You add one SDK to the app, connect each ad account to the MMP, map your install and in-app events, and test one install on a real device. The MMP then decides which campaign earned each install and sends the result back to every network. Linkrunner does this on a free tier of 25k attributed installs, with every feature included.
Meta Ads Manager says 1.2k installs this week. Google Ads says 900. The Play Console and App Store Connect together show 1.6k downloads, and your backend counted 1.4k new users. Every number is "right" by its own rules, and none of them tells you which campaign to scale.
This guide is for marketers setting up install tracking for the first time: why the networks disagree, what an MMP adds, and the steps to a tested first install.
Why do Meta and Google report different install numbers?
Meta and Google are self-attributing networks: each one matches installs against its own ads using its own rules, so both can claim the same install and neither sees the other's clicks.
Self-attributing network (SAN): an ad network that decides attribution itself instead of passing raw click data to a third party. Meta and Google are the two largest.
The gaps usually come from four places:
- Overlapping claims. A user sees a Meta video, later taps a Google ad, then installs. Both networks can count that install. Your total "paid installs" across ad managers can exceed the installs that actually happened.
- Different windows. Each network uses its own click and view windows. A view-through install that Meta counts may not appear anywhere else.
- iOS privacy. On iOS, both networks lean on Apple's SKAdNetwork, which reports aggregated, delayed results. Meta also documents Aggregated Event Measurement for people on iOS 14.5 and later.
- Modelled conversions. Google's own app conversion tracking page says App campaign reporting may combine observed and modelled conversions, and that complete reporting for iOS and Android app ads is only available inside Google Ads.
Each ad manager referees its own games only. Our guide to why SAN numbers differ goes deeper on the mechanics.
What we see in practice: when a team asks us why Linkrunner's numbers differ from Meta or Google, the cause is usually a definition gap (a 7-day click window against a 30-day or lifetime one, view-through counted on one side only), not a broken setup. In one Google comparison the gap shrank to around 2 per cent once both sides used the same 30-day window. Line up definitions before you go hunting for bugs.
What does an MMP do that the ad managers cannot?
A mobile measurement partner (MMP) is a neutral platform that collects install and event signals from your app, receives claims from every ad network, decides which campaign earned each install, and reports one de-duplicated number.
It does three jobs:
- Referee. One install, one winning campaign, across Meta, Google, TikTok, affiliates, influencers and QR codes.
- Reporter. One dashboard from click to install to sign-up to revenue, so you compare channels on the same rules.
- Messenger. It sends postbacks (install, sign-up and purchase events with revenue) back to each network, so Meta and Google optimise towards users who actually convert.
| Linkrunner (MMP) | Meta Ads Manager | Google Ads | |
|---|---|---|---|
| Counts installs from | Every connected network, plus owned links | Meta ads only | Google ads only |
| De-duplicates across networks | Yes, one winner per install | No | No |
| Separates organic installs | Yes | No | No |
| Sends events to other networks | Yes, via postbacks | No | No |
| Revenue and ROAS by campaign | All channels, one window you choose | Meta's own rules | Google's own rules |
If Google Ads is your only paid channel, GA4 and Firebase can carry you for a while. Our GA4 vs an MMP comparison covers exactly where that stops.
How to track app installs from Meta and Google, step by step
Button names in steps 2 and 3 are Linkrunner's, but every MMP follows the same shape.
Step 1: Add the attribution SDK to your app
- Pick the SDK for your stack: React Native, Flutter, iOS, Android, Expo, Unity and others. The quickstart walks through initialisation.
- Call the sign-up method when a user registers, and track the two or three events that matter most (first purchase, subscription, KYC complete).
- Ship it to 100 per cent of users. Partial rollouts produce partial attribution.
If you want to understand what the SDK actually collects, read how mobile attribution SDKs work. Most teams integrate it the same day and are fully live within a week.
Step 2: Connect Meta Ads
From Linkrunner's Meta Ads setup guide:
- In Meta for Developers, open your app's Settings > Basic. Copy the App ID and, in the Android section, the Install Referrer Decryption Key.
- In Linkrunner, paste both into the Meta App Integration tab.
- On the Ad Account Integration tab, log in with a Meta account that has full control of the business portfolio and connect the ad account.
- In Events Manager, generate a Conversions API access token for the app dataset, then paste it into Linkrunner under Configure CAPI.
- Map events.
MobileAppInstallandCompleteRegistrationare sent by default. Add your purchase event with Send Revenue on, then send a test event. Meta can take up to an hour to show it in Events Manager.
Why the decryption key matters on Android: Meta's Install Referrer covers view-through installs and click-through installs across sessions, which the Google Play referrer alone cannot. It needs the Facebook (v428+) or Instagram (v296+) app on the device. Without it, Meta installs often land as organic. Our Meta Install Referrer explainer covers this in full.
Step 3: Connect Google Ads
Google calls this linking a third-party app analytics provider. From Linkrunner's Google Ads setup guide:
- In Google Ads, go to Tools > Data Manager > Third-party app analytics and click Create link ID.
- Choose Other provider, enter Linkrunner's provider ID (listed in the docs), pick the platform and your app, and copy the link ID. Link IDs are per platform, so repeat for iOS and Android.
- In Linkrunner, open Integrations > Google Ads, add your Google account, then paste the link IDs under Setup Link IDs.
- Map events under App Event Mapping.
first_openandsign_upare included by default. Names must match exactly:Signupis notsign_up. - Back in Google Ads, import the discovered conversion action and set it as Primary if you want campaigns to bid on it.
Campaigns appear in Linkrunner after their first attributed install, not at launch. Start new App campaigns on install volume bidding, and switch to in-app action bidding once imported conversions have enough volume.
Step 4: Add your other networks and owned channels
- Ad networks: TikTok, Snapchat, LinkedIn, Reddit, Apple Ads, Jio Ads and ChatGPT Ads each connect in the same integrations area. If you run ChatGPT Ads, our ChatGPT Ads install tracking guide covers that network specifically.
- Everything without an ad manager: give influencers, affiliates, WhatsApp, SMS, QR codes and email one tracking link per source, so each shows up as its own row.
Step 5: Prepare for iOS
- SKAdNetwork. Meta and Google both measure iOS installs through SKAN, so complete the SKAN setup for each network before you launch iOS campaigns.
- Prerequisites first. In our support conversations, more than 10 iOS teams launched before the prerequisites were done: ad network IDs in Info.plist, postback copy endpoints, events copied into Meta. Check these off before spending.
- Google ICM. Set up Google Integrated Conversion Measurement so Google can attribute installs from users who decline the App Tracking Transparency prompt.
Step 6: Decide what to send back to each network
Send fewer, better events. A sensible starting set:
- Install (sent by default)
- Sign-up or registration
- One revenue event, such as first purchase, with revenue turned on
Sending every in-app event as a postback dilutes the signal the bidding algorithms learn from. The postback setup guide for Meta, Google and TikTok shows how to choose and map them.
Step 7: Test your first install
Linkrunner's integration testing guide gives two routes. The manual one:
- Uninstall the app from a test device.
- Create a campaign in the dashboard and open its link on the device. The click count should go up.
- Install your build and open it. The install count should go up.
- Register a user. The sign-up count should go up.
The click must happen before the first app open, or there is nothing to match. For a faster loop, register the device in SDK Console and follow its guided test link. For a full pre-launch protocol, see our mobile attribution QA checklist.
How do you read the install report?
Read the MMP report by channel first, then campaign, and compare it with each ad manager only after you have lined up the attribution windows.
- Attributed vs organic. Attributed installs have a winning campaign. Organic installs had no matching click or view in the window. A sudden jump in organic after a paid launch usually means a network is not connected properly, not a viral spike.
- Windows. Linkrunner's default click window is 7 days for most networks and 30 days for Meta and Google, and each channel can be set from 1 to 30 days in attribution windows. Match these to the ad manager before comparing.
- Expect some gap. The MMP total will usually be lower than the sum of every ad manager, because overlapping claims are de-duplicated. That is the point.
What does this cost?
- Free tier: 25k attributed installs, one time, no credit card, every feature included (Meta and Google integrations, postbacks, SKAN, fraud rules).
- After that: pay as you go, postpaid. The INR card runs from ₹1.20 per attributed install below 50k a month down to ₹0.80 above 500k. Organic installs Linkrunner does not attribute are not billed.
- Seats: unlimited on every plan.
Two published Linkrunner customer results show what one trusted install number makes possible: Matiks cut its Meta CPI by 46 per cent in three months while scaling installs, and Playo cut its Google Ads CPI by 34 per cent in three months.
FAQ
Can I track app installs without an MMP?
Yes, inside each ad manager, and with GA4 if Google Ads is your only paid channel. Once you run two or more networks, nothing referees overlapping claims, so you cannot trust a combined total or compare channels fairly.
Do I need the Meta SDK to track Meta installs?
Not for attribution through Linkrunner. The Linkrunner SDK plus the Meta connection (App ID, decryption key, ad account and Conversions API token) is enough for core install attribution and events.
Why do my Meta installs show as organic on Android?
Usually the Install Referrer Decryption Key is missing, or the SDK version predates Meta Install Referrer support. Add the key, update the SDK and test again.
How long until installs appear in the MMP?
A test install raises the dashboard's install count once the app is opened. Live campaigns show up after their first attributed install, and events sent to Meta can take up to an hour to show in Events Manager.
The takeaway
Ad managers tell you what each network thinks it did. An MMP tells you what happened across all of them and feeds it back so each network optimises on real users. Set up the SDK, connect Meta and Google, map three events, and test one install before you spend.
If you want to see this on your own campaigns, request a demo from Linkrunner, or work through our mobile attribution setup checklist with your developer this week.
