Check in-app event campaigns for spoofed inventory
A spoofed placement can look like a premium app in your network's reports while its installs and events never turn into users. Tapper stores each install with its campaign and publisher and checks every install and reinstall against four fraud rules.
Advertisers and agencies using Tapper


































































Domain spoofing on mobile in-app inventory grows with programmatic buying
Domain spoofing in mobile advertising happens when a publisher misrepresents its in-app inventory in the programmatic bid stream, so a low-quality or non-human placement appears to be a premium app. Your network reports the ad as served on a reputable app, while it reached bots or never ran at all.
The result shows up in the installs that placement sends: the network looks efficient, but its installs do not behave like real users. Each install carries its campaign and publisher, and the rules check its timing, location and network.
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 domain 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.
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 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
No. Tapper does not verify bundle IDs or the bid stream. It stores the installs your MMP reports with their campaign and publisher and checks each install against its fraud rules.
It can. Clicks from spoofed placements that are attributed in your MMP make those sources look efficient. Seeing which sources send installs that fail the timing, location and network rules helps you question them.
Open exchange inventory and networks with light publisher vetting carry the most risk. Tapper checks installs from every source your MMP reports, so you can compare them.
See domain spoofing in your Mobile in-app events
Get a demo and we will show you how Tapper checks the installs on your account.

