Check the installs behind your in-app event campaigns
Fake users can trigger the registrations, purchases and level completions your campaigns optimize toward. Tapper stores your in-app events with their campaign and publisher and checks every install behind them against four fraud rules.
Advertisers and agencies using Tapper
In-app event optimization is targeted because it pays out more than basic CPI
As more UA campaigns optimize toward in-app events such as registrations, purchases and subscriptions, bad actors have adapted. A source that convinces your ad network it delivers your target event gets more budget, which accelerates the losses.
Fake events come from several routes: devices run in bulk, automation that scripts early in-app interactions and spoofed signals with no device at all. Whatever the route, your ROAS calculations include events that produced no revenue, and your budget moves toward the sources that look best on false data.
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 your in-app events on Mobile
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 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 and events
In-app events
Stored with campaign and publisher
Attribution inside the MMP
Install checks
Four fraud 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 your in-app events with their campaign and publisher and runs its fraud rules on each install and reinstall, the point where a user arrives.
Networks optimize delivery toward the events you set as conversion goals. If fake events count, the sources that send them look like top performers and get more budget. Seeing which campaigns and publishers send installs that fail Tapper's rules helps you question them.
Yes for the click to install time, location and network rules, which apply to installs on any platform your MMP reports. Click injection is mainly an Android issue.
No. Tapper only checks installs and leaves your MMP data, your attribution and your campaigns exactly as they are.
Other campaign types on Mobile app
See fraud in your Mobile in-app events
Get a demo and we will show you how Tapper checks the installs on your account.