Google App Campaigns are underused because they're fully automated — practitioners used to granular controls feel uncomfortable handing over the wheel. That discomfort is the opportunity. When set up correctly (measurement first, budgets at 10–20× your tCPA target, iOS and Android in separate campaigns, and a real creative pipeline), App Campaigns are one of the most cost-efficient mobile acquisition channels available, especially on Android.
Key takeaways
App Campaigns are fully automated, so measurement quality, bid targets, budget level, and creative assets are the only levers that actually matter.
Always separate iOS and Android into distinct campaigns — the CPIs, creative performance, and optimization signals are too different to combine.
Launch tCPA 20–30% above your real goal and fund each campaign at 10–20× that target daily; underfunding is the single most common reason new App Campaigns fail.
Firebase (or a supported MMP postback) is non-negotiable for conversion data — using GA4 web+app events as your optimization signal produces unreliable results.
Respect the 7–14 day learning phase: avoid changing budgets, bids, or creative until the algorithm has enough conversion data to stabilize.
Key terms
tCPA (Target CPA)
A Smart Bidding target that tells Google's algorithm what you want to pay per conversion; it works as an optional target within the Maximize Conversions bid strategy.
Learning Phase
A 7–14 day window after a campaign launches or is significantly changed, during which Google's algorithm collects conversion data before it can optimize reliably.
MMP (Mobile Measurement Partner)
A third-party attribution platform (such as AppsFlyer, Adjust, or Branch) that tracks installs and in-app events across multiple paid channels in one unified view.
Firebase
Google's native mobile analytics SDK that sends install and in-app event data directly into Google Ads, providing the cleanest conversion signal for App Campaign optimization.
SKAdNetwork (SKAN)
Apple's privacy-preserving attribution framework for iOS that limits the granularity of install and post-install data available to advertisers and measurement partners.
---
Why do Google App Campaigns get so little attention from PPC practitioners?
The short answer is that automation makes practitioners uncomfortable. The question came up recently in the r/PPC community, and the thread revealed a pattern: most app advertisers running serious budgets on Meta and TikTok haven't seriously tested Google's channel, not because it doesn't work, but because they never learned the setup rules specific to it.
Unlike Search campaigns — where you control keywords, match types, bids, and audiences — App Campaigns surrender all of that to Google's algorithm. [1] For practitioners who find Google Ads confusing enough already, adding a black-box campaign type feels risky. The result is that the channel stays underinvested, which also keeps CPIs lower for those who do run it well.
The other practical factor: App Campaigns require Firebase or a mobile measurement partner (MMP) to function properly. Advertisers already running Meta and TikTok through an MMP often assume the Google setup is handled — it usually isn't configured correctly for App Campaign optimization.
What are the three App Campaign types and when should you use each?
Google offers three distinct App Campaign subtypes, and most advertisers only ever run one of them, which is why results plateau.
Campaign Type
Primary Goal
Best For
Notes
App Installs
New user acquisition
New markets, bootstrapping Android volume
Run until you hit 50–100 installs/day before moving to event optimization
App Engagement
Re-engage existing users
LTV improvement, winback, subscription upgrades
Criminally underused; CPA on deep events often runs 40–70% below install CPA
App Pre-Registration
Pre-launch awareness
New Android app launches, major updates
Android only; CPM/CPC model; seeds early reviews and Day 1 install velocity
If you're spending meaningful budget on acquisition and nothing on re-engagement, you're refilling a leaky bucket. App Engagement campaigns targeting users who installed but haven't opened the app in 14–30 days are a direct LTV lever most app advertisers ignore entirely.
How should you set bidding strategy for App Campaigns without wasting the learning phase?
Bidding setup is where most App Campaigns fail before they ever get a chance to prove value. Google's App Campaigns use Smart Bidding — the algorithm needs a minimum conversion volume to function, and launching with targets that are too aggressive starves it of that data. [2]
Target CPA
Set a target cost per install or per in-app event, and the algorithm optimizes toward it. [3] In practice, this requires at least 30–50 conversions per week before the algorithm stabilizes. Below that threshold, campaigns underspend or spike erratically.
Target ROAS
Available when you're passing revenue values back through Firebase. [4] Use this when your app monetizes through in-app purchases or subscriptions and you have consistent revenue data flowing. In accounts I manage, tROAS doesn't become reliable until you're seeing at least 100+ purchase events per week.
Common Mistake: Setting an aggressive tCPA on day one because your Meta CPI is $4.00 and you want parity immediately. Launch 20–30% above your actual target — if you want a $4.00 CPI, start at $5.00–$5.50. Launching too tight causes the campaign to underspend and never exit the learning phase. Tighten the target by ~10% every two weeks as conversion data accumulates.
Best Practice: Set your daily budget at 10–20× your tCPA target. At a $5.00 tCPA, that means $50–$100/day minimum per campaign. Underfunding is the single biggest structural reason new App Campaigns underperform — the algorithm needs daily conversion volume, not weekly trickles. [5]
Respecting the learning phase
App Campaigns have an explicit learning phase of approximately 7–14 days after launch or after any significant change. During this window, avoid adjusting tCPA by more than 15–20%, changing your creative set, or materially changing your budget. Any of these resets the learning clock. Practitioners who make weekly changes in the first month consistently report that "the campaign never stabilized" — that's the direct cause.
What creative strategy actually works when you control almost nothing else?
Because you can't control keywords, placements, or audiences, creative is your primary optimization lever inside App Campaigns — and Google's algorithm distributes your assets across Search, YouTube, Display, Discover, and the Play Store simultaneously.
Asset requirements that move the needle
Video is non-negotiable. App Campaigns heavily weight video assets, especially for YouTube inventory. Minimum: 4–6 videos in 16:9, 1:1, and 9:16 aspect ratios. Launching with only static images cedes YouTube inventory to competitors.
Lead with your hook in the first 3–5 seconds. YouTube skippable ads mean users bail immediately. A logo hold or brand intro at the start is a wasted impression.
Show real in-app footage. For consumer apps, showing the actual product experience in the first few seconds measurably improves CTR and downstream conversion rates.
Use all text asset slots. Google uses text assets for Search placements and Play Store listings. Fill all five headline and five description slots with meaningfully different angles — value prop, social proof, urgency, feature-focused.
Reading asset performance ratings
Google scores each asset as "Low," "Good," or "Best" based on its contribution to performance. Assets rated "Low" for two or more consecutive weeks should be replaced. The algorithm's signal is the only feedback that matters; don't preserve creative you like if the data says it isn't working.
Key Insight: The advertisers who consistently win with App Campaigns treat creative production as a recurring budget line item. A useful benchmark from accounts at scale: allocate 10–15% of your App Campaign budget toward creative production and testing, and refresh assets every 4–6 weeks. Creative fatigue is harder to detect without placement-level reporting, so build a refresh cadence regardless of whether you see obvious signals.
Why does measurement setup determine whether App Campaigns succeed or fail?
App Campaigns live and die on the quality of conversion data flowing into Google Ads — bad measurement is invisible until you've wasted weeks of budget learning from noise. Unlike web campaigns where tagging is handled through Google Tag Manager, App Campaigns require Firebase or a supported MMP (AppsFlyer, Adjust, Branch) configured with proper postbacks.
Factor
Firebase (Native)
MMP (AppsFlyer, Adjust, Branch)
Setup complexity
Moderate
Higher initial setup
Cross-channel view
Google-only
All paid channels unified
Data quality for Google
Best (native integration)
Good, with proper postback configuration
iOS attribution
Limited (SKAdNetwork)
Better SKAdNetwork modeling tooling
Best for
Android-first or Google-only spenders
Multi-channel app advertisers at significant daily spend
For advertisers already spending $15k/day across Meta and TikTok, an MMP is almost certainly worth the cost. The unified view of installs, cost, and LTV across channels is essential when making budget allocation decisions at that scale. Configure MMP postbacks to send the same conversion events you're optimizing toward — installs, registrations, purchases — within a 24-hour window where possible.
Common Mistake: Importing GA4 app events into Google Ads and using those as your App Campaign optimization signal. GA4 web+app properties have significant session-based sampling and attribution gaps for mobile. Use Firebase events imported directly into Google Ads, or MMP postbacks — not GA4 conversions — as your primary optimization signal for App Campaigns.
How do you scale Google App Campaigns alongside existing Meta and TikTok spend?
Adding a new channel to an existing paid mix raises real budget allocation questions, and the right answer is a phased approach that lets Google's algorithm accumulate data before you commit significant reallocation.
Phase 1: Baseline test (Weeks 1–4)
Launch one Android Installs campaign and one iOS Installs campaign — never combine OS in one campaign.
Set budgets at 10–20× your tCPA target per campaign.
Set tCPA at 20–30% above your actual goal.
Do not touch campaigns during the first 14 days.
Phase 2: Incremental scaling (Weeks 5–8)
Review asset performance ratings and replace "Low" assets.
If tCPA is tracking below target, increase budget 15–20% and tighten tCPA by 10%.
Add an in-app event campaign if install-to-event rates are strong (a typical signal is >15% install-to-registration).
Compare Google-attributed installs to MMP-attributed installs — some discrepancy is normal, but if Google claims 2× what your MMP reports, investigate postback configuration.
Phase 3: Full integration (Month 3+)
Shift Android budget progressively toward Google — in accounts I manage, Google frequently wins on Android CPI versus Meta.
Add App Engagement campaigns targeting lapsed users (installed but no open in 14–30 days).
Test tROAS bidding if you have sufficient purchase volume (>100/week).
Best Practice: Always segment iOS and Android into separate App Campaigns. Bid prices, creative performance, and optimization signals are completely different between the two OS environments. Combining them forces the algorithm to average across very different user pools and typically degrades performance for both. This is a structural rule that applies at any meaningful spend level — and if you're unsure whether your current account structure is working against you, a 250-point Google Ads audit can surface structural issues like this quickly.
What to do next
Audit your Firebase or MMP setup before spending a dollar. Confirm that install events, key in-app events (registration, purchase, subscription start), and revenue values are flowing cleanly into Google Ads. Bad measurement kills campaigns before they can prove value.
Launch Android first. If your Android base is small and your iOS is already scaled on Meta, start Google App Campaigns on Android. Lower CPIs, cleaner attribution via Firebase, and less overlap with your existing Meta spend make Android the right test market.
Set tCPA 20–30% above your actual goal and fund it properly. If you want a $4.00 CPI, launch at $5.00–$5.50 tCPA with a daily budget of at least $250–$500 per campaign. Underfunding is the most preventable reason new App Campaigns fail.
Build your creative set before launch. Prepare at least four videos (in 16:9, 1:1, and 9:16), ten images, five headlines, and five descriptions. Launching with minimal creative kneecaps the algorithm's ability to find what works across Google's inventory.
Set calendar reviews at day 14 and day 28 — and don't touch campaigns between them. Over-management is the biggest operational mistake with App Campaigns. If you want ongoing monitoring without the temptation to over-intervene, Buddy, the AI Google Ads agent, can flag anomalies without requiring you to make changes manually.
Frequently asked questions
Can I run Google App Campaigns without Firebase?
You can connect a supported MMP (AppsFlyer, Adjust, or Branch) instead of Firebase, and for multi-channel advertisers that's often the better choice. What you cannot do is use GA4 web+app events as your primary optimization signal — those have sampling and attribution gaps that make App Campaign bidding unreliable. One of Firebase or a properly configured MMP postback is required.
Why is my App Campaign stuck in the learning phase?
The most common causes are: daily budget too low relative to tCPA (below 10× your target), tCPA set too aggressively so the campaign rarely spends, or someone made a bid or budget change within the first 14 days and reset the clock. Check budget-to-tCPA ratio first, then look at whether any changes were made during the learning window.
Should I combine iOS and Android in the same App Campaign?
No — always run them in separate campaigns. iOS and Android have different CPI benchmarks, different attribution constraints (SKAdNetwork on iOS versus deterministic Firebase data on Android), and different creative performance patterns. Combining them forces Google to optimize toward an average of two distinct user pools and typically hurts performance on both platforms.
How do I know when to switch from App Installs to App Engagement campaigns?
Start testing App Engagement campaigns once your install volume is large enough to define a meaningful re-engagement audience — generally after you've accumulated at least several thousand installs with identifiable drop-off patterns. A common trigger is identifying users who installed but haven't opened the app in 14–30 days. Engagement campaigns optimizing toward a specific in-app event often show CPA well below what install campaigns deliver on the same event.
How does Google App Campaign creative differ from Meta creative strategy?
The core difference is feedback loop speed and specificity. On Meta you get placement-level data and can diagnose creative fatigue by audience segment. On Google App Campaigns, you only get asset-level "Low / Good / Best" ratings across all inventory combined. That means you build a refresh cadence based on time (every 4–6 weeks) rather than waiting for obvious fatigue signals, and you rely on the algorithm's rating rather than your own creative intuition.
Is it normal for Google-reported installs to differ from MMP-reported installs?
Some discrepancy is expected because Google and your MMP use different attribution windows and models. A small gap (10–20%) is normal. If Google is claiming 2× or more of what your MMP reports, investigate your postback configuration — the MMP may not be sending conversion data back to Google correctly, which also means the bidding algorithm is optimizing on incomplete signal.
AI Disclosure: This article was generated with AI assistance based on a community discussion on Reddit r/PPC. Expert analysis and practitioner perspective by John Williams, Founder, AHMEEGO · Google Ads Practitioner with $350M+ in managed Google Ads spend. AI was used to draft and structure the content; all strategic recommendations reflect real campaign experience.