Blog

Value Bidding for Apps: Meta and Google Setup

Lakshith Dinesh

Lakshith Dinesh

Head of Growth, Linkrunner

Last updated on 7 min read

Value Bidding for Apps: Meta and Google Setup

Short answer: Value bidding tells Meta and Google to find users who will spend more, not just users who will install. To make it work, every purchase event must reach the network with a value and an ISO currency code ("INR" for rupees), and you need enough valued purchases: Meta asks for at least 15 in-app purchases with values in the last 7 days, and Google App campaigns tROAS asks for at least 10 conversions a day from the Firebase SDK. An MMP such as Linkrunner sends confirmed purchases with value and currency to Meta and Google from one event map.

Value bidding rarely fails because the algorithm is weak. It fails because the number it learns from is wrong: a ₹499 purchase arrives as 49,900, a trial start is sent as revenue, or the same purchase lands twice from two SDKs.

This post covers what each platform needs, how to send revenue through your MMP, how to test it, and the mistakes to check first. For step-by-step network setup screens, see our postback setup guide for Meta, Google and TikTok.

What is value bidding for apps?

Value bidding is a bid strategy where the ad network optimises for the total value of conversions (usually purchase revenue) rather than the number of installs or events, using the value you send with each conversion.

Return on ad spend (ROAS): revenue divided by ad spend. Value bidding is how you ask the network to optimise for it directly.

Meta's own example shows the trade-off. On the same budget, optimising for purchase count produced four purchases worth $250, while optimising for value produced three purchases worth $500, per Meta's guide to maximising the value of conversions. The network only knows "higher value" from the numbers you send it. The strategies are:

  • Meta: the "Maximise value of conversions" performance goal in app promotion campaigns, optimising for in-app purchase value or in-app ad impression value, with an optional ROAS goal.
  • Meta Advantage+ app campaigns: the same "Maximise value of conversions" goal, but Meta's Advantage+ app campaign page says the only bid type available is lowest cost and the only optimisation event is purchase.
  • Google App campaigns: target ROAS (tROAS), or Maximise conversions set to conversion value.

What does each platform need before value bidding works?

Both platforms need a valued purchase event from an approved source and a minimum volume of those purchases; Google is stricter about where the event comes from.

RequirementMeta: Maximise value of conversionsGoogle: App campaigns tROAS
Event sourceConversions API, Meta pixel, Facebook SDK or an MMPGoogle Analytics for Firebase SDK; Google Play codeless conversions on Android
What the event carriesA value and a currencyA dynamic revenue value on each event
Minimum volumeAt least 15 in-app purchases with values in the last 7 days (ad revenue apps: 15 ad impressions with at least 2 distinct values in 28 days)At least 10 conversions a day, or 300 in 30 days
Recommended before switchingTest for at least 3 weeks, aiming for 50+ conversions a weekRun target CPA first; 3 to 4 weeks of conversion value history
TimingAccess can take a few weeks after you meet the requirementsSet the first target from a comparable campaign's achieved ROAS

Sources: Meta's requirements page and value optimisation guide; Google's tROAS requirements, App campaign bidding and initial tROAS guidance, all checked November 2026.

  • Google wants Firebase for tROAS. Google's initial-target guidance says to make sure the conversion source is Firebase or Google Play codeless, and that third-party tools may have limitations. An MMP can still send installs and in-app conversions with revenue to Google Ads for reporting and target CPA, so plan to run Firebase alongside it if tROAS is on your roadmap.
  • Meta's window shapes what "value" means. App promotion campaigns offer 1-day, 7-day or 28-day click windows; 28-day is for in-app purchases only and suits apps that earn most revenue after day 7.

Which revenue should you send?

Send the amount the user actually paid for a completed payment, in the currency they paid in, and decide once whether that figure is gross or net.

  • Completed payments only. Fire the purchase when payment is confirmed, never at checkout start or on a failed payment.
  • The real currency code. Meta's developer guide says currency must be a valid ISO 4217 three-letter code. For Indian apps: the rupee amount with "INR", not paise.
  • Gross vs net revenue, consistently. Gross is what the user paid; net removes store fees and taxes such as GST. Either works if you never mix them across platforms or months.
  • Paid events, not trials. A free trial start has no value. The first paid charge and each renewal do. Our guide to attribution for subscription apps covers the event design.
  • In-app purchases and ad revenue are different goals. Meta optimises for them as separate events; pick the one that matches how your app earns.

How do you send revenue to Meta and Google through an MMP?

Your app (or server) reports each completed payment to the MMP with an amount, a currency and a unique payment ID; the MMP attributes it and forwards it as a valued postback to each network you have mapped.

  1. Capture the payment once. Track it from the SDK or, better for subscriptions, from your server once the payment is confirmed. Linkrunner's Revenue Tracking API takes server-side payments, and RevenueCat can be the revenue source, so renewals arrive without the app being open.
  2. Give every transaction a unique payment ID. Linkrunner de-duplicates on the payment ID, so a retry does not double revenue.
  3. Map the event for Meta. In Linkrunner's Meta Ads integration, connect the Conversions API token and dataset, map your payment event to Meta's Purchase, turn on revenue and pick the currency.
  4. Map the event for Google. In the Google Ads integration, add your third-party app analytics link IDs (one each for Android and iOS), map the payment event to a Google conversion action with revenue, then check which actions your campaign goal bids on.
  5. Keep one bid source per event. If Firebase sends the purchase to Google for tROAS, keep the MMP's copy as Secondary.

How Linkrunner handles this: only completed payments count as revenue, and the confirmed purchase goes to Meta and Google with its value and currency. You still choose the bid strategy in each network. Revenue postbacks are included on every plan: 25k one-time free attributed installs, then ₹1.20 down to ₹0.80 per attributed install.

Choosing between delivery methods for the same events? See webhooks vs postbacks vs server-to-server.

How do you test that values arrive correctly?

Make one real purchase on a test device and follow it through your MMP's event log, the network's test view, and the network's reporting a day later.

  • In the MMP. Linkrunner's event and revenue testing guide shows where the payment appears in the Events Log with its amount, payment ID and status. Check ₹499 shows as 499, not 49,900.
  • In Meta. Use Test Events in Events Manager; Linkrunner's docs say events can take up to an hour to appear.
  • In Google. Check the conversion action after a day, and confirm its value setting is not "Don't use a value".
  • Repeat after every app release. Renamed payment fields and dropped events often arrive with an app update, not on launch day.

What are the most common value bidding mistakes?

The costly ones are unit and currency errors, duplicates, mixed gross and net, failed payments counted as revenue, and missing renewals.

MistakeWhat the network learnsFix
Amount sent in paiseUsers are worth 100x more than they areSend the rupee amount with "INR"
No currency code, or the wrong oneValues off by the exchange rateAlways pass the ISO code the user paid in
Gross on Meta, net on GoogleROAS gaps that are really definitionsPick one and document it
Purchase fired at checkout startFailed and cancelled payments look like revenueSend only completed payments
Same purchase from Firebase and MMPDouble revenue, inflated ROASOne Primary bid action per event
Renewals not trackedSubscribers look like one-time buyersSend renewals server-side, through RevenueCat or an API

On refunds: watch refund rates by campaign in your MMP and finance reporting. If one campaign's buyers refund far more often, its value is overstated to the algorithm even when every postback was correct.

Linkrunner support threads argue for checking definitions before hunting for bugs. Across roughly 15 ROAS-mismatch threads from August to early November 2026, most traced to a definition gap: a 7-day click window against 30 days, cohort against in-period revenue, or view-through. Real setup faults, such as a renamed payment field breaking de-duplication or events lost after an app update, were the minority. Our guide on why Meta ROAS and MMP ROAS don't match walks through the comparison.

Two more checks before you switch strategies:

  • Android installs from Meta read as organic. If those users are never attributed to Meta, their purchases may never be credited to the campaign. The Meta Install Referrer fixes much of this on Android.
  • You cannot see which creatives earn the value. Value bidding shifts spend towards ads that attract buyers; track creative-level ROAS to see which ones.

When should you switch to value bidding?

Switch once your valued purchase event clears the platform threshold consistently for several weeks, not on the first good week.

  • Below Meta's 15 purchases a week: optimise for the purchase event (count), or an upstream event such as sign-up, until volume builds.
  • Clearing 15 but under 50 a week: you may be eligible, but Meta's best practice is 50+ a week. Expect a noisy first month.
  • Google: run target CPA on the purchase event until you reach about 10 a day, then move to tROAS with a starting target close to the ROAS you already achieve.
  • Before festive peaks: switch a few weeks ahead so learning does not land on your highest-spend days.

For why install-only signals pull bidding towards cheap users, see why smart bidding optimises the wrong users.

FAQ

How many purchases does Meta need for value optimisation in an app?

At least 15 in-app purchases with values over the last 7 days, sent through the Conversions API, pixel, Facebook SDK or an MMP. Access can take a few weeks after you qualify.

Can I use an MMP instead of Firebase for Google tROAS?

An MMP can send conversions with revenue to Google Ads for reporting and target CPA. Google says App campaign tROAS requires the Firebase SDK, so most teams run both and keep one Primary action per event.

Should I send gross or net revenue?

Either can work. What matters is choosing one, using it on every platform, and not changing it mid-campaign. Net (after store fees and GST) is closer to what you keep; gross is simpler to match against store reports.

How do I send subscription renewals for value bidding?

Track renewals server-side, because the user may not open the app when a renewal charges. A revenue source such as RevenueCat, or a server-side revenue API, sends each renewal to the MMP, which forwards it as a valued event.

The takeaway

Value bidding works when the value is right. Before changing bid strategy, confirm every completed purchase reaches Meta and Google once, in rupees with "INR", on one gross or net definition, renewals included, and that volume clears each threshold for several weeks.

Linkrunner is a mobile and web (beta) attribution platform that sends confirmed purchases with value and currency to Meta and Google from one event map. Integration is the same day for most teams, fully live within a week. If you want to check your current revenue setup before switching to value bidding, request a demo from Linkrunner.

Start measuring the installs your team cares about

Bring attribution, deep links, SKAN, cohorts, and campaign intelligence into one workflow your growth team can trust.