Check in-app event campaigns for SDK spoofing
A spoofer can send in-app events together with the install, with no device and no user behind 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
SDK spoofing is hard to see from device signals alone
Bad actors reverse-engineer the SDKs that mobile measurement partners use and simulate the signals a real install would produce. No real device is involved and no real user downloads the app, yet your MMP receives what looks like a valid install, complete with device ID and location.
Because the device signals can be copied, they cannot settle the question alone. The click to install time, the country compared with the network the install came from and whether that network is a datacenter, VPN or proxy are checks on the install itself that do not depend on the signals a spoofer can copy.
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 SDK spoofing 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.
3
Rules on the install itself: timing, location and network
4
Fraud rules checked on every install and reinstall
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
Timing
Click to install time checked on every install
Depends on the MMP and its plan
Location and network
Compared with the MMP's country and checked for datacenter, VPN or proxy
Device signals inside the MMP
Your MMP data
Never changed by Tapper
Kept as the MMP reports it
Frequently asked questions
MMPs verify installs with the same SDK signals that bad actors copy, so accurate copies are hard to tell apart. Tapper adds its own checks beside your MMP: timing, location and network.
Every install and reinstall goes through four rules: install timing, click injection, a location that does not match the one the MMP reports, and datacenter, VPN or proxy networks. Each install is stored with its campaign and publisher.
Spoofing targets the signals an SDK sends, not one platform. Tapper sits alongside your MMP and stores the installs and in-app events it reports, without changing them.
See SDK spoofing in your Mobile in-app events
Get a demo and we will show you how Tapper checks the installs on your account.