Google App Campaigns: A Practical Setup and Measurement Checklist

A low cost per install tells you what it costs to acquire an installation. It does not tell you whether that person completes onboarding, pays for your product, or returns next week.

Before launching a Google App campaign, decide which outcome matters and verify that your measurement setup can report it. Then build the creative and budget around that goal.

This guide is for acquisition marketers setting up campaigns or investigating a gap between install volume and customer value. App campaigns were previously known as Universal App Campaigns, or UAC.

Choose the outcome before the bid strategy

Start with the action that represents progress for your business. That could be an install, a completed registration, a first order, or a paid subscription.

An install-focused campaign can help build a user base. If your goal is to acquire people who complete an in-app action, the campaign needs that action configured and reporting reliably. Value-based optimization also requires usable conversion values.

For example, a subscription app might measure installs, onboarding completion, trial starts, and paid subscriptions. Those events answer different questions. Select the optimization goal deliberately rather than treating every event as equally valuable.

Check the options available for your campaign and platform in Google’s App campaign bidding guidance.

Test the attribution setup before spending

Google supports app conversion measurement through Firebase and approved attribution partners. If you use an MMP such as Adjust or Singular, validate the app integration and the connection to Google Ads before launch. See Google’s measurement setup guidance.

Work through the journey on each supported platform. Confirm that the app records the event, sends the expected properties, and makes it available in the destination used for campaign optimization.

Event definitions: agree on when an action counts as completed.
Counting: decide whether repeated actions should count once or each time.
Values: check amounts and currencies for revenue events.
Duplication: inspect overlapping integrations that may report the same action.
Timing: understand how long the event takes to appear.
Platform differences: validate Android and iOS separately.

For iOS, include the applicable privacy and attribution configuration in the implementation scope. Do not assume that a successful Android test validates the iOS setup.

Understand why Google Ads and your MMP differ

Before treating a reporting difference as an integration failure, compare the definitions behind the numbers.

Check attribution windows, reporting time zones, event counting, and whether the reports include the same conversion types. Google specifically recommends checking conversion-window alignment with third-party measurement systems. Review Google’s App campaign measurement guidance.

Document which report the team uses for bidding decisions and which it uses for business reporting. Investigate changes in the gap over time, rather than expecting every platform to produce identical totals.

Build creative around real app use

Show what the user can do in the app and why that action is useful. A product demonstration, a customer problem, and a specific feature give you different messages to evaluate.

Prepare images and videos in the formats supported by the campaign. Check current upload requirements in Google Ads rather than treating one asset count as a universal rule.

Review the assets together:

Text makes sense in different combinations.
The advertised feature exists in the current app.
Prices and offers match the store listing and onboarding flow.
Important text remains readable on a phone.
Videos communicate the product clearly, including when viewed without sound.
Each creative concept has a clear audience need or benefit.

If an ad promotes a feature users cannot find after installation, investigate that journey before producing more versions of the ad.

Set a budget that fits the selected goal

Use acquisition economics to set your target. Consider what an acquired user is worth, how often they reach the desired outcome, and how long that takes.

Google’s setup guidance recommends an average daily budget of at least 50 times target CPI for install-volume campaigns, and 10–15 times target CPA for in-app-action campaigns. These are platform planning recommendations; they do not establish whether the spend is affordable for your business. See Google’s goal-specific budget guidance.

For example, a $2 target CPI implies a $100 average daily budget under the 50-times recommendation. Check that the resulting spend fits your test budget before launching.

Keep platform, country, currency, bid target, and budget ownership visible in your campaign documentation.

Evaluate results after accounting for conversion delay

Users may subscribe or purchase days after installation. A recent cohort has had less time to convert than an older one.

Google advises allowing time for learning after significant changes. Use campaign status, conversion volume, and the actual delay to your selected outcome when deciding whether you have enough evidence to evaluate a change.

Fix broken measurement or an incorrect destination when you find it. For performance changes, keep a record of the hypothesis and avoid changing the goal, bid, budget, and creative together.

Read asset performance labels as relative feedback within the campaign. An asset rated highly in one campaign is not proof that the concept will perform equally well elsewhere.

Google App campaigns launch checklist

The intended app, operating system, markets, and languages are correct.
The store listing and onboarding flow support the ad’s promise.
The campaign goal matches the outcome the team wants to acquire.
The selected conversion event has been tested end to end.
Revenue values, currencies, and counting settings are correct where applicable.
The team understands reporting windows and expected conversion delays.
Creative assets meet current specifications and represent the app accurately.
The bid target and budget fit both campaign requirements and business economics.
Someone owns tracking checks after app releases.
Changes and unresolved measurement issues are documented.

After launch, review downstream outcomes alongside acquisition costs. Install volume, paid conversion, and retention answer different questions about the users you acquired.