Google Ads conversion value settings determine how much the algorithm values each conversion event — and most advertisers running app install campaigns leave these settings at their defaults. For PWA install campaigns, this is a costly mistake. PWA installs behave differently from native app installs in ways that Google’s default conversion value logic doesn’t account for. Misconfigured conversion values mean Google’s algorithm optimizes for the wrong outcomes, overbidding on low-value installs and underbidding on high-value users. Here’s how to set up conversion values specifically for PWA campaigns, and why getting this right can cut your cost-per-quality-install by 20-35%.

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

Why Default Conversion Values Don’t Work for PWA Campaigns

When you set up a conversion action in Google Ads for a native app install, the system assigns a default value based on historical data from similar apps in your category. This default assumes a standard Google Play install funnel: the user clicks an ad, navigates to the Play Store, downloads the app, and opens it. Each step has a known drop-off rate, and Google calibrates the conversion value accordingly.

PWA installs skip most of these steps. The user clicks your ad, lands on your page, and adds the PWA to their home screen in seconds — no store navigation, no download wait, no permission dialogs. This compressed funnel means two things for conversion value:

1. Higher conversion rate, different user composition. PWA installs convert at 1.2x the rate of Play Store installs. But this higher rate includes users who wouldn’t have completed a Play Store install — users with older devices, limited storage, or short attention spans. Some of these users are valuable (they couldn’t install via Play Store but will engage heavily with your PWA). Others are low-quality (they installed impulsively and won’t return). Default conversion values treat all installs equally, missing this nuance.
2. Different post-install engagement pattern. PWA users interact with your app through the browser engine, which means session tracking, push notification behavior, and in-app purchase flows differ from native apps. If your conversion value is based on native app LTV data, it will systematically misvalue PWA installs — usually by undervaluing them, because PWA push notifications (which work even after “uninstall”) drive higher re-engagement rates than most advertisers expect.

Setting Up Conversion Values for PWA Install Campaigns

Step 1: Define Your PWA Conversion Events

Before touching conversion values, you need the right conversion events firing. For PWA campaigns, set up these events in Google Ads (via Google Tag Manager or gtag.js on your PWA landing page):

• PWA Page View: Fires when a user lands on your PWA install page. Value: $0 (tracking only, not a conversion).
• PWA Install Prompt Shown: Fires when the browser’s install prompt appears. Value: $0.50-1.00 (indicates high intent — the user stayed long enough to trigger the prompt).
• PWA Installed: Fires when the user completes the add-to-home-screen action. This is your primary conversion event. Value: set dynamically (see Step 2).
• PWA First Session: Fires when the installed PWA is opened for the first time. Value: $2-5 above the install value (confirms the user actually uses the app, not just installed and forgot).
• PWA Push Enabled: Fires when the user accepts push notification permissions. Value: $3-8 (push-enabled users have 3-4x higher Day-30 retention than non-push users).

This event hierarchy gives Google’s algorithm multiple conversion signals to optimize against, each with increasing value. Instead of optimizing purely for install volume, the algorithm learns to find users who install AND open AND enable push — a much more valuable cohort, as outlined in our complete PWA install campaign guide.

Step 2: Calculate Dynamic Conversion Values

Static conversion values ($5 per install, regardless of source) are a blunt instrument. For PWA campaigns, dynamic values based on user signals dramatically improve optimization quality. Here’s the framework:

Base install value: Start with your 90-day average revenue per PWA install. If your PWA generates $15 in revenue per user over 90 days, and your target ROAS is 3x, your base install value is $5.

Adjustment factors:

• Device type: High-end Android devices (Samsung S series, Pixel) show 40% higher PWA LTV than budget devices. Multiply base value by 1.4 for flagships, 0.7 for budget devices.
• Traffic source within Google Ads: Search traffic installs have 2x higher Day-30 retention than Display traffic installs. Use audience signals or campaign segmentation to pass different values.
• Geographic region: Tier-1 markets (US, UK, Germany) show 3-5x higher ARPU than Tier-3 markets. Adjust conversion values to reflect regional revenue differences.
• Push notification acceptance: Users who accept push notifications are worth 3-4x more than those who don’t. Fire a separate higher-value conversion event when push is enabled.

Step 3: Configure Bidding Strategy to Match

With conversion values properly set, choose the right bidding strategy:

Target ROAS (tROAS): Best for campaigns where you’ve accumulated 50+ conversions with value data. Set your target ROAS based on the dynamic conversion values you’ve configured. Start conservative (2x ROAS) and increase as the algorithm learns your PWA-specific conversion patterns.

Maximize Conversion Value: Best for new PWA campaigns with fewer than 50 conversions. This strategy lets Google find the highest-value installs without a ROAS constraint, giving the algorithm room to learn which user profiles generate the most downstream value.

Avoid Maximize Conversions (without value): This strategy optimizes for install volume only, ignoring your conversion values entirely. It will fill your funnel with cheap installs from Display inventory — high volume, low quality, exactly what you don’t want.

Common Mistakes and How to Avoid Them

Mistake 1: Using the same conversion values for PWA and Play Store campaigns. PWA users have different LTV curves, different push notification engagement, and different retention patterns. Copying Play Store conversion values to PWA campaigns guarantees misoptimization. Build PWA-specific values from PWA-specific data.

Mistake 2: Not tracking post-install events. If your only conversion event is “PWA Installed,” Google optimizes for install volume. Adding first-session and push-enabled events with increasing values teaches the algorithm to find high-quality users, not just users willing to tap “Add to Home Screen.” This approach mirrors the multi-event tracking we recommend in our cross-platform campaign optimization guide.

Mistake 3: Setting conversion values too high. If you tell Google that every PWA install is worth $20 but your actual ARPU is $8, the algorithm will overbid aggressively, winning auctions at any price. Set values based on actual revenue data, not aspirational targets.

Mistake 4: Ignoring the learning period. After changing conversion values, Google’s algorithm needs 2-3 weeks and 30-50 conversions to recalibrate. Don’t make additional changes during this period. Monitor performance but resist the urge to adjust values before the learning period completes.

Measuring Success: What to Track

After implementing PWA-specific conversion values, track these metrics weekly:

• Cost per quality install (CPQI): Total spend divided by installs where the user also completed first session AND enabled push. This should decrease 20-35% within 4-6 weeks as the algorithm learns to find higher-quality users.
• Conversion value accuracy: Compare your assigned conversion values to actual 90-day revenue per user. Adjust values quarterly to maintain accuracy as your ARPU changes.
• Channel mix shift: As Google learns which channels produce high-value PWA installs, it should shift budget away from low-intent Display toward higher-intent Search and Discover placements. Monitor this shift in your channel performance report, building on insights from our customer match campaign analysis.
• Push notification acceptance rate: This is your leading indicator of install quality. High-value users accept push at 2-3x the rate of low-value users. If your push acceptance rate is rising, your conversion value optimization is working.

The ROI of proper conversion value setup is measurable within the first month. Teams that switch from default values to PWA-specific dynamic values typically see a 15-20% reduction in cost per quality install within 3 weeks, as the algorithm shifts budget from volume-optimized Display placements toward intent-rich Search and Discover inventory. Over 90 days, the cumulative impact compounds: better conversion value signals lead to better audience targeting, which leads to higher-LTV installs, which generates more accurate conversion value data. This virtuous cycle is the primary reason why PWA campaigns with proper conversion value setup consistently outperform those running on defaults by 2-3x on a ROAS basis.

Action Checklist

• Set up PWA-specific conversion events (install, first session, push enabled) in Google Ads
• Calculate base conversion value from 90-day PWA revenue data
• Implement dynamic conversion value adjustments for device, region, and traffic source
• Choose the right bidding strategy (tROAS for mature campaigns, Maximize Value for new ones)
• Allow 2-3 weeks learning period after any conversion value change
• Track cost per quality install, not just cost per install
• Review and adjust conversion values quarterly based on actual ARPU data

Conversion value configuration isn’t a one-time task — it’s an ongoing calibration that directly controls how Google spends your budget. Teams that invest in PWA-specific conversion values consistently outperform those using default settings, because the algorithm has better signals to work with. The data doesn’t lie: when Google knows what a high-value PWA install actually looks like, it finds more of them.

---

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