Value-Based Optimization (VBO, sometimes called VBB for value-based bidding) is a class of ad-platform bidding strategies that optimize toward predicted user value rather than just install count. Where install-count bidding asks the algorithm to maximize the number of installs at a given cost, VBO asks it to maximize the total value (revenue, predicted LTV, ROAS) those installs will generate.
Major VBO implementations in 2026
- Meta Advantage+ Value Optimization — Meta's automated bidding for value events. Requires conversion-value events flowing back via Conversions API or Meta SDK.
- TikTok VBB (Value-Based Bidding) — TikTok's equivalent for in-stream UA campaigns.
- Google tROAS for Apps — Target ROAS bidding for Google App Campaigns. The user specifies a target ROAS percentage; Google bids to hit it.
- AppLovin / Liftoff value bidding — value-event-driven bidding in in-app exchanges.
All major SANs and many programmatic DSPs now offer some form of value-based bidding.
Why VBO outperforms install-count bidding
- Naturally surfaces high-LTV users — instead of competing for any install at the cheapest price, the network competes for installs likely to generate the most value.
- Self-tunes to your unit economics — if your high-LTV users are concentrated in specific demographics / interests, VBO finds them. You don't have to manually segment.
- Compounds with creative quality — VBO + high-IPM creatives generate the strongest performance compounding.
- Better post-ATT performance on iOS — VBO works well with SKAN conversion-value signals (the conversion value IS the user-value proxy).
What you need to feed VBO
- Reliable conversion-value events — every IAP, subscription start, key milestone fired back to the network with revenue or pLTV score.
- Server-side firing where possible — Meta Conversions API, TikTok Events API, Google's enhanced conversions. More reliable than client-side SDK events.
- Sufficient event volume — VBO needs ~50+ value events per week per ad set to learn well. Below that threshold, the optimization signal is too sparse.
- Consistent value encoding — same currency, same value definition, no schema changes mid-campaign.
- For pLTV: a model that scores users within hours of install + a pipeline to fire those scores to the ad network.
VBO often takes 2-4 weeks of learning to outperform install-count bidding — the network needs time to learn which value-generating users look like in your specific app.
When VBO doesn't work well
- Low-volume campaigns — under 50+ value events per week per ad set, optimization signal is too sparse.
- Apps with weak revenue events — if conversions are rare or unpredictable, VBO struggles to find a signal.
- Very new programs — VBO needs historical signal to learn patterns. Brand-new programs may start with install-count bidding and graduate to VBO at 3-6 months.
- Apps with poor server-side event wiring — VBO requires reliable event delivery. Apps with broken event pipes get worse results than basic install bidding.