Phones produce more stray taps, more app inventory and shorter visits. Learn to judge mobile traffic on its own terms, review in-app placements and spot patterns worth investigating.
Mobile ad traffic is the paid clicks and visits that come from phones and tablets, both in mobile browsers and inside apps. It behaves differently from desktop traffic because touchscreens, app inventory and on-the-go intent change how people click and what they do next, so it needs its own baseline and its own review rather than a straight comparison with desktop.
This guide explains why mobile traffic differs, what Google says about accidental mobile ad clicks, how to review and exclude in-app placements in current Google Ads, how device segmentation and bid adjustments work, which mobile-specific fraud concepts are worth understanding, and how to compare mobile and desktop quality fairly.
Several features of mobile use shape the numbers before any question of quality arises:
None of these is a quality problem in itself. Together, they mean mobile metrics have to be judged against mobile baselines.
Google treats accidental clicks as invalid. Its help center lists clicks that occur because of poor ad placement among its examples of invalid clicks, alongside automated and manual abuse, and states that advertisers won’t be charged for invalid clicks. An accidental tap is one of several kinds of ad interaction, alongside genuine, deliberately manual and automated clicks, which our guide to what an ads clicker is sets out.
Google has also described specific measures aimed at mobile. In a 2015 post on its advertising blog, it said that:
Treat that post as an indication of Google’s approach rather than a description of today’s exact rules, which Google does not publish in detail.
On the publisher side, Google’s AdMob guidance explains where many accidental clicks begin: close proximity of banner ads to other elements within an app is described as one of the biggest causes of accidental clicks, and banners should not float or hover over app content. App publishers who ignore that guidance put their own accounts at risk.
For advertisers, the practical upshot is that some accidental taps are prevented or filtered, but not necessarily all. Those that remain tend to appear as very short, unengaged visits from app placements. Our explainer on how Google filters, reports and credits invalid clicks covers the reporting side.
Google says Display Network campaigns are designed to show your ads in apps by default when the placement matches your targeting. Unless you have narrowed your placements, part of your mobile Display traffic is in-app, and in-app ad traffic quality can differ sharply from mobile web.
The “Where ads showed” report, reached through Insights and reports and then When and where ads showed, lists the placements where your ads appeared, including mobile apps. Google cautions that the report is not regularly updated, that it may include invalid traffic, and that over-optimizing on it can limit the inventory available to your campaigns. Use it to find apps with consistently poor engagement or lead quality across a meaningful number of clicks, not to react to a handful of bad visits.
Individual apps can be excluded as placements at campaign, ad group or account level, alongside website URLs and video IDs. Account-level placement exclusions now also apply to the Search partner network, including Performance Max campaigns. Google’s page on showing ads in apps also lists app categories among the available placement controls.
Older shortcuts no longer work. Google says Google Ads no longer supports targeting app inventory through device settings and the adsenseformobileapps.com placement, and that the former “G-mob mobile app non interstitial” content exclusion has been replaced by simplified device targeting options of computer, tablet and mobile. That page does not describe a single setting that removes all app inventory while keeping mobile web, so check your current campaign settings rather than relying on guides written for older versions of the interface. Placement exclusions are one of several controls covered in our guide to practical invalid click protection.
Separate devices in every report you rely on. Google Ads can segment results by device, and comparing mobile with its own history is far more informative than comparing it with desktop.
If mobile performance is consistently different, bid adjustments let you act on it. Google’s page on bid adjustments sets device adjustments between -100% and +900%, and a -100% adjustment opts the campaign out of that device. With Smart Bidding, manual adjustments generally aren’t applied, several automated strategies accept only a -100% device adjustment, and Target CPA uses device adjustments to change the CPA target rather than the bids.
Excluding mobile entirely is a blunt instrument. It removes accidental and invalid clicks along with real customers who simply behave differently on a phone. A narrower fix, such as excluding a few poor app placements, usually costs less. If you suspect your mobile spend is structurally inefficient rather than invalid, our guide to finding avoidable Google Ads spend is the better starting point.
A few forms of abuse are particular to mobile, especially app advertising. They are described here only at the level needed to recognize them in data.
In data, these tend to show up as patterns rather than single events: installs credited to clicks that land implausibly close to the install, app placements with unusually high click-through rates and almost no engagement, or a sudden surge of “mobile” traffic whose technology values look nothing like your real audience. For the wider map, see our overview of automated ad traffic, benign and malicious, and for software built specifically to click ads, our explainer on ads clicker bots and why they are prohibited.
Mobile and desktop rarely perform identically, and a raw comparison usually says more about mix than about quality. To compare fairly:
As an illustration, imagine a hypothetical campaign over one month:
| Segment | Clicks | Conversions | Conversion rate |
|---|---|---|---|
| Desktop | 1,000 | 50 | 5.0% |
| Mobile web | 2,000 | 80 | 4.0% |
| In-app | 1,000 | 5 | 0.5% |
| All mobile (blended) | 3,000 | 85 | 2.8% |
Read as “mobile versus desktop”, the campaign seems to have a serious mobile problem. Split by placement type, mobile web performs close to desktop and the gap comes almost entirely from in-app placements. The sensible response is to review those app placements, not to cut mobile bids across the board. Our guide to segment-by-segment ad traffic analysis turns this kind of comparison into a regular routine.
Keep reading
Measurement
Traffic quality is not the same as conversion rate. Here is a segment-by-segment routine for reviewing paid traffic every week, with a simple scorecard and a worked example.
Click fraud
No setting makes a campaign immune to bad clicks. See how Google's filtering, your own campaign controls and outside tools fit together, and where each one stops working.
Google Ads
Most wasted spend in Google Ads comes from settings, search terms and tracking rather than fraud. Here is how to find it, check it and decide what to fix first.
