Short answer: Google Ads counts Android reinstalls as install conversions and Firebase counts reinstalls as installs by default. Many MMPs only treat a reinstall as a new install after a re-attribution window. Older apps with many returning users show the biggest gap.
Why reinstalls are counted differently
Reinstall: an install of an app by a device or user that had installed and removed it before.
Google's developer documentation says Google Ads counts Android reinstalls by users who previously uninstalled as install conversions. Google's help centre says Firebase counts reinstalls as installs by default, while third parties often apply a re-attribution window.
How do I know reinstalls are the cause?
The gap grows with the size of your past user base and is larger on retargeting-style audiences. If the gap shrinks when you compare only new users, reinstalls are the cause.
Likely causes
- Google Ads counts reinstalls. On Android, reinstalls are install conversions.
- Firebase counts reinstalls. By default they are installs.
- MMP re-attribution window. A reinstall inside the window is not a new install in many MMPs. The exact default is vendor-specific.
- Install vs first open. Google Play conversions count downloads, so a reinstall that is never opened still counts in Google.
How to confirm it
- Check your MMP's reinstall and re-attribution settings.
- Compare Google or Firebase installs with MMP installs plus MMP reinstalls or re-attributions.
- Compare a brand-new app or market, where reinstalls are rare, with an established one.
- Check whether the Google conversion action is a Play install or your MMP's first_open.
How to fix it
- Compare like with like: add MMP reinstalls to MMP installs when comparing with Google or Firebase.
- Use your MMP's first_open conversion in Google Ads for bidding comparisons.
- Document your MMP's re-attribution window in your reporting notes.
- Report new installs and reinstalls as separate lines.
| Tool | Counts a reinstall as an install? |
|---|---|
| Google Ads (Android) | Yes |
| Firebase | Yes, by default |
| Typical MMP | After a re-attribution window (vendor-specific) |
| AdAttributionKit | Marks it as redownload |
Apple's AdAttributionKit labels postbacks as download, redownload or re-engagement, so reinstalls are visible there too. The Play Install Referrer also resets on reinstall, according to Android's documentation.
See Google Ads shows more installs than the MMP and GA4 or Firebase installs differ from the MMP for related gaps, and run the Google installs troubleshooter.