If you are running PWA install campaigns in Google Ads and relying on default conversion values, your Smart Bidding strategy is almost certainly leaving money on the table. In 2026, as Google continues to shift toward value-based bidding across Search, Display, and Performance Max, the accuracy of your conversion value setup directly determines whether the algorithm chases high-value installs or wastes budget on low-quality ones. According to Google’s own case studies, advertisers who implement dynamic conversion values see an average 14% improvement in return on ad spend compared to those using flat, static values. For PWA install campaigns specifically — where there is no app store intermediary providing revenue signals — getting conversion values right is not optional. It is the single most impactful lever you have for campaign performance.

This guide walks you through exactly how to set up conversion values for PWA install campaigns in Google Ads, from lead generation models to ecommerce flows. No code, no manifest files — just the campaign-side configuration that makes Smart Bidding work for you instead of against you.

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

Why Conversion Value Matters for PWA Install Campaigns

Google Ads Smart Bidding strategies like Target ROAS and Maximize Conversion Value rely on one critical input: the value you assign to each conversion action. When you run a native app install campaign through Google Play, the platform automatically feeds purchase data back to Google Ads. PWA installs do not have this luxury. There is no app store sitting between your ad and the user, which means you are responsible for telling Google what each install is worth.

This distinction matters enormously. Google’s bidding algorithm uses conversion value data to decide which auctions to enter, how aggressively to bid, and which user segments to prioritize. A 2025 analysis from Search Engine Land found that campaigns using value-based bidding outperformed those using target CPA by 22% in conversion volume when value signals were properly configured. But when value signals are inaccurate or missing, the algorithm optimizes blindly — treating a user who installs and never returns the same as one who makes a $200 purchase within the first week.

For PWA install campaigns, the stakes are even higher. Because PWA installs happen directly from the browser — often through a simple “Add to Home Screen” prompt — the install friction is lower than native apps. This means you get more installs per click, but the quality variance is wider. Without proper conversion values, Smart Bidding cannot distinguish between a casual browser tap and a genuinely engaged user. For a deeper look at the full campaign setup process, see our Google Ads PWA install campaign guide.

There are three core reasons conversion values are non-negotiable for PWA campaigns in 2026:

• Algorithm training data: Google Ads needs at least 30–50 conversions with value data in a 30-day window to optimize effectively. Without values, it cannot learn which user profiles drive revenue.
• Budget allocation across campaigns: If you run multiple PWA campaigns (different geos, different creatives, different landing pages), conversion values allow Google to shift budget toward the campaigns producing the highest return — not just the most installs.
• Competitive bidding: In auctions where native app advertisers are sending rich value signals from Google Play, your PWA campaign is at a disadvantage if it only reports binary install/no-install data. Value signals level the playing field.

Common Mistakes in Conversion Value Setup

After auditing dozens of PWA install campaigns across lead gen, ecommerce, and subscription models, we see the same mistakes repeatedly. These are not minor oversights — each one directly degrades Smart Bidding performance.

Mistake 1: Using a Single Static Value for All Installs

The most common error is assigning one flat value — say, $5.00 — to every PWA install conversion. This tells Google that every install is equally valuable, which is never true. A user who installs your PWA and completes onboarding is worth far more than one who installs and bounces within 10 seconds. Google’s internal data suggests that advertisers using dynamic values see 18–25% better ROAS than those using static values, yet roughly 60% of PWA campaigns we audit still use a single fixed number.

Mistake 2: Counting Installs Without Post-Install Signals

Many teams track the PWA install event as their only conversion action. While this captures top-of-funnel activity, it gives Smart Bidding no information about what happens after the install. For ecommerce PWAs, you need to pass back actual purchase values. For lead gen PWAs, you need to assign estimated values based on lead quality tiers. The install itself should either be a secondary conversion action or carry a value that reflects average downstream revenue.

Mistake 3: Misaligning Conversion Windows with PWA User Behavior

Google Ads default conversion windows are designed for traditional web conversions. PWA install-to-value cycles often differ significantly. For example, a subscription PWA might see 70% of its conversions happen within 3 days of install, while an ecommerce PWA might have a 14-day consideration cycle. Setting the wrong conversion window means Google either over-counts (attributing unrelated purchases to the campaign) or under-counts (missing legitimate conversions that happen after the window closes).

Mistake 4: Not Differentiating Between Conversion Actions

In Google Ads, you can set conversion actions as “primary” (used for bidding optimization) or “secondary” (tracked for reporting only). A frequent mistake is marking both the PWA install and the post-install purchase as primary actions. This double-counts value and inflates your reported ROAS, which in turn causes Smart Bidding to over-bid on low-quality traffic because it thinks performance is better than it actually is.

Mistake 5: Ignoring Enhanced Conversions for Server-Side Accuracy

With browser-side tracking increasingly limited by cookie restrictions and ITP, relying solely on the Google tag for conversion value reporting leads to data gaps. Enhanced Conversions let you send hashed first-party data server-side, improving match rates by up to 15% according to Google. For PWA campaigns, where the install happens in-browser and subsequent engagement may happen across sessions, Enhanced Conversions are critical for maintaining value accuracy. Learn more in our guide to Google Enhanced Conversions for PWA tracking.

Step-by-Step: Setting Up Conversion Values for PWA Installs

Here is the exact process for configuring conversion values in Google Ads for your PWA install campaigns. These steps cover the Google Ads interface and strategy decisions — no development work required on your end if you are using a PWA packaging service like ROiBest that handles the technical tracking implementation.

Step 1: Define Your Value Model

Before touching Google Ads, decide which value model fits your business:

• Lead gen model: Assign estimated values based on lead quality. For example, if 10% of PWA installs become paying customers worth $500 on average, your baseline install value is $50. If you can segment by user intent (e.g., users who viewed pricing pages before installing), assign higher values — perhaps $75 for high-intent installs and $30 for generic ones.
• Ecommerce model: Pass dynamic values based on actual transaction amounts. Each purchase event sends its real revenue figure as the conversion value. The PWA install itself can carry a nominal value ($1–$2) as a secondary conversion, while the purchase is the primary conversion action with the real dollar amount.
• Subscription model: Use predicted lifetime value (pLTV). If your average subscriber stays 8 months at $19/month, the pLTV is $152. Discount for churn probability — if 40% cancel within 3 months, your adjusted install value might be $91. As you accumulate more data, refine these estimates quarterly.

Step 2: Create and Configure Conversion Actions in Google Ads

Navigate to Goals → Conversions → Summary in your Google Ads account. Create separate conversion actions for each stage of your funnel:

1. PWA Install: Set this as a secondary conversion action (observation only). Category: “Install.” Value: use the default value from your model in Step 1, or set “Don’t use a value” if you are passing dynamic values for downstream actions only.
2. Post-Install Engagement: This might be “completed onboarding,” “added to cart,” or “submitted lead form.” Set as primary or secondary depending on whether you want Smart Bidding to optimize for this event. Assign a value that reflects the probability of eventual revenue.
3. Revenue Event: Purchase, subscription start, or qualified lead handoff. Set as your primary conversion action. For dynamic values, select “Use different values for each conversion.” Set a default value as a fallback (e.g., your average order value of $65).

For the conversion counting method, use “One” for lead gen (one lead per user matters) and “Every” for ecommerce (multiple purchases from one user all count).

Step 3: Set Conversion Windows Based on Your PWA Funnel Data

In each conversion action’s settings, configure the click-through and view-through conversion windows:

• Click-through window: Analyze your existing data. If 90% of installs happen within 7 days of ad click, a 7-day window is appropriate for the install action. For the revenue event, use the window that captures 85–90% of first purchases — typically 30 days for ecommerce, 14 days for lead gen, and 7 days for impulse/casual apps.
• View-through window: Keep this shorter — typically 1 day for Search campaigns and 3 days for Display/YouTube. PWA installs from view-through impressions are less reliable signals for value optimization.
• Engaged-view window: For YouTube campaigns promoting PWA installs, set this to 3–5 days. Engaged views (10+ seconds watched) correlate with higher-quality installs.

Step 4: Implement Value Rules for Audience Segmentation

Google Ads Conversion Value Rules let you adjust values based on audience, location, and device — without changing your tracking code. This is powerful for PWA campaigns:

• Location rules: If users in Tier 1 markets (US, UK, DE) have 2x the LTV of users in Tier 2 markets, create a value rule that multiplies conversion values by 2.0 for those geos and by 0.5 for lower-value regions.
• Audience rules: Apply higher values for returning visitors (they already know your brand) or users on your CRM-based customer match lists. A 1.5x multiplier for remarketing audiences is a common starting point.
• Device rules: If your PWA performs better on Android (where PWA install prompts are more prominent), you might assign a 1.3x value multiplier for Android traffic and 0.8x for iOS, where PWA install UX is more limited.

These rules stack multiplicatively, so a returning user in the US on Android might get a 2.0 × 1.5 × 1.3 = 3.9x value adjustment. Monitor performance for 2–3 weeks after applying rules before making further changes.

Step 5: Choose the Right Bidding Strategy

With your conversion values configured, select the appropriate bidding strategy:

• Maximize Conversion Value: Best for campaigns in the learning phase or when you want Google to spend your full budget while prioritizing high-value conversions. Use this when you have fewer than 50 conversions per month.
• Target ROAS: Best for mature campaigns with consistent value data. Set your target ROAS based on your breakeven point plus a margin. If your average CPA is $8 and your average conversion value is $40, your baseline ROAS is 500%. Start with a target of 400% to give the algorithm room, then tighten as performance stabilizes.

Avoid switching between strategies frequently. Each change restarts the learning period (typically 1–2 weeks), during which performance may fluctuate. If your PWA landing pages are optimized for install rate, this gives Smart Bidding stronger signals to work with — read more about PMax landing page PWA install optimization for details.

Optimizing Bids with Accurate Value Signals

Once your conversion values are configured and data starts flowing, the real optimization work begins. Here are the practices that separate high-performing PWA install campaigns from mediocre ones.

Monitor the Conversion Value/Cost Ratio Weekly

In Google Ads, navigate to Campaigns → Columns → Modify Columns → Conversions, and add “Conv. value / cost.” This is your true ROAS metric. For healthy PWA campaigns, this ratio should be above 3.0 (meaning $3 in value for every $1 spent). If it drops below 2.0, investigate whether your value assignments are accurate or whether traffic quality has shifted.

Use the Conversion Action Report to Identify Value Gaps

Go to Goals → Conversions → Conversion Actions and compare performance across your install, engagement, and revenue actions. A common pattern in underperforming campaigns is a high install count with low revenue conversion values — this suggests the install value is set too high relative to actual downstream revenue. Recalibrate by reducing the install value or removing it from the primary conversion set entirely.

Segment by New vs. Returning Users

In your campaign reports, segment by audience to see whether new users or returning users generate higher conversion values. For most PWA campaigns, returning users who re-engage through push notifications have 2–3x higher LTV than new installs. Use this data to refine your Conversion Value Rules and bid more aggressively for remarketing audiences.

Test Value Thresholds with Campaign Experiments

Google Ads Campaign Experiments let you run A/B tests on bidding strategies. Create an experiment where the test arm uses a 20% higher target ROAS than your control. Run it for 4 weeks with a 50/50 budget split. If the higher target delivers comparable conversion volume with better efficiency, adopt it. If volume drops significantly, your current target is closer to optimal.

Leverage Seasonality Adjustments for Predictable Value Shifts

If your PWA sees predictable value spikes (Black Friday for ecommerce, end-of-quarter for B2B lead gen), use Google Ads Seasonality Adjustments to tell Smart Bidding about expected conversion rate changes. This prevents the algorithm from over-correcting during high-value periods and then under-bidding when things normalize. Set adjustments 2–3 days before the expected shift and schedule them to end 1–2 days after.

Action Checklist

Use this checklist to ensure your Google Ads conversion value setup for PWA install campaigns is complete and optimized:

• ☐ Define your value model — lead gen (estimated value per lead tier), ecommerce (dynamic transaction values), or subscription (predicted LTV with churn adjustment)
• ☐ Create separate conversion actions for install (secondary), engagement (secondary or primary), and revenue event (primary)
• ☐ Set accurate conversion windows — analyze your funnel data to determine the right click-through, view-through, and engaged-view windows for each action
• ☐ Configure Conversion Value Rules for location, audience, and device adjustments that reflect real LTV differences
• ☐ Choose the right bidding strategy — Maximize Conversion Value for learning phases, Target ROAS for mature campaigns
• ☐ Enable Enhanced Conversions for server-side data accuracy and improved match rates
• ☐ Monitor Conv. value / cost weekly — target a ratio above 3.0 and investigate drops below 2.0
• ☐ Run Campaign Experiments quarterly to test value thresholds and bidding targets
• ☐ Set Seasonality Adjustments for predictable value spikes to prevent Smart Bidding miscalibration
• ☐ Review and recalibrate values every quarter as your PWA funnel data matures and user behavior patterns evolve

Getting conversion values right is not a one-time setup. It is an ongoing process of measurement, adjustment, and refinement. But the payoff is significant: campaigns that bid on accurate value signals consistently outperform those that treat every install as equal. For PWA campaigns running outside the app store ecosystem, this is the most important competitive advantage you can build into your Google Ads account.

---

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