Google just handed Performance Max advertisers something they’ve been asking for since PMax launched: meaningful control over how campaigns run. The 2026 PMax control expansion includes new asset group exclusions, placement-level reporting, brand exclusion lists, and campaign-level URL controls — changes that directly affect how you run PWA install campaigns through Google Ads.

If you’ve been running PWA install campaigns in PMax and wondering why your results have been inconsistent, the new control options give you the levers you’ve been missing. Here’s exactly how to use them.

→ Want to bypass Google Play entirely? See how ROiBest PWA works — no submission, no cut, 1.2x installs.

What Changed in Google PMax: The 2026 Control Expansion

Performance Max has operated as a black box since its launch — you provide assets, set a budget and target, and trust Google’s automation to allocate across Search, Display, YouTube, Discovery, Maps, and Gmail. The problem is that “trust the automation” works when all channels perform equally, and they rarely do for PWA install campaigns.

The 2026 updates to PMax include several control mechanisms that directly impact PWA install efficiency:

• Channel-level exclusions for Search partners: You can now exclude Search partner networks from PMax campaigns, preventing budget from flowing to lower-quality search inventory that performs poorly for app install intent queries
• Expanded brand exclusions: Brand exclusion lists now apply across all PMax inventory types, including Display and YouTube — preventing your app install budget from going to branded searches that would convert anyway (and making non-branded install campaigns cleaner)
• Asset group-level URL control: You can now set specific final URLs at the asset group level, meaning you can direct traffic to different PWA landing pages based on creative theme or audience segment without campaign duplication
• Enhanced placement reporting: Display and Video placements in PMax now show impression and conversion data at the placement URL level, letting you identify and exclude low-performing publishers
• Audience signal expansion controls: You can now specify “similar audiences only” within audience signals, reducing the automation’s tendency to drift toward broad audiences that inflate install volume but hurt post-install quality

Why These Controls Matter Specifically for PWA Install Campaigns

PWA install campaigns have unique requirements that make PMax’s default black-box behavior particularly problematic:

The PWA Landing Page Is the Install Environment

Unlike Google Play app installs (where the install happens in the store), PWA installs happen directly on your landing page. This means your landing page quality score, mobile load speed, and install prompt design directly affect your conversion rate — more than in any other campaign type. PMax’s automatic URL testing can override your optimized PWA landing page with variants that don’t include the install prompt, killing your conversion rate silently.

With the new asset group URL controls, you can lock your PMax campaign to your proven PWA install URL and prevent automatic URL experimentation from degrading performance.

PWA Install Intent Queries Are Narrow

Users who will successfully install a PWA tend to come from specific search intent categories: game or app name queries, “play [game] online” queries, and “no download” game queries. PMax’s Search expansion can route your budget to tangentially related queries with low install intent, wasting spend on impressions that will never generate installs.

Brand exclusions help here: by excluding your own brand terms, you ensure your PMax budget goes to new-user acquisition rather than re-engaging existing users who would have found you organically.

Display Placement Quality Is Critical for Mobile Install Context

For PWA installs, the display placement matters because the click leads directly to the install experience. Clicks from low-quality display placements (gaming sites, content farms) produce users who bounce before the install prompt loads. The new placement reporting lets you identify these placements and exclude them, improving install rate from remaining traffic.

Step-by-Step: Configuring PMax Controls for PWA Campaigns

Step 1: Set Up Brand Exclusions First

Before anything else, create a brand exclusion list that includes your app or game name, your company name, and common misspellings. Apply this to your PMax campaign. This prevents your non-branded install budget from going to users already searching for you — they’ll find you organically, and this budget is better spent on acquisition.

In Google Ads: Campaign → Settings → Brand exclusions → Create or apply exclusion list.

Step 2: Lock Asset Groups to Your PWA Install URL

For each asset group in your PMax campaign, set the final URL explicitly to your PWA landing page (the one with the install prompt). Disable “Final URL expansion” at the campaign level — this prevents Google from substituting other pages on your domain that don’t include the install prompt. If you have multiple PWA landing page variants (e.g., different games or app features), create separate asset groups with the corresponding locked URLs.

Step 3: Review and Exclude Low-Quality Placements Weekly

In your PMax campaign, navigate to Placements → Where ads showed → filter by Display/Video. Sort by Cost and identify placements with high spend but 0 conversions (installs) after 7 days. Add these to an exclusion list. Review weekly and expand the exclusion list as data accumulates.

For PWA install campaigns, typical exclusion candidates include: generic content sites, news aggregators, and entertainment portals where the audience has no app-install intent. Gaming-specific placements, tech-review sites, and comparison sites tend to perform better.

Step 4: Tighten Audience Signals with “Similar Only” Setting

If you have existing PWA install data (from previous campaigns or from your PWA platform’s analytics), use this as your audience signal and enable the “similar audiences only” expansion. This prevents PMax from expanding to users with no behavioral similarity to your existing installer base, keeping conversion rates higher on Display and YouTube inventory.

Step 5: Set Up Conversion Tracking for Post-Install Events

PMax optimizes toward the conversion events you define. If you’re only tracking installs, PMax will optimize for volume — which can produce low-quality installs. For BC gaming teams, set up in-app conversion events (first session, first purchase, day-3 return) as secondary conversions. For AI social apps, track first meaningful interaction (first AI conversation, profile completion). Signal quality to PMax about which installs become active users, and the algorithm will find more of them.

PWA Install Campaigns vs. Google Play UAC: The Control Advantage

One underappreciated advantage of PWA install campaigns over Google Play Universal App Campaigns is control over the post-click experience. In a UAC campaign driving to Google Play, Google controls the store page presentation. In a PWA install PMax campaign, you control the entire experience from click to install — landing page design, install prompt timing, pre-install value communication, and the install confirmation flow.

Teams using ROiBest for PWA deployment report that this end-to-end control over the install experience, combined with optimized PMax settings, consistently produces install conversion rates 1.2x higher than equivalent Google Play traffic — because the install prompt loads instantly without the friction of the app store flow.

The 2026 PMax controls make this advantage more accessible: by locking URLs to your PWA install page and excluding low-quality placements, you remove the scenarios where PMax’s automation would route traffic away from your optimized install experience.

Measuring PMax PWA Install Campaign Success: The Right Metrics

Don’t just track install volume. For PWA install campaigns through PMax, the metrics that predict long-term ROAS are:

• Install rate from landing page sessions: target > 35% (users who visit your PWA page should install at 35%+ if the page and prompt are optimized)
• Day-1 return rate: PWA installs that return to the app the next day — target > 40% for casual games, > 25% for AI apps
• Push notification opt-in rate: one of PWA’s key advantages over Google Play is post-uninstall push access; track opt-in rate as a proxy for high-quality installs
• Revenue per install (RPI): ultimately, what matters is revenue, not install count

Action Checklist: PMax Controls for PWA Install Campaigns

• ☐ Create brand exclusion list and apply to all PMax campaigns
• ☐ Set final URL per asset group to your PWA install landing page; disable Final URL expansion
• ☐ Review Display/Video placements weekly; exclude zero-install placements after 7 days
• ☐ Enable “similar audiences only” for audience signal expansion
• ☐ Add post-install conversion events (first session, day-3 return, first purchase)
• ☐ Check Search partner network settings and exclude if install intent is low
• ☐ Track install rate from landing page sessions; target > 35%

For more on Google Ads optimization for PWA campaigns, see our complete Google Ads PWA install campaign guide, our article on setting up conversion values for PWA lead gen to eCommerce, and our analysis of how the TikTok SEO shift impacts your Google Ads PWA strategy.

---

Skip the app store. Go live instantly, keep 100% of your revenue.

ROiBest helps Android app teams launch PWAs — no review process, no 30% Google Play cut, and push notifications that work even after uninstall. Teams see up to 1.2x higher install conversion rates vs native app downloads.

→ Get Started Free