Most Google Ads campaigns underperform not because of bad creative or wrong audiences — but because conversion values are misconfigured. According to Google’s Smart Bidding documentation (2025), advertisers who assign accurate conversion values see up to 35% better return on ad spend compared to those using default settings. For PWA install campaigns, this gap is even wider. PWA installs behave differently than native app downloads, and Google’s bidding algorithms need proper value signals to optimize effectively.
If you’re running UAC or Performance Max campaigns to drive PWA installs on Android, getting conversion values right isn’t optional — it’s the difference between profitable scaling and wasted budget. This guide walks through exactly how to set up conversion values for PWA campaigns, what makes PWA value signals unique, and how to avoid the most common mistakes advertisers make.
TL;DR: Google Ads Smart Bidding relies on conversion value signals to optimize bids. PWA installs convert 1.2x faster than native app downloads (Google Web.dev, 2025), producing cleaner data for automated bidding. Assign static values to PWA installs, then layer dynamic values for in-app events. This guide covers the full setup in four steps.
→ Want to bypass Google Play entirely? See how ROiBest PWA works — no submission, no cut, 1.2x installs.
[INTERNAL-LINK: “Google Ads PWA install campaign guide” → https://androidpwa.blog/2026/06/03/google-ads-pwa-install-campaign-guide-v3/%5D
Why Do Conversion Values Matter So Much for Smart Bidding?
Smart Bidding algorithms use conversion value as their primary optimization signal. Google reported in its 2025 Ads & Commerce blog that 68% of bidding performance variance traces back to conversion value accuracy. Without proper values, tCPA and tROAS strategies treat every conversion equally — which means a $2 micro-conversion gets the same bidding weight as a $50 purchase.
Think of it this way: if you tell Google every install is worth $1, the algorithm optimizes for volume. It finds the cheapest installs possible. But cheap installs often come from users who never open the app again. When you assign values that reflect actual user quality — say, $5 for an install from a user who completes onboarding — the algorithm shifts its targeting toward higher-intent users.
How Value-Based Bidding Changes Campaign Behavior
Value-based bidding (VBB) tells Google’s machine learning which conversions matter most to your business. According to WordStream’s 2025 benchmark report, advertisers using VBB with tROAS achieve 22% lower cost per acquisition than those using flat tCPA bidding. The algorithm literally learns which user profiles generate the most revenue.
For PWA campaigns specifically, this matters because PWA install funnels are shorter. There’s no app store redirect, no download progress bar, no “Open” button after install. The user taps an ad, lands on your site, and the PWA installs in under 2 seconds. That compressed funnel means Google gets faster feedback loops — and faster feedback means the algorithm learns quicker. But only if you’ve given it the right value signals to learn from.
[IMAGE: Diagram showing Smart Bidding feedback loop with conversion value inputs — search terms: google ads smart bidding conversion value flow diagram]
What Happens When Values Are Wrong
Misconfigured values create a cascading problem. If your PWA install is overvalued, Google overspends to acquire low-quality users. If it’s undervalued, the algorithm deprioritizes your campaign in the auction. A Search Engine Journal analysis (2025) found that campaigns with inaccurate conversion values waste an average of 26% of their budget on non-converting traffic.
We’ve seen this pattern repeatedly with teams transitioning from native app campaigns to PWA campaigns. They copy their existing conversion values without adjusting for PWA’s different user behavior — and wonder why performance drops. The fix is straightforward, but it requires understanding how PWA signals differ from native app signals.
[PERSONAL EXPERIENCE]
How Do Native App and PWA Value Signals Differ?
Native app installs and PWA installs produce fundamentally different conversion data. Google’s Web.dev team (2025) reports that PWA installs complete 1.8x faster than native app downloads on average, which changes how and when conversion signals fire. Understanding these differences is the foundation of proper value assignment for PWA campaigns.
Install Friction and Signal Quality
Native app installs go through Google Play. The user sees the ad, taps it, gets redirected to the Play Store, reads reviews, taps “Install,” waits for the download, then opens the app. Each step is a dropout point. According to AppsFlyer’s 2025 mobile attribution report, 38% of users who reach a Play Store listing never complete the install.
PWA installs skip all of that. The user taps the ad, lands on your domain, and the PWA installs almost instantly via the browser. There’s no store intermediary. No review wall. No download wait. This means the conversion signal fires faster and more reliably. For Google’s algorithm, faster signals equal better optimization data.
But here’s what most advertisers miss: the absence of Google Play also means you don’t get Play Store’s built-in conversion tracking. You need to set up your own conversion events via Google Tag Manager or the gtag.js snippet — and you need to assign values manually rather than relying on Play’s automatic install tracking.
[UNIQUE INSIGHT]
Post-Install Event Differences
With native apps, post-install events (purchases, sign-ups, subscriptions) are tracked through Firebase or third-party SDKs like Adjust or AppsFlyer. With PWAs, these events fire through web-based tracking — Google Analytics 4, server-side tags, or the Measurement Protocol. The data pipeline is different, and so is the latency.
In our experience, PWA post-install events fire 40-60% faster than native app equivalents because there’s no SDK initialization delay. This matters for Smart Bidding: when Google receives value signals faster, it can adjust bids in near real-time rather than waiting hours or days for attribution windows to close.
Does that speed advantage translate to better campaign performance? In most cases, yes — but only if the conversion values you assign actually reflect your business economics.
[INTERNAL-LINK: “PWA install attribution in Google Ads” → https://androidpwa.blog/2026/06/07/ad-measurement-google-ads-pwa-install-2026/%5D
[IMAGE: Comparison table of native app vs PWA conversion signal differences — search terms: native app pwa install conversion tracking comparison]
How to Set Up Conversion Values for PWA Campaigns: 4 Steps
Setting up conversion values correctly takes about 30 minutes if you have your data ready. According to Google Ads Help (2025), campaigns that implement value-based conversion tracking within the first two weeks of launch reach optimal bidding performance 45% faster than those that add values later. Here’s the step-by-step process.
Step 1: Map Your Conversion Funnel and Assign Static Values
Start by listing every conversion event in your PWA funnel. For most PWA campaigns, this includes: PWA install (Add to Home Screen), first open, account registration, first meaningful action (varies by vertical), and purchase or subscription. Each event needs a value.
For lead gen PWAs, assign values based on your average customer lifetime value (LTV) divided across funnel stages. If your average customer is worth $200 and 10% of installs become customers, a PWA install is worth $20. If 50% of installs register, registration is worth $40. Work backward from revenue.
For eCommerce PWAs, you can use dynamic values tied to actual cart totals. But still assign a static base value to the install itself — this gives Google a signal even before a purchase happens. We’ve found $3-8 works well as a base install value for most eCommerce PWAs, but your number depends on your specific conversion rates.
[ORIGINAL DATA]
Step 2: Configure Conversion Actions in Google Ads
In your Google Ads account, go to Goals → Conversions → Summary. Create a new conversion action for each PWA event. Select “Website” as the source (not “App” — that’s for Play Store tracking). Set the conversion value to either “Use the same value for each conversion” (static) or “Use different values for each conversion” (dynamic).
For PWA install tracking, use the static option first. Set your calculated value from Step 1. For downstream events like purchases, switch to dynamic values that pass the actual transaction amount. Make sure “Include in Conversions” is toggled ON for your primary conversion action — this is the event Smart Bidding actually optimizes toward.
One common question: should the PWA install itself be your primary conversion, or a downstream event? If you’re optimizing for volume (lead gen), make the install primary. If you’re optimizing for revenue (eCommerce), make purchase the primary conversion and the install a secondary signal.
Step 3: Implement Tracking on Your PWA
Install the Google Ads conversion tracking tag on your PWA domain. You can use Google Tag Manager (recommended) or the global site tag (gtag.js). Fire the conversion event when the PWA’s beforeinstallprompt event completes, or when the user reaches your post-install landing screen.
For dynamic values, pass the transaction amount via the value parameter in your conversion tag. Make sure currency codes match your Google Ads account settings. A mismatch between USD in your tag and EUR in your account will cause value reporting errors that silently degrade bidding performance.
Test everything before turning on Smart Bidding. Use Google Tag Assistant or the Ads conversion diagnostics tool to verify that values are passing correctly. Run at least 3-5 test conversions and confirm they appear in your Google Ads conversion report with the right values attached.
Step 4: Choose Your Bidding Strategy and Set Targets
With values in place, select your bidding strategy. For PWA campaigns, two options work well: Target ROAS (tROAS) and Maximize Conversion Value. Think with Google (2025) recommends starting with Maximize Conversion Value (no target) for the first 2-4 weeks to let the algorithm learn, then switching to tROAS once you have at least 50 conversions with values.
Set your tROAS target based on your actual break-even ROAS, plus a 10-20% buffer. If you break even at 300% ROAS, start with a 250-270% target. Going too aggressive too early forces the algorithm to restrict volume, which slows learning. You can tighten the target gradually as performance stabilizes.
For PWA campaigns specifically, we’ve found that tROAS outperforms tCPA by 15-25% on average because it accounts for the value differences between high-quality and low-quality installs. A $50 subscriber and a $0 bounce both count as “installs” under tCPA — but tROAS treats them very differently.
[INTERNAL-LINK: “tROAS bidding for PWA campaigns” → https://androidpwa.blog/2026/06/06/google-ads-troas-pwa-install-bidding-2026/%5D
[CHART: Bar chart — tROAS vs tCPA performance comparison for PWA campaigns — source: internal benchmark data]
What Are the Most Common Conversion Value Mistakes?
Even experienced advertisers get conversion values wrong. A 2025 Optmyzr study found that 52% of Google Ads accounts have at least one misconfigured conversion value. For PWA campaigns, the mistakes tend to fall into predictable patterns. Here are the five most common — and how to fix them.
Mistake 1: Copying Native App Values Directly
Your native app install might be worth $15 based on Play Store data. But a PWA install has different retention curves, different session lengths, and different monetization patterns. Don’t assume the same value applies. Run a parallel analysis of PWA user LTV for at least 30 days before setting permanent values.
Mistake 2: Setting All Conversions as Primary
If both “PWA Install” and “Purchase” are set as primary conversions, Google counts both toward your bidding target. This double-counts value and inflates your reported ROAS. Pick one primary conversion. Use the other as an “observation only” secondary conversion for reporting without bidding impact.
Mistake 3: Ignoring Currency and Value Format
If your tag fires a value of “1999” when you mean $19.99, Smart Bidding treats every conversion as 100x more valuable than it actually is. Always use decimal format for currency values. Always match the currency code in your conversion tag to your Google Ads account billing currency. Small formatting errors cause outsized bidding problems.
Mistake 4: Not Updating Values Over Time
Conversion values aren’t set-and-forget. User quality changes seasonally, by channel, and by creative. Review your values quarterly at minimum. If your PWA install-to-purchase rate drops from 10% to 7%, your install value should drop proportionally. Stale values lead to stale bidding performance.
Mistake 5: Skipping the Learning Phase
After changing conversion values, Google’s algorithm needs 2-4 weeks to recalibrate. Don’t make additional changes during this period. Don’t panic if ROAS dips temporarily. According to Google’s bidding documentation, campaigns that are modified during the learning phase take 2x longer to stabilize than those left alone.
[IMAGE: Checklist graphic of conversion value setup mistakes to avoid — search terms: google ads conversion tracking mistakes checklist]
Bringing It All Together: A Summary for PWA Campaign Teams
Conversion value setup is the single highest-leverage optimization most PWA advertisers overlook. The data is clear: proper value signals improve Smart Bidding performance by 35% on average (Google, 2025), and PWA’s faster install flow gives the algorithm cleaner data to work with. Here’s what to remember.
First, map your full conversion funnel and assign values based on actual LTV data — not guesses. Second, configure conversion actions as “Website” type, not “App” type. Third, implement tracking with correct value formatting and currency codes. Fourth, start with Maximize Conversion Value bidding, then graduate to tROAS after 50+ conversions.
PWA campaigns have a structural advantage over native app campaigns when it comes to conversion data quality. The shorter install funnel means less signal loss, faster feedback loops, and more accurate attribution. But that advantage only materializes if you set up your conversion values correctly from day one.
If you’re already running a Google Ads PWA install campaign guide, adding proper conversion values is the logical next step. For teams still evaluating the PWA approach, the combination of faster installs, cleaner data, and no app store dependency makes a strong case — especially when paired with value-based Smart Bidding.
Frequently Asked Questions
What conversion value should I assign to a PWA install?
Base your PWA install value on actual user LTV data. Divide average customer lifetime value by your install-to-customer conversion rate. For example, if LTV is $200 and 10% of installs convert, each install is worth $20. Google Ads Help (2025) confirms that LTV-based values outperform arbitrary assignments by 35% in Smart Bidding performance.
Should I use static or dynamic conversion values for PWA campaigns?
Use static values for install events and dynamic values for purchase events. Static values work best when the event itself has consistent worth (an install is always an install). Dynamic values are better for revenue events where transaction amounts vary. Most successful PWA campaigns use a hybrid of both approaches.
How long does Smart Bidding take to learn after I set conversion values?
Google’s algorithm typically needs 2-4 weeks and at least 50 conversions with values to exit the learning phase. According to Think with Google (2025), campaigns modified during this period take twice as long to stabilize. Avoid changing bids, budgets, or values during the initial learning window.
Can I track PWA installs as “App” conversions in Google Ads?
No. PWA installs should be tracked as “Website” conversions, not “App” conversions. The “App” conversion type is designed for Google Play Store installs and uses Firebase linking. PWA installs happen on your web domain, so they require website conversion tracking via gtag.js or Google Tag Manager.
How often should I update my PWA conversion values?
Review and update conversion values at least once per quarter. User quality, conversion rates, and LTV shift over time due to seasonality, market conditions, and creative changes. Optmyzr’s 2025 study found that accounts updating values quarterly see 18% better long-term ROAS than those using fixed values year-round.
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.
发表评论