> Site index: https://usehardal.com/llms.txt
> Every content route also serves markdown at <url>.md

# What Is Value-Based Bidding?

Value-based bidding tells an ad platform to bid for conversions worth more, using the value you send with each conversion: revenue, margin, or predicted LTV.

Source: https://usehardal.com/glossary/value-based-bidding

---

Value-based bidding is an automated bid strategy that optimizes for the total value of conversions rather than the count. Each conversion carries a `value` and a `currency`. The ad platform learns which audiences, placements, and queries tend to produce higher values and bids more for them.

The platform only knows the value you send. A wrong value trains it toward the wrong customer.

## How does value-based bidding work?

Three things have to be in place.

1. **A conversion with a value.** A `purchase` event with `value` and `currency`, sent through the browser tag, a conversion API, or an offline import. A conversion without a value counts as one conversion and teaches the platform nothing about worth.
2. **A value bid strategy.** In Google Ads that is Maximize conversion value, or Target ROAS when you set a return goal. In Meta Ads it is the Maximize value of conversions goal, with a ROAS goal when you set a return target. App campaigns have their own ROAS options for purchase and ad revenue.
3. **Enough consistent history.** The platform needs a steady flow of valued conversions before it can tell high-value traffic from low-value traffic. Changing the value definition resets what it learned.

The value can be observed revenue, gross margin, or a forecast such as [predicted LTV](https://usehardal.com/glossary/pltv). Observed revenue is the easiest to audit. A forecast is useful when the real revenue lands weeks after the click, which is common for subscriptions and mobile games.

## A concrete example

An online store sells two products through the same campaign: a $20 accessory and a $400 device.

Under a conversion count goal, both purchases count as one. The platform finds the cheapest buyers, who mostly buy the accessory.

Under value-based bidding, the store sends `purchase` with `value` `400`, `currency` `USD`, and `transaction_id` `order-881` for the device. The accessory sends `value` `20`. The platform now sees that one device buyer is worth twenty accessory buyers and can pay more to reach people who look like the device buyers.

If the device is returned, the store sends a `refund` for `order-881`, or adjusts the conversion value through the platform's adjustment upload. Without that, the platform keeps the $400 as a win.

If the browser pixel and the server both send `order-881`, both copies need the same event ID. See [event deduplication](https://usehardal.com/glossary/event-deduplication). A double-counted order looks like a customer worth twice as much.

## What are the limits?

Value-based bidding cannot see revenue you never send. Ad revenue in a mobile game, renewals in a subscription app, and offline sales all need their own events. See [impression-level ad revenue](https://usehardal.com/glossary/ad-revenue-ilrd).

Inflated values train the platform on revenue that never arrived. Unvalidated in-app purchases, test orders, and values in the wrong unit (micros sent as dollars) all count. Validate store purchases first with [receipt validation](https://usehardal.com/glossary/receipt-validation).

Low volume makes the strategy unstable. A campaign with a handful of valued conversions per week gives the platform little to learn from. Grouping campaigns or using a value goal on a higher-volume event can help.

Setting a ROAS target too high can cut spend sharply, because the platform finds few auctions that meet it.

Sending values server-side does not bypass consent or App Tracking Transparency. The same permission rules apply to the event, whatever value it carries.

## How Hardal handles it

Hardal collects purchase, refund, and ad revenue events from your website, app, and backend, then forwards the `value`, `currency`, and `transaction_id` you allow to [Google Ads](https://usehardal.com/go/google-ads-conversions), Meta, and other destinations through their server-side APIs. One event ID travels with each conversion, so the browser and server copies are counted once.

Hardal does not choose the value for you or build a value model. You decide whether the platform optimizes on revenue, margin, or a forecast. Hardal makes sure the value you chose arrives complete, deduplicated, and with refunds attached. The [MMP revenue signals](https://usehardal.com/blog/mobile-game-mmp-revenue-signals) article covers the mobile game case.

**Related terms:** [Predicted LTV](https://usehardal.com/glossary/pltv), [Event deduplication](https://usehardal.com/glossary/event-deduplication), [Impression-level ad revenue](https://usehardal.com/glossary/ad-revenue-ilrd), [Receipt validation](https://usehardal.com/glossary/receipt-validation)
