Conversion signals · Optimization goals
Optimize for installs, registrations or purchases? Start with the signals you can provide
A goal closer to revenue is not always the right immediate choice. Check event volume, conversion delay and real value before selecting an optimization goal.
In short: installs, registrations and purchases are not three names for the same goal. When purchases are sparse, feedback is slow and real values are unavailable, do not rush into purchase-value optimization. Make signals reliable and stable before moving towards revenue.
Your goal tells the system which users to find
Google Ads describes app-campaign optimization around installs, in-app actions or conversion value. Choosing installs prioritizes installs; choosing an in-app event prioritizes users more likely to complete it. Comparing both only by install price misses their different purposes.
Installs are usually easier to accumulate, but only establish an early action, not continued usage. Registration is closer to real use but may still include low-intent users. Purchases are closer to revenue yet rarer and later; their suitability depends on your data conditions.
“Deeper is better” is therefore not a decision rule. The closer the goal is to revenue, the more important it is to confirm the action really happened, was recorded correctly and happens more than occasionally. Otherwise the business has a clear wish, but the system lacks evidence to pursue it.
A hypothetical case: a deep goal with thin feedback
Imagine an app with ongoing installs and registrations but uneven purchases. Some users pay much later, and reporting only says a purchase occurred without a real amount. This is a hypothetical reasoning example, not measured customer returns or a particular product.
If the goal immediately becomes revenue return, the platform has little basis to distinguish high- and low-value users. Combining long periods also delays a complete view of recent traffic. Switching goals frequently in response to short-term fluctuations makes comparisons less clear.
This does not rule out purchases forever. It means identifying whether the current issue is recording quality, sparse events or genuinely long purchase delay. Those causes need different remedies and cannot be bypassed with a more sophisticated goal label.
Purchase count and purchase value are different goals
Knowing that a purchase happened can still create an in-app action event; it does not make optimizing event counts technically impossible. Missing amounts mainly restrict value assessment, not all in-app action optimization. Do not conflate count and value goals.
If you want more first-time payers, event counts may be meaningful. If you want higher revenue for the spend, reliable value signals are needed. Google’s guidance for target-return bidding explicitly calls for tracking the value of the in-app actions being optimized.
Values cannot be arbitrary. Sending the same placeholder for every payment hides real differences; duplicate reporting or inconsistent units also distort assessment. Before switching, check completeness, duplication and agreement with real business results, not merely whether the interface displays conversions.
A longer conversion window is not automatically safer
The window should cover typical time to payment while preserving timely feedback. Too short can miss late outcomes; too long delays maturity of recent results. Extending a window does not create real events and is not a reason to wait indefinitely for an unstable goal.
Google’s value-bidding guidance balances revenue coverage against timely feedback. Rather than copying a fixed day count, examine actual install-to-payment timing. Give recent and historical cohorts equal observation opportunities; do not reject an immature cohort by comparing it with a fully observed one.
When moving deeper becomes worth considering
First confirm sufficient, relatively stable target events arrive daily or weekly, not averages propped up by occasional spikes. Verify that events reflect real use or payment and arrive within a reasonable time. For value optimization, real amounts must be recorded and transmitted consistently.
If these conditions are missing, assess a more stable upstream action that represents intent, such as meaningful registration, while continuing to track downstream quality. This is not a mandatory path for every account and does not guarantee that more registrations mean more profit. The goal needs learnable signals, not a new name for a desired business result.
Before switching, record the reason, expected observations and review conditions. Avoid changing budgets, creatives and goals together. Check current official eligibility rules. A diagnosis can clarify the evidence, but an actual goal change still needs renewed confirmation from the account owner.