Check in-app event campaigns for fake installs
Every in-app event starts with an install. A fake install can carry fake events with it and steer your optimization toward the source that sent them. Tapper stores each install with its campaign and publisher and checks every install and reinstall against four fraud rules.
Advertisers and agencies using Tapper
Fake installs are the most direct form of mobile UA budget theft
Every fake install triggers a CPI payout, which drains budget that should be acquiring real users. On a campaign with no check of its own, you pay for installs from users who never engage with the app and contribute nothing to revenue.
Fake installs enter attribution data by several routes: simulated installs, devices run in bulk and clicks injected just before a real install. Each leaves different traces, such as an impossible click to install time, a location that does not match or a datacenter network. Your LTV projections, built on cohorts that include fake users, overestimate engagement and revenue.
Tapper keeps the in-app events your MMP reports tied to the campaign and publisher that brought each user, and checks the install behind them. The four rules look at the time from click to install, click injection, a location that does not match, and datacenter, VPN or proxy networks.
How Tapper checks fake installs on Mobile in-app events
Three steps from connecting your MMP to seeing your installs in your dashboard.
01
Tapper works with the major mobile measurement partners and stores the installs and in-app events your MMP reports, each with its campaign and publisher.
02
Each install and reinstall is run through four rules: install timing, click injection, a location that does not match the one the MMP reports, and datacenter, VPN or proxy networks.
03
The Mobile tab of your Tapper dashboard shows your installs and in-app events by campaign and network. Your MMP data and your campaigns stay as they are.
What Tapper checks on every mobile install
How the mobile fraud rules work, in numbers.
4
Fraud rules checked on every install and reinstall
2
Install events checked: new installs and reinstalls
0
Changes to your MMP data, attribution or campaigns
Tapper vs your MMP alone
Role
A separate check beside your MMP
Tracks and credits installs
Install source
Installs and in-app events stored with campaign and publisher
Attribution inside the MMP
Fraud rules
Four rules on every install and reinstall
Depends on the MMP and its plan
Your MMP data
Never changed by Tapper
Kept as the MMP reports it
Frequently asked questions
Tapper stores each install with its campaign and publisher and runs the four rules on every install and reinstall.
Click injection is when a malicious app on the device sees an install begin and fires a click just before it completes, so the injected source claims credit for an install it did not drive. Tapper's click injection rule checks whether the attributed click arrived after the install began or right at its start.
No. Tapper only checks installs and leaves your MMP data, your install counts and your campaigns exactly as they are.
See fake installs in your Mobile in-app events
Get a demo and we will show you how Tapper checks the installs on your account.