Google Ads Conversion Value for PWA Install Campaigns 2026 | ROiBest

Google Ads conversion value settings determine how Google’s algorithm optimizes your campaigns. Set them wrong, and your budget flows toward low-value actions. Set them right, and every dollar works harder. For teams running PWA install campaigns — where the install happens on a web page rather than through Google Play — conversion value configuration is even more critical, because Google’s default settings assume a native app store flow that does not apply to PWA distribution.

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

Why Default Conversion Values Fail for PWA Install Campaigns

Google Ads was built around the app store install model. When you run a Universal App Campaign (UAC) or Performance Max (PMAX) targeting app installs, Google assumes the conversion event is a Google Play download. This assumption breaks in three specific ways for PWA campaigns:

• Install event mismatch: A PWA “install” is an Add to Home Screen action, not a Play Store download. Google’s default conversion tracking does not recognize this event without custom configuration, which means your campaign may be optimizing for page views rather than actual installs.
• Value attribution gap: If you do not assign explicit conversion values to PWA install events, Google treats all conversions equally. A user who adds your PWA to their home screen and a user who merely visits the landing page both look the same to the algorithm — destroying your optimization signal.
• Post-install events are invisible: Google’s app campaign tracking automatically captures in-app purchases and registrations from Play Store installs. For PWA installs, you must manually configure these post-install events as separate conversion actions with their own values.

The result: teams running PWA install campaigns with default Google Ads conversion settings typically see 20-40% higher cost per install compared to teams with properly configured conversion values, according to PWA distribution benchmarks.

Step-by-Step: Configure Conversion Values for PWA Installs

Here is how to set up Google Ads conversion tracking that accurately reflects the value of PWA install actions:

Step 1: Define Your PWA Conversion Funnel

Before touching Google Ads settings, map your PWA conversion funnel with explicit values at each stage:

1. Landing page visit — Value: $0 (do not count as conversion)
2. PWA install prompt shown — Value: $0.50 (engagement signal, but not a conversion)
3. PWA Add to Home Screen completed — Primary conversion. Assign your target CPI value (e.g., $2.00)
4. First app open after install — Secondary conversion. Value: $3.00 (indicates retention intent)
5. In-app purchase or registration — High-value conversion. Assign actual revenue value or target LTV proxy

Step 2: Set Up Custom Conversion Actions in Google Ads

1. Go to Google Ads → Goals → Conversions → New conversion action → Website.
2. Create separate conversion actions for each funnel stage above (install, first open, purchase).
3. For the PWA install event, set the conversion value to your target CPI and select “Use the same value for each conversion.”
4. For in-app purchases, select “Use different values for each conversion” and pass the actual transaction value through your tracking tag.
5. Set the counting method: “One” for installs (each user only installs once), “Every” for purchases.

Step 3: Implement GA4 Event Tracking on Your PWA Landing Page

1. Add a GA4 event tag that fires when the beforeinstallprompt event is triggered (install prompt shown).
2. Add a second GA4 event that fires when the user completes the Add to Home Screen action.
3. Link these GA4 events to your Google Ads conversion actions using the Google Ads-GA4 integration.
4. Verify the events are firing correctly in GA4 DebugView before activating campaigns.

Step 4: Optimize Bidding Strategy Based on Conversion Values

1. Select “Maximize conversion value” as your bidding strategy, not “Maximize conversions.” This tells Google to prioritize high-value actions (installs + purchases) over low-value ones (page views).
2. Set a target ROAS if you have enough conversion data (at least 15 conversions in the last 30 days).
3. If you are just starting, use “Maximize conversions” with manual CPI targets for the first 2-4 weeks, then switch to value-based bidding once you have enough data.

Common Mistakes That Waste PWA Campaign Budget

Based on analysis from teams who have optimized PWA install campaigns with Google Ads, these are the most frequent conversion value errors, as discussed in our ad measurement analysis:

• Counting page views as conversions: If your only conversion action is “page visit,” Google will optimize for cheap traffic, not install-ready users. Always use the PWA install event as your primary conversion.
• Equal values for all conversion actions: If install and purchase both have the same value ($1.00), Google has no reason to prefer purchase-likely users. Differentiate values by at least 3x between funnel stages.
• Not excluding returning users: PWA install is a one-time action. If you do not exclude users who already installed, you waste budget re-acquiring existing users. Use audience exclusion lists based on the install event.
• Ignoring the attribution window: PWA installs often happen within minutes of the ad click, not days. Set your conversion window to 1-day click for installs, and 7-day click for post-install purchases.

PWA vs. Google Play: Conversion Value Comparison

Teams running both native app and PWA campaigns can use conversion value data to compare channel performance directly. Here is what the data typically shows:

• Install conversion rate: PWA campaigns average 1.2x higher install rates than Google Play campaigns because the install is instant (no download wait time).
• Cost per install: Properly configured PWA campaigns deliver 15-30% lower CPI because Google can optimize toward a cleaner install signal without the noise of Play Store browsing behavior.
• Post-install revenue: PWA users show comparable or higher post-install engagement when push notifications are enabled, because PWA push works even after the user leaves the app — unlike native push which requires the app to remain installed.

These advantages compound when you factor in the absence of Google Play’s 30% revenue cut on PWA transactions, as covered in our platform risk analysis.

Action Checklist

1. Audit your current Google Ads conversion actions — remove page-view conversions and replace with PWA install events.
2. Assign differentiated values to each funnel stage (install, first open, purchase).
3. Implement GA4 event tracking for PWA install prompt and completion events.
4. Switch to “Maximize conversion value” bidding once you have 15+ conversions.
5. Set 1-day attribution window for installs, 7-day for post-install actions.
6. Exclude installed users from targeting to prevent budget waste.

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