How do you set a mobile UA budget?

Setting a mobile UA budget isn't about guessing what feels right, it's about working backwards from your unit economics and growth goals. At RocketShip HQ, we've helped apps allocate over $100M in ad spend by connecting budget decisions to LTV, CAC, and payback period targets. Here's how to build a budget framework that scales.

Page Contents

What's the best way to determine your total mobile UA budget?

Start with one of three frameworks: percentage of projected revenue (typically 10-30% for early stage, 5-15% for mature apps), target CPI multiplied by your volume goals, or payback period method (how quickly acquisition costs convert to profit). Most successful apps we work with use a hybrid approach.

The percentage of revenue method works well once you have predictable LTV, but it assumes stable unit economics. Target CPI times volume is better for growth-stage apps chasing specific install goals. Payback period (usually 3-12 months) is the safest for conservative budgeting because it ties spend directly to when you actually recoup costs.

Percentage of revenue: 10-30% for early stage, 5-15% for mature apps
Target CPI method: Best when you know exact install goals and CAC limits
Payback period: 3-12 months typical range, ties spend to actual profitability

How do I calculate my sustainable CPI if I don't know my LTV yet?

Use a blended payback period approach: estimate your day-7 ARPPU, multiply by your retention rate, then divide by your target payback period (usually 90 days). For example, if day-7 ARPPU is $3 and 60% of users stay, your sustainable CPI is roughly $1.80 at 90-day payback.

This isn't perfect, but it's more defensible than just guessing. As you collect more data, refine this quarterly. Early stage apps often aim for 60-180 day payback periods, while monetized apps target 30-90 days.

Formula: (Day-7 ARPPU × Retention Rate) / Target Payback Days
Adjust payback period based on unit economics (longer for lower monetization)
Revisit this quarterly as retention and monetization data improves

How should I split my budget across different channels?

Allocate based on channel efficiency and volume capacity, not equally. Start with 40-50% to your most efficient channel, 30-40% to your second best performer, and test 10-20% on emerging channels. Monitor ROAS weekly and rebalance monthly.

Most apps find that 1-2 channels drive 60-80% of their profitable volume. The temptation to spread budget thin across all channels usually kills profitability. Instead, let winners fund experiments.

Channel allocation by app maturity

Early stage apps should concentrate 60% on one or two proven channels (usually TikTok, Instagram, or Google App Campaigns) while testing 20-30% on secondary channels. Growth stage apps can typically support 3-4 channels at scale. Mature apps should shift 50%+ to owned channels and predictive lookalikes.

Testing budget allocation

Reserve 10-15% of your monthly budget for testing new channels, creative angles, or audiences. But only increase a test channel's budget by 50-100% per week, not overnight. A channel that works at $2K/day might not work at $20K/day.

When should I scale my UA budget and when should I pull back?

Scale when ROAS stays above 3x for 2+ consecutive weeks and you still have unmet volume goals. Pull back when ROAS drops below 2x or your payback period extends beyond your target. Most apps should scale in 50-100% increments, not double overnight.

The biggest mistake is scaling too fast. We've seen apps go from profitable at $50K/month to unprofitable at $150K/month because they ignored diminishing returns. Set hard ROAS thresholds before scaling, not after.

Scale: ROAS above 3x for 2+ weeks AND volume goals not met
Pull back: ROAS below 2x or payback period exceeds target
Speed: Increase budget by 50-100% per week, measure for 7-14 days before next increase
Reserve emergency funds: Always hold 10-20% of monthly budget to capitalize on sudden opportunities

How do I handle budget allocation when channels have different payback periods?

Weight your allocation toward channels with shorter payback periods early on, then increase allocation to longer-payback channels as cash flow stabilizes. For example, allocate 60% to 30-day payback channels and 40% to 90-day payback channels if you have healthy reserves.

This matters most for apps with mixed monetization models (ads plus IAP). Ads typically have faster payback, IAP slower. As we've seen at RocketShip HQ, apps that balance this well maintain steady month-over-month growth while building long-term value.

Cash flow considerations

If you have less than 6 months of operating runway, prioritize faster payback channels. If you have 12+ months, you can afford more allocation to high-LTV, slow-payback channels.

What's a realistic UA budget for different app categories?

Gaming apps typically spend $200K-$5M per month at scale, productivity apps $50K-$500K, and dating/social apps $100K-$2M. But category matters less than your unit economics. A casual game with 20% day-1 retention might need $100K/month while a utility app with 60% retention could spend $5K/month profitably.

Budget size should track to LTV and competition level, not category. Hypercasual games compete intensely on user acquisition, so they spend aggressively. Niche productivity apps might reach profitability with minimal spend because competition is lighter.

Gaming: $200K-$5M/month at scale, highly competitive
Productivity/Utility: $50K-$500K/month, variable competition
Dating/Social: $100K-$2M/month, depends on monetization model
Your budget should match your LTV and payback period, not category averages

How do I adjust my budget if my LTV assumptions were wrong?

If actual LTV is 20%+ lower than projected, cut your sustainable CPI target by the same percentage and reduce budget allocation proportionally. Recalculate weekly for the first month, then monthly once data stabilizes. Don't wait for quarterly reviews to make cuts.

This is where many apps fail. They set a budget based on optimistic LTV projections, then refuse to adjust when reality is bleaker. If you projected $10 LTV and you're seeing $6, your sustainable CPI drops from $3 to $1.80. Adjust immediately.

LTV validation timeline

You need at least 1,000 paying users and 30 days of monetization data to validate LTV meaningfully. Until then, use conservative estimates and be prepared to cut budget by 20-30% if early cohorts underperform projections.

Should I budget differently for user acquisition versus retention and monetization?

Yes. Most successful apps allocate 60-70% of marketing budget to UA, 20-25% to retention (push notifications, email, in-app offers), and 5-10% to monetization optimization. But if your retention drops, shift budget back to retention immediately before scaling UA further.

This is counterintuitive for growth teams focused on installs. But a 10% improvement in day-30 retention often delivers more profit than a 30% increase in UA spend. At RocketShip HQ, we've seen apps recover 3-5x ROI improvements by rebalancing toward retention when acquisition saturation hits.

Typical allocation: 60-70% UA, 20-25% retention, 5-10% monetization optimization
If retention drops 5%+ month over month, pause UA scaling and invest in retention
Test retention channels with 10-15% of budget before scaling; ROI often exceeds UA

What budget monitoring cadence should I use to stay on track?

Check daily spend versus daily targets and ROAS daily, review channel allocation weekly, and do a full budget reconciliation and forecast update monthly. Never wait more than 7 days to catch a budget miss or ROAS drop.

Real-time monitoring is non-negotiable at scale. Apps spending $50K+ monthly should have dashboards showing daily spend, ROAS, and payback period by channel. A single underperforming week can cascade into a 20-30% budget overrun if you're not watching.

KPIs to monitor daily

Daily spend vs. daily target (±10% acceptable), daily ROAS by channel, daily install volume, and daily payback period. Flag deviations immediately.

Monthly budget review checklist

Compare actual spend to planned budget, analyze ROAS trend, reforecast next month's budget based on payback performance, and plan any scaling or reductions. Update LTV assumptions if new cohort data warrants it.

Your mobile UA budget should be data-driven and dynamic, not set-and-forget. Start with a payback period or CPI-based framework, allocate conservatively across channels, and adjust weekly as ROAS and retention data arrive. The apps that scale fastest are the ones that treat budget management as an ongoing optimization, not a quarterly exercise.