App Event Optimization: How to Choose the In-App Event Your Campaigns Bid On

App event optimization is the practice of telling an ad platform which in-app event to bid on, so its delivery algorithm finds users likely to complete that event rather than users who merely install. An optimization event is the single conversion signal a campaign or ad set is trained on, such as an install, a registration, a trial start, a purchase, or a purchase value. A proxy event is an earlier, higher-volume event chosen because it predicts the event you actually care about, usually a paid subscription or revenue, and fires often enough for the algorithm to learn from it.

The choice sounds administrative. It is not. The optimization event decides which users the auction pays for, how fast a campaign exits learning, how much budget it needs, and whether iOS reporting returns any signal at all. Pick an event that is too deep and the campaign starves. Pick one that is too shallow and it buys cheap installs that never pay. This guide explains how Admiral Media chooses, tests, and graduates optimization events across Google App Campaigns, Meta, TikTok, and iOS privacy frameworks, with results from Admiral Media client work and the platform thresholds that constrain every decision.

Why the Optimization Event Matters More Than the Bid

The optimization event matters more than the bid because it defines what the algorithm is trying to buy; the bid only defines how much it may pay. Every modern UA platform runs a predictive model that scores each impression for its probability of producing the chosen event. Change the event and you change the model’s target, which changes the audience the campaign reaches before any bid adjustment takes effect.

Consider a subscription app where only a small share of installers ever pay. An install-optimized campaign rewards the algorithm for finding the cheapest installers in the auction. Those users are, by definition, the ones other advertisers valued least. A purchase-optimized campaign asks a harder question, but it trains on the behavior the business actually monetizes. Between those two poles sit registrations, onboarding completion, trial starts, and custom engagement events, and the right answer depends on volume, correlation with revenue, and measurement lag.

In Admiral Media’s campaigns across subscription, dating, fintech, mobility, and health apps, the optimization event is one of the first levers the team audits when a new account is onboarded. Based on our work managing over €500M in mobile ad spend for 150+ mobile brands, a misaligned event is among the most common reasons an account plateaus: the creative is fine, the budget is fine, but the algorithm is being paid to find the wrong people.

Three optimization modes every UA manager uses

All major platforms offer some version of the same three modes. They differ in naming and thresholds, not in logic.

• Install optimization: the algorithm targets users likely to install. Highest volume, fastest learning, weakest link to revenue.
• Action optimization: the algorithm targets users likely to complete a specific in-app event, bid on a cost-per-action basis (tCPA on Google, App Event Optimization on Meta and TikTok).
• Value optimization: the algorithm targets users likely to generate the most revenue, bid on a return basis (tROAS on Google, value optimization on Meta, Value-Based Optimization on TikTok).

The Constraint That Decides Everything: Event Volume

Event volume is the binding constraint because a delivery model cannot learn a pattern it rarely sees. Each platform publishes guidance on how frequently an event must fire before it is a viable optimization target, and those thresholds should be the first filter on any shortlist of candidate events.

Google is the most explicit. Its App campaigns best practices guide advises picking an in-app action that is completed by at least 10 different users per day in the campaign, setting a daily budget of at least 10 times the target CPA for action-optimized campaigns, and a daily budget of at least 50 times the target CPI for install-volume campaigns. Google’s guidance on setting up App campaigns by goal adds that if fewer than 10 different users complete the most valuable in-app action every day, you should pick a more common in-app action instead, and that you should allow 7 to 14 days for the system to stabilize after significant changes.

TikTok frames it through the learning phase. Its Value-Based Optimization tips for app campaigns state that achieving 50 conversions is the most significant indicator of passing the learning phase, recommend a minimum of 7 days for learning, and suggest a daily budget of 30 times the CPA or 3 times a manual campaign budget. TikTok’s App Event Optimization best practices also note that iOS 14.5+ AEO campaigns should return at least 90 daily app installs to avoid SKAdNetwork privacy thresholds withholding conversion data.

Meta works on the same principle: an ad set leaves the learning phase only after it has collected enough optimization events within a rolling week, and ad sets that cannot reach that volume are flagged as learning limited. The practical consequence is identical across platforms. The deeper the event, the fewer times it fires, and the more budget each campaign needs before the algorithm has enough examples to work with.

Correlation and Lag: The Two Tests Every Candidate Event Must Pass

A good optimization event must fire often enough to train on, correlate strongly with revenue, and happen soon enough after install to be attributed. Volume is the first test; correlation and lag are the two that most accounts skip.

Correlation with monetization

A proxy event is only useful if users who complete it are meaningfully more likely to pay than users who do not. “Tutorial completed” is a poor proxy if almost everyone completes the tutorial. “Added a second goal” might be an excellent proxy for a fitness subscription if it separates committed users from browsers. The question to ask of your product analytics is simple: among users who completed this event in their first day, what share converted to paid, compared with users who did not? The wider that gap, the more predictive information the event carries.

This is where product knowledge beats platform defaults. Admiral Media’s work with Clark, the German insurance app, is a clear illustration. The Admiral Media team ran Facebook Ads in Germany and optimized not only for leads and installs but for a middle-funnel event, “level achieved”. The case study notes that it sometimes helps to optimize for events that stand on the sideline of the standard funnel. Comparing month 3 with month 1, cost per lead fell 50%, conversion rate rose 41%, CPI fell 29%, installs rose 18%, the count of levels achieved rose 13%, and cost per level achieved fell 47%.

Lag between install and event

Lag matters for two reasons. First, platforms attribute and learn within finite windows, so an event that typically happens on day 9 contributes little to a model that weighs early post-install signals. Second, on iOS the privacy frameworks impose their own timing. Under SKAdNetwork and Apple’s AdAttributionKit, conversion values are sent in postbacks tied to conversion windows, which means the event you encode must happen inside those windows to be reported at all. A trial start on day 0 is measurable; a trial-to-paid conversion after a seven-day trial needs a later window and arrives with less granularity.

The practical rule Admiral Media applies: the shorter the lag, the more weight an event can carry in the bid. Long-lag events are better used as validation metrics in cohort reporting than as direct optimization targets, unless the platform offers a value model that can predict them from early behavior. For the full mechanics of encoding events into iOS postbacks, see the Admiral Media guide to SKAdNetwork conversion values.

The Admiral Media Event Ladder Framework

The Admiral Media Event Ladder Framework is a seven-step method for choosing an optimization event that the algorithm can learn from today, and graduating to deeper, more valuable events as data accumulates. It treats the optimization event as a rung on a ladder, not a permanent setting.

The Admiral Media Event Ladder Framework

1. Map the monetization path. List every event between install and revenue: registration, onboarding milestones, paywall view, trial start, first purchase, renewal. Note the typical time from install to each one. This is the ladder.
2. Measure correlation with revenue. For each rung, compare the paid conversion rate of users who completed it in their first day against users who did not. Discard events that nearly everyone completes or that show little separation.
3. Apply the volume gate. Estimate how many times each surviving event will fire per campaign per day at the planned budget. Check it against the platform thresholds above, for example Google’s guidance of at least 10 different users per day for in-app actions. The deepest event that clears the gate is the starting rung.
4. Check the measurement path. Confirm the event is sent reliably through the SDK or MMP to every platform, deduplicated, and timestamped correctly. On iOS, confirm it fits inside the conversion value schema and the earliest postback window.
5. Launch on the starting rung with clean structure. Concentrate budget in as few campaigns or ad sets as possible so each accumulates events quickly. Give the platform its full learning period, 7 to 14 days on Google per its own guidance, before judging performance.
6. Graduate when the next rung clears the gate. When the deeper event starts firing at threshold volume, test it in a parallel campaign rather than switching the live one. Move from install to action, then from action to value, only when data supports it.
7. Re-validate quarterly. Product changes alter correlations. A new onboarding flow, paywall, or pricing test can turn a strong proxy into a weak one. Re-run step 2 whenever the funnel changes and at least once a quarter.

The framework reflects a principle that runs through Admiral Media’s work: the right optimization event is the deepest one the algorithm can actually learn from at the current budget. Not the deepest one in theory. Not the cheapest one in the dashboard.

Climbing the Ladder in Practice: Install to Sign-Up at TIER

Graduating from install optimization to a deeper event works best when the account first builds enough data to support it. Admiral Media’s work with TIER, the European e-scooter operator, followed exactly that sequence.

Admiral Media expanded TIER’s user acquisition from Facebook to Google and Snapchat, built a creative database with ad copy in 8 languages, and, in the words of the case study, “started with install optimization and moved down the funnel to sign-up optimization once we got enough learnings and enough data within the account.” The engagement delivered +297% new customers, 2 new channels, and 5x budget scaling in less than 3 months, while the team adjusted strategy and budget allocation through the iOS 14 rollout.

The lesson is about sequencing. Starting on sign-up optimization with an empty account would have forced the algorithm to learn from a handful of events per day. Starting on installs built volume, gave the team creative and audience learnings, and created the event history needed for sign-up optimization to work when it was switched on.

Choosing Between Action and Value Optimization

Value optimization outperforms action optimization when revenue per user varies widely and purchase events are frequent enough to train on; action optimization wins when most payers are worth roughly the same or when purchase data is sparse. The decision is not a matter of sophistication. It depends on the shape of your revenue distribution.

If every subscriber pays the same monthly price, a tCPA campaign on “subscription started” already captures most of the value signal, because one subscriber is worth about the same as another. If the app sells weekly, monthly, and annual plans, consumables, or tiered bundles, a user who buys an annual plan can be worth many times more than one who buys a week. In that case tROAS or value optimization lets the algorithm pay more for users predicted to buy the expensive option, which a flat CPA bid cannot express.

Admiral Media’s work with ChatPDF shows how this choice is made with tests rather than assumptions. Admiral Media restructured ChatPDF’s Google and Meta accounts, eliminating overlaps and consolidating ad sets, ran weekly creative concept tests with three variants per winner, and tested target CPA versus target ROAS bidding with value rules and an LTV signal added. Comparing year 1 with year 2 year to date on an indexed baseline, ChatPDF achieved +320% ROAS, +156% subscriptions, and -42% CAC overall.

The channel split is worth noting. On Google Ads, ChatPDF’s ROAS grew 320% with subscriptions up 142% and CAC down 38%. On Meta, ROAS grew 280% with subscriptions up 171% and CAC down 45%. Bidding strategy was one of several levers, alongside account consolidation and creative testing, which is typical: event and bid choices compound with structure and creative rather than replacing them.

When value optimization struggles

Value models need accurate, timely revenue values. They tend to struggle in three situations, based on observed patterns in accounts Admiral Media manages:

• Sparse purchases: when only a few purchases fire per day, the model has too few value examples and bids erratically.
• Delayed value: when most revenue arrives after a free trial converts days later, the early signal the model sees is mostly zero.
• Distorted values: when revenue is sent gross of refunds or store fees inconsistently, or when trial starts are sent with a placeholder value, the model optimizes toward noise.

In those cases, a hybrid approach often works better: keep action optimization on a high-correlation event such as trial start, and use value rules or predicted LTV values to steer it, which is the direction Admiral Media tested with ChatPDF. For the predictive side of this approach, see the Admiral Media guide to predictive LTV bidding.

Testing Event Combinations: The FET Example

Optimization events should be tested like creatives, because the event that looks right on a whiteboard is not always the one that performs. Admiral Media’s work with FET, a dating app, put that into practice.

Admiral Media ran optimization event tests to find, in the case study’s words, “the right event combo to align campaigns with true monetization drivers.” The team also performed SKAN remapping and rebuilt FET’s iOS conversion setup from scratch, which turned iOS into a profitable channel and balanced spend across platforms, and tested more than 60 ad iterations across 9 unique concepts. The result: +181% conversion rate, -66% cost per subscription, and +162% subscriptions.

Two details make this example useful. First, the event test and the iOS rebuild were inseparable: on iOS, the optimization event is only as good as the conversion value mapping that reports it. Second, the creative volume mattered. Event optimization narrows the audience the algorithm pursues, so it needs a steady supply of creative to avoid fatigue within that narrower pool.

How to Run an Optimization Event Test

An optimization event test compares two campaigns that are identical except for the event they bid on, and judges them on a downstream business metric rather than the platform’s own cost per event. Comparing cost per event across different events is meaningless, because a cheaper trial start is not better than a more expensive purchase.

1. Define the arbiter metric first. Pick the metric both arms will be judged on, typically cost per paying user or day-7 ROAS from your MMP or backend, not the in-platform event cost.
2. Hold everything else constant. Same creatives, geos, audiences, budget, and bid strategy family. Change only the event.
3. Split budget evenly and give both arms a full learning period. On Google that means 7 to 14 days of stable settings; on TikTok at least 7 days.
4. Read results on cohorts, not dates. Compare install cohorts from the same period, measured at the same age, so the deeper event is not penalized for slower revenue.
5. Check for audience overlap. Two campaigns from the same app in the same geo can bid against each other. Where possible, use platform experiment tools or geo splits to keep arms clean.
6. Decide with a margin. If the arms land close together, prefer the event with more volume, because it will scale more easily.

Platform-by-Platform Guidance

Each platform implements optimization events differently, so the same event strategy must be adapted to each one’s bidding options, data paths, and documented thresholds. The table summarizes the sourced thresholds and the implementation notes Admiral Media applies.

Google App Campaigns

Google App Campaigns optimize on a single selected in-app action or its value, so event choice is concentrated in one setting with large consequences. Google’s own guidance favors one frequent action over several rare ones, which matches Admiral Media’s experience: combining multiple low-volume actions often dilutes the signal rather than strengthening it. When the deepest valuable action does not reach Google’s threshold of 10 different users per day, pick the more common action and let a value or LTV signal do the refinement.

The same logic applies to web-to-app campaigns on Google Search. Admiral Media’s work with Miles Mobility, the car-sharing service operating in Germany and Belgium, aligned web-to-app Search campaigns with Google’s Smart Bidding, added broad match keywords, applied dynamic keyword insertion, and implemented an MMP solution for better conversion tracking. The result was 260% more conversions at a 25% lower CPA. Smart Bidding can only optimize toward conversions it can see, so the measurement fix was a precondition for the bidding gain.

Meta

Meta’s app campaigns let advertisers choose between installs, app events, and value, and its delivery system needs consistent weekly event volume per ad set to exit learning. Fragmented account structures are the most common reason event optimization fails on Meta: ten ad sets each collecting a handful of purchase events will stay in learning, while two consolidated ad sets collecting the same total can exit it. That is why consolidation featured in the ChatPDF work above.

TikTok

TikTok offers App Event Optimization and Value-Based Optimization with explicit learning guidance, and its iOS campaigns carry a specific volume floor. The documented recommendation that iOS 14.5+ AEO campaigns return at least 90 daily installs means that on iOS, budget concentration is not optional. Small iOS AEO campaigns risk losing conversion data to SKAdNetwork privacy thresholds entirely, which leaves the algorithm optimizing blind.

iOS: SKAdNetwork and AdAttributionKit

On iOS, the optimization event must survive the trip through Apple’s privacy frameworks, so event strategy and conversion value mapping are a single decision. Apple’s frameworks report conversions through postbacks with limited granularity and privacy thresholds, so an event that is not encoded in the conversion value schema effectively does not exist for iOS optimization. The FET example shows the payoff of getting this right.

Choosing a Proxy Event: A Scoring Matrix

A proxy event should be chosen by scoring candidates on volume, correlation, lag, and measurement reliability, then picking the highest combined score that clears the platform’s volume gate. The matrix below is the decision template the Admiral Media team uses with clients. It contains decision criteria rather than measured values, because the scores must come from each app’s own analytics.

Common Mistakes in App Event Optimization

Most event optimization failures come from four avoidable mistakes: choosing events too deep for the budget, switching events too often, measuring tests on the wrong metric, and ignoring iOS encoding. In Admiral Media’s account audits, these patterns recur across categories.

• Optimizing for the “real” goal from day one. Bidding on purchases with a budget that produces a few purchases a day keeps the campaign permanently in learning. Start lower on the ladder.
• Resetting learning repeatedly. Changing the optimization event restarts learning. Swapping events every few days because early numbers look noisy guarantees the campaign never stabilizes. Test new events in parallel campaigns instead.
• Judging by in-platform cost per event. A campaign optimized for registrations will always show a cheaper cost per event than one optimized for purchases. That comparison says nothing about which one makes money.
• Sending events inconsistently. Duplicate events, client-side and server-side double counting, or events missing on one platform make the model learn from corrupted data.
• Never revisiting the choice. A proxy event chosen a year ago may no longer predict revenue after paywall, pricing, or onboarding changes.

Diagnosing a Struggling Event-Optimized Campaign

When an event-optimized campaign underperforms, the symptom usually points to whether the problem is volume, correlation, or measurement. The table maps common symptoms to likely causes and first actions.

How Event Optimization Fits the Wider Growth System

App event optimization is one lever in a system that also includes creative, account structure, measurement, and product. It amplifies good inputs and cannot rescue bad ones.

The case studies in this guide make that clear. ChatPDF’s gains came from bidding tests, consolidation, and weekly creative testing together. FET’s came from event tests, iOS rebuild, and 60+ creative iterations. TIER’s came from channel expansion and creative localization as much as from moving to sign-up optimization. Admiral Media’s work with NeuroNation, the brain training app, is another reminder: between January and August 2019, intensive creative testing and channel exploration, prioritized with Admiral Media’s pRank methodology, delivered +117% ROAS, -39% CPI, +66% installs, +32% purchases, and +42% net cohort revenue. The event the algorithm bids on determines where it looks; creative determines whether the right users respond when it finds them.

The event decision also connects to how you value users. If you know what a cohort is worth, you know how deep an event you can afford to buy and what target to set.

Frequently Asked Questions

What is app event optimization?

App event optimization is a bidding approach in which an ad platform targets users likely to complete a specific in-app event, such as a registration, trial start, or purchase, instead of users likely to install. The advertiser sends in-app events to the platform through an SDK or mobile measurement partner, then selects one as the campaign’s optimization event. The platform’s model then scores each impression for the probability of that event. It is offered under different names on Meta, TikTok, and Google App Campaigns.

Should I optimize my app campaigns for installs or purchases?

Optimize for the deepest event that fires often enough for the platform to learn from at your current budget. If purchases are rare, purchase optimization will keep campaigns stuck in learning, so start with installs or a high-correlation proxy event and graduate later. Google, for example, advises picking an in-app action that at least 10 different users complete per day in the campaign. Admiral Media typically tests a deeper event in a parallel campaign once it reaches that kind of volume.

What is a good proxy event for a subscription app?

A good proxy event fires early after install, fires often, and separates future payers from non-payers. Common candidates are trial start, paywall view, registration, or a key onboarding milestone. The right choice comes from your own data: compare the paid conversion rate of users who completed the event on day one with those who did not. Choose the candidate with the widest gap that still clears the platform’s volume threshold.

How long should I wait before judging a new optimization event?

Wait until the campaign has completed its learning period with stable settings. Google recommends allowing 7 to 14 days for App campaigns to stabilize after significant changes, and TikTok recommends at least 7 days for learning in Value-Based Optimization campaigns. Judge the result on install cohorts of the same age using a downstream metric such as cost per paying user or day-7 ROAS. Changing the event again before learning completes resets the process.

When should I switch from tCPA to tROAS?

Switch when users differ widely in value and revenue events fire often enough to give the model reliable value data. If most payers are worth roughly the same, tCPA on a purchase or trial event already captures most of the signal. If plan mix or purchase size varies a lot, tROAS lets the algorithm bid more for high-value users. Test the switch in a parallel campaign rather than changing the live one.

Why does event optimization perform worse on iOS?

On iOS, conversion data is reported through Apple’s SKAdNetwork and AdAttributionKit frameworks, which use conversion values, postback windows, and privacy thresholds. If the optimization event is not encoded in the conversion value schema, or if campaigns are too small to clear privacy thresholds, the platform receives little or no event data. TikTok, for instance, recommends that iOS 14.5+ AEO campaigns return at least 90 daily installs. Mapping events correctly and concentrating iOS budget usually close much of the gap.

Can I optimize for more than one in-app event at once?

Each campaign or ad set generally optimizes for one event, and spreading the signal across several rare events tends to weaken learning. Google’s App campaign guidance recommends a single, frequently occurring in-app action. The usual approach is to run separate campaigns for different events, or to use value optimization so that multiple purchase types are expressed as one revenue signal. Event combinations are best validated with structured tests, as Admiral Media did with FET.