This post covers your ads showing inside other people's apps on the Google Display Network, not App campaigns that promote your own app. Google's page Show your ads in mobile apps makes the same split, and says Display campaigns "are designed to show your ads in apps by default" when your targeting matches. This post is part of our guide to Google Ads exclusion lists.
How we checked this. No ad-account test was run. We read the Google Ads Help pages linked in this post on 20 November 2026. That day we also ran five report queries through Google's Ads API query validator for version 26, which checks syntax and fields only, not account data. Both app placement queries passed, and the Performance Max placement view rejected clicks, cost and conversions.
What you probably want, and where Google handles it:
- Exclude one app you can name: enter its app ID in a Display campaign.
- Keep apps out of every campaign: add them to account-level placement exclusions.
- Keep app exclusions through the move to Demand Gen: move them to account level before migrating.
- Find which apps cost you money: the Where ads showed and Performance Max placement reports.
| Campaign type | What you can exclude | Where | Limit | Source |
|---|---|---|---|---|
| Display (until migrated) | Single apps by store ID, sites, videos; app category and device are listed controls | Campaign or ad group, or account level | 65,000 per account; 128,000 per ad group | Exclude specific webpages and videos; About your Google Ads account limits |
| Demand Gen, including migrated Display | Single apps and sites | Account level; Google says not generally at campaign or ad group level. Per ad group, you can leave out the Google Display Network channel | 65,000 per account | Demand Gen FAQ; Display Ads new home in Demand Gen; Channel controls in Demand Gen campaigns |
| Performance Max | Single apps and sites | Account level only, or a manager account list | 65,000 per account; 3 manager lists of up to 250,000 | Exclude placements at the account level |
| Search partners (side effect of account-level lists) | Whole sites | Account or manager level | Same account limits | Exclude placements at the account level |
| Every campaign at once | No single setting excludes all apps; add apps one by one | Account level under Content suitability; in our reading, excluding the mobile device also drops mobile web | Not applicable; the account list holds 65,000 | Exclude placements at the account level; Exclude specific webpages and videos |
Sources: the Google Ads Help pages linked in each section and About your Google Ads account limits, read 20 November 2026. Limits change, so check the page before you plan around them.
How to exclude mobile app placements in Display campaigns
Google Ads Display campaigns still give the most control: you can exclude single apps at campaign, ad group or account level.
Find the app ID for iOS and Android apps
Google's format has two prefixes, one per store:
- iOS apps. Take the iTunes ID at the end of the App Store URL and enter it after
mobileapp::1-. - Android apps. Take the package name after "id=" in the Play Store URL and enter it after
mobileapp::2-.
Google's example is the MechaHamster app: mobileapp::1-1286046770 and mobileapp::2-com.google.fpl.mechahamster.
Add the exclusion to a Display campaign
Google's steps on Exclude specific webpages and videos, condensed:
- Open the Campaigns menu and go to the Content exclusions page.
- Select Exclusions, then the drop-down arrow next to it, then Placements.
- Select the pencil icon, then Add placement exclusion.
- Under "Exclude from", choose Campaign and pick the campaign.
- Select Enter multiple placements.
- Paste one app per line in the
mobileapp::format and save.
To cover every campaign at once, use the account-level path instead. In our reading, it is the same account-level list Performance Max uses.
App category exclusions and device targeting
App category exclusions were not removed. Google still lists "App category" among the controls for mobile Display inventory, next to topics, device targeting and individual app exclusions, on both pages linked above. Neither Google page gives a step for excluding an app category, so check whether your account's exclusion editor offers app categories before you plan around them.
Google also warns about category exclusions in general: "we can't guarantee that you'll exclude 100 percent of related pages".
What Google did retire is the old app exclusion. It was replaced by device targeting with three options: computer, tablet and mobile. In our reading, excluding mobile removes mobile websites as well as apps, so it is the wrong tool if you only want apps out.
What no longer works, including adsenseformobileapps.com
Two methods still appear in older guides, and a third circulates without a Google source:
- adsenseformobileapps.com. Google says it "no longer supports targeting to app inventory using device settings and adsenseformobileapps.com placement". Google's page gives no date for the change. The domain "will continue to show up" in Automatic placement reports, which is why the old advice keeps coming back.
- The G-mob exclusion. The "G-mob mobile app non interstitial" exclusion "has been replaced by simplified device targeting".
- The all-apps code. Some practitioner guides describe a single ID that excludes every app category; no Google page documents it and reports differ on whether it applies at account level.
What happens to your app exclusions when Display moves into Demand Gen
Google is moving Display campaigns into Demand Gen, and migrated campaigns "can't be reverted". Campaign level content exclusions and some ad group exclusions do not carry over, so move the app exclusions you want to keep to account level before you migrate. Google's page Google Display Ads campaigns have a new home in Demand Gen sets out the details:
- The timeline. In June 2026 Google began "launching a phased rollout of our migration tool". Later, new Display campaigns "can only be created within Demand Gen", and remaining eligible campaigns move automatically. Google gives no date for either step.
- Exclusions that block the move. Google's error table lists "Some ad group exclusions are not supported" and "Campaign-specific content suitability exclusion not supported". Google's fix for both is to remove them before migrating, and campaign level exclusions "can be transitioned to account level".
- What carries over. The feature table lists placement and topic exclusions as supported and content suitability exclusions as "Supported only at account level". It does not mention app categories, so in our reading you should check any app category exclusions after the campaign moves.
- Google's advice. Google recommends "keeping GDN-only in channel controls" during migration.
What to do before your campaigns move:
- Export your campaign and ad group app exclusions.
- Add the ones you want everywhere to account-level placement exclusions.
- Remove the ad group and campaign level exclusions, as Google's migration page asks.
- Migrate the campaign.
- Once it serves, check the Where ads showed report for apps that came back.
An account-level list cannot keep apps in one campaign and out of another, so decide before migrating which campaigns lose that distinction.
How to exclude apps in Demand Gen campaigns
In Demand Gen, exclude apps at account level under Content suitability, because Google's Demand Gen FAQ says placement exclusions will not be generally available at campaign or ad group level. The Demand Gen Frequently Asked Questions (FAQ) uses the words "will not be generally available at the campaign or ad group levels" for topic and placement exclusions alike, and sends brand safety to the Content Suitability page. The migration page, by contrast, lists placement exclusions as supported.
Our reading: treat any campaign-level option you see in your account as an extra, not a plan.
The steps are the account-level path in the Performance Max section, with apps in the same mobileapp:: format.
Demand Gen has one finer control that does work per ad group. Per Channel controls in Demand Gen campaigns, "Channel controls are set at the ad group level", and the Google Display Network is an optional channel. Leave it out and that ad group stops serving on Display Network sites and apps. YouTube, Discover, Gmail and Maps remain.
How to exclude mobile apps from Performance Max
Performance Max has no campaign-level app exclusion: Google says "For Performance Max campaigns, placement exclusions are managed at the account level." That line is on Exclude placements at the account level, which gives the path:
- Select the Tools tab.
- Select the Content suitability tab, then Advanced settings.
- In "Excluded placements", enter the URL or search for the content, without the
www.prefix. - To paste a list, select Enter multiple placements.
- Save.
Apps go here too. Google's page About content suitability says the Excluded placements setting covers "specific videos, channels, websites, and apps".
The limits on Google's account-level page:
- Volume. Up to 20,000 exclusions at a time and 65,000 per account.
- Timing. "New placement exclusions typically take effect within 12 hours."
- Reach. The list applies across the account, including Display or Demand Gen campaigns that may want app inventory; Google notes that YouTube Sponsorship campaigns bypass it. Since March 2024, site exclusions at account or manager level also apply to the Search partner network.
Agencies can share one list across clients from a manager account. Google's page Use placement exclusion lists across your accounts says "A manager account can have a maximum of 3 exclusion lists." Each list holds up to 250,000 exclusions, per the account-level page. The manager account page adds: "Account level exclusion lists can't be added to specific campaigns."
If you need apps in one Performance Max campaign and out of another, Google offers no setting for it. Apps are only one part of Performance Max traffic quality; for the rest, see the full Performance Max traffic quality audit.
How to find app placements in the Google Ads placement report
To find app waste, use the Where ads showed report for Display and Demand Gen and the Performance Max placement report, which shows impressions only. No reliable public figure says how much budget apps take, so this post prints no waste percentage.
Display and Demand Gen: the Where ads showed report
Google's page About the "Where ads showed" report gives the path: Campaigns, then Insights and reports, then When and where ads showed, then the "Where ads showed" tab. It works at account, campaign or ad group level. For the Display Network, placements are "the websites, pages, or apps where your ads showed". Discover and Gmail placements can include apps too. Sort the app rows by cost, then compare them with conversions you trust.
Google's own caveats:
- Not complete. Do not use it as "an exhaustive list of placements", and do not treat it as an accurate record of billing.
- Not cleaned. Invalid traffic is removed from most reports, but it "may not be removed" from this one.
- Not significant. With many placements and few impressions each, performance data "is generally not statistically significant".
Our judgment: exclude an app on repeated evidence, such as cost with no conversions across a window you choose, not on one week of rows.
Performance Max: impressions only
Google's page Find or create placement reports for your Performance Max campaigns gives the path: Campaigns, then Insights and reports, then Report editor, then "Performance Max campaigns placement". Add the "Performance Max placement type" column, which is hidden by default, and filter to Mobile App. Google is plain about its purpose: "Placement reports should be used as a brand safety tool."
The Ads API shows the same limit, as the query section below shows. So for Performance Max you can see which apps served, not which apps cost you money. Pair the list with landing-page visits by app if your tracking records them, and check first whether the Display channel holds the spend with Performance Max channel reporting.
When an app click counts as invalid traffic
Some app clicks are Google's problem, not yours. Google's page Invalid clicks: Definition counts "Clicks that occur because of poor ad placement" as accidental, invalid clicks, and About invalid traffic names ads "placed too close to navigation buttons". When Google finds invalid traffic after billing, the Invalid clicks: Definition page says you get "a credit on your next invoice where appropriate and possible".
A real person who taps your ad on purpose and leaves without buying is a valid click, and that is where your exclusions do the work. For why app inventory carries more of this risk than Search, see how invalid traffic risk differs by campaign type.
Pull the app rows with a query
Both queries passed Google's validator for v26 on 20 November 2026. The validator checks syntax and fields only, not account data.
Display and Demand Gen app placements, with cost (detail_placement_view):
SELECT detail_placement_view.display_name, detail_placement_view.placement,
detail_placement_view.placement_type, detail_placement_view.target_url,
campaign.name, metrics.impressions, metrics.clicks, metrics.cost_micros,
metrics.conversions
FROM detail_placement_view
WHERE detail_placement_view.placement_type = 'MOBILE_APPLICATION'
AND segments.date DURING LAST_30_DAYS
ORDER BY metrics.cost_micros DESC
Performance Max app placements, impressions only (performance_max_placement_view):
SELECT performance_max_placement_view.display_name,
performance_max_placement_view.placement,
performance_max_placement_view.placement_type,
performance_max_placement_view.target_url, campaign.name, metrics.impressions
FROM performance_max_placement_view
WHERE performance_max_placement_view.placement_type = 'MOBILE_APPLICATION'
AND segments.date DURING LAST_30_DAYS
ORDER BY metrics.impressions DESC
A query on the Performance Max view that selects metrics.clicks fails validation. The validator said it "is not a valid field in the SELECT clause" for that view, and returned the same error for metrics.cost_micros and metrics.conversions. Google's Performance Max reporting page for the API covers the view.
What ClickFortify adds for the clicks that still reach your site
Exclusions stop apps you have already found; ClickFortify works on the clicks that still get through and load your page. It scores each visit that loads your landing page on 100+ device, network and behavior data points, and what it does next depends on the campaign type:
- Display. ClickFortify excludes the IPs and placements behind bad clicks in Google Ads. Sites and apps that keep sending bad clicks are added to your placement exclusions. See ClickFortify for Google Display.
- Demand Gen. The exclusion audience is opt-in. Turn it on and flagged visitors are uploaded in batches to a Google Ads exclusion audience. See ClickFortify for Demand Gen.
- Performance Max. Flagged IPs and ranges go into account-level exclusions, the level Google Ads applies to PMax. See ClickFortify for Performance Max.
Its limits:
- It cannot see what never loads. An in-app click that never loads your landing page is invisible to ClickFortify, as it is to any on-page script.
- It does not replace your list. It does not exclude app categories or replace the account-level exclusions you set from the placement report.
- It does not promise credits. Credits for invalid clicks are Google's decision.
The verdict on excluding mobile app placements
Exclude mobile app placements in Google Ads on evidence from your own placement report, one app at a time, at the level that matches your campaign mix. Put the exclusions you want everywhere at account level now. Performance Max accepts them at account level alone, Google steers Demand Gen there too, and Display is moving into Demand Gen, where Google says "Some ad group exclusions are not supported". Before a campaign moves, remove its ad group and campaign level exclusions, as Google's migration page asks. Do not exclude the mobile device to get rid of apps, because in our reading it takes mobile websites with them. Ignore the all-apps shortcuts and waste percentages that no Google page backs.
This approach is wrong for campaigns where app placements convert. There, a blanket account-level list costs you real buyers, and a per-ad-group channel choice in Demand Gen or a short list of named apps serves you better. No ad-account test was run for this post, so check each path in your own account before you rely on it. More in our Google Ads click fraud guide.




