Google Ads Apps: App Campaigns from Goal Selection to Optimization
This domain tests whether you can set up, bid on, and optimize Google Ads App campaigns end to end. App campaigns run a single campaign across Google Search, Google Play, YouTube, Discover, the Display Network, and in-app inventory, so the exam focuses on the decisions that replace manual targeting: campaign goal, bid strategy, creative asset groups, conversion measurement, and platform constraints such as iOS attribution.
The goal decides almost everything
- Available goals: app installs, in-app actions (including value/tROAS), engagement (re-engaging people who already installed, driven by deep links), and pre-registration for Android apps not yet launched.
- The goal sets which bid strategies appear. Install-focused campaigns offer install-volume bidding and target cost per install (tCPI); in-app action campaigns offer target CPA and, once value data is flowing, target ROAS.
- There is no keyword or audience targeting. Reach is controlled by location, language, network settings, budget, bids, and the assets themselves; Google's machine learning matches your app store listing and creative to likely users.
- Changing the goal resets learning, so pick the goal that matches the business outcome you can actually measure.
Creative is the targeting signal
Supply up to 5 headlines, 5 descriptions, images, videos, and HTML5 assets per asset group; Google mixes them into multiple formats automatically. If you skip text assets, they are pulled from your store listing, which works but usually reads like marketing copy rather than an ad. Build separate asset groups per theme or language and watch ad strength (Incomplete, Average, Good, Excellent) as a coverage indicator, not a performance guarantee.
Measurement plumbing comes first
Conversions are attributed through Firebase or an app attribution partner (AppsFlyer, Adjust, Branch, Kochava, Singular). On iOS, App Tracking Transparency consent and SKAdNetwork configuration determine what you can see; postbacks are aggregated and delayed, so install-level granularity is limited by design.
Worked example
A fitness app spends $1,000/day on an installs campaign at tCPI $2.00, expecting roughly 500 installs daily. Firebase shows 3% of installers start a free trial, so about 15 trials per day. The team wants to switch to tCPA $20 for trials. Reasoning: 15 conversions/day × $20 = $300/day of spend the tCPA can justify, far below the $1,000 budget, so the campaign would throttle. The correct sequence is to keep driving installs, improve the install-to-trial rate, and only then launch an in-app actions campaign with a tCPA it can support, adding tROAS later once purchase values are stable.
Traps that cost marks
Judging performance inside the learning period and editing assets daily; assuming you can add keywords or audience segments; expecting tCPI to optimize in-app actions; and forgetting that iOS reporting depends on ATT/SKAdNetwork setup.