This beginner's guide adapts Xiao Wei's 2022 article on Google app advertising for teams promoting a Google Play app. The original screenshots and some menu names reflect an older Google Ads interface. This version preserves the useful workflow while updating recommendations that need current context.
1. Prepare the store listing, account, and measurement
Confirm that your app is live on Google Play and that its store listing, target markets, language, and policy status are ready. A Google Ads manager account (MCC) can organize multiple accounts, but verify campaigns, conversions, and billing in the relevant child account.
Set up app measurement with Firebase (Google Analytics for Firebase) or a third-party attribution partner such as AppsFlyer. Link it to Google Ads, map the events you need, and confirm the necessary permissions. Test that installs and in-app events are actually imported before increasing spend; a connected status alone is not enough.
2. Choose the right conversion goal
Decide what this campaign should optimize for: new users, registrations, purchases, or another valuable in-app action. Pick an event that is reliably reported and tied to your business goal. The 2022 article recommended making first_open a primary conversion in every case. That is not a universal rule: counting both installs and first opens as new users can inflate results. Check your measurement setup and conversion settings before selecting a primary action.
Review event names, primary versus secondary actions, attribution, and conversion windows so reporting matches the bidding goal. See Google Ads app conversion guidance.
3. Create the App campaign
- Select an App campaign in Google Ads and choose the correct Google Play app.
- Choose the campaign objective and bidding goal, such as installs or in-app actions.
- Set locations, languages, and a sustainable daily budget. Match these choices to the store listing and creative.
- Add text, images, and videos, then review policy status, tracking, and previews.
The original article cited daily budgets of $50–70 or $200–500. These are historical examples, not universal thresholds. Set a budget based on target CPA or ROAS, expected conversion volume, test duration, and Google's current bidding guidance. See campaign setup and creative and budget best practices.
4. Test creative with clear hypotheses
The original workflow used two or three ad groups to compare creative directions. That can still be useful if each group tests a clear idea—for example, product features, use cases, or user benefits. Avoid changing too many variables at once. Use the formats and asset requirements shown in the current Google Ads interface; the article's 1200×628 and 1200×1200 image sizes are not the only specifications to follow.
Provide varied copy, images, and videos so the system has combinations to test. Asset ratings are relative signals; judge creative alongside install cost, in-app conversions, and retention. See asset performance reporting.
5. Review performance after launch
- Confirm delivery and event reporting first, then evaluate CPA, ROAS, and the outcome that matters to the business.
- Compare markets, languages, creative concepts, and time periods after enough data has accumulated.
- Use the App campaign placement report to understand impression distribution. Its placement data is limited; it does not provide a complete spend, conversion, and CPA breakdown for every placement.
- Refresh tired creative, keep effective concepts, and test new variations.
See Google's App campaign placement reporting guide. Explore more on our advertising guides page.
FAQ
Are UAC and App campaigns different products?
No. UAC is an older name commonly used for what Google Ads now calls App campaigns.
Should a new campaign optimize for installs or purchases?
It depends on your business goal and event volume. If purchase events are too sparse for useful learning, consider an earlier event that is still related to value; revisit the goal as measurement and performance stabilize.
Can I reuse the article's fixed budgets and image sizes?
Treat them as a 2022 example. Use current interface requirements, target CPA or ROAS, and your own test results for launch decisions.