Value-based bidding on Meta works differently from Google in one critical way: the signal infrastructure. Google receives conversion values through direct tag firing and Offline Conversion Import. Meta's system is built around the Conversions API (CAPI): a server-to-server connection that sends purchase events and their values directly from your server to Meta's systems, bypassing browser-based pixel tracking entirely. Understanding this distinction is the first step in setting up value optimisation that actually works.The reason CAPI matters so much on Meta is signal completeness. iOS 14+ tracking restrictions and ad blocker interference mean browser pixel events miss 15 to 30% of purchase events for most DTC advertisers. Meta's Conversions API best practices documentation confirms that server-side events are more reliable and produce higher Event Match Quality scores: the metric that determines how well Meta's algorithm can attribute conversions back to your ads. Without a solid CAPI setup, value-based optimisation is working with incomplete data from day one.
This guide covers how Meta's value optimisation feature works, the two bid strategies that activate it, the CAPI prerequisites required to make it reliable, and the practical setup sequence for a DTC brand moving from standard conversion campaigns to a full value-based setup. References throughout link directly to Meta's official documentation for each step.
In This Article
- 1How Meta's Value Optimisation Works
- 2Why CAPI Is the Foundation, Not an Optional Enhancement
- 3Highest Value vs ROAS Goal: The Two Bid Strategies
- 4The Signal Flow: From Purchase to Meta's Algorithm
- 5Setting Up Value Optimisation: The Correct Sequence
- 6Event Match Quality: The Number That Determines Signal Strength
- 7Value Optimisation With Advantage+ Sales Campaigns
- 8Common Configuration Mistakes
- 9Further Reading
How Meta's Value Optimisation Works
Meta's value optimisation is an ad delivery feature that tells the algorithm to optimise for purchase value rather than purchase count. Under standard conversion optimisation, Meta finds the people most likely to buy. Under value optimisation, it finds the people most likely to spend the most. The algorithm uses purchase values passed in your conversion events to learn which audience characteristics correlate with higher-revenue buyers, then weights delivery and bidding accordingly.
To activate value optimisation, Meta requires value sets: a minimum of four distinct purchase value ranges defined in Events Manager. These ranges allow Meta to bucket conversions by value tier and weight them in the optimisation model. For most DTC brands, this step is straightforward: you enable value optimisation in Events Manager, Meta auto-generates four value ranges based on your historical purchase data, and the system begins learning.
The two conversion value tracking prerequisites are: first, your purchase events must include a `value` parameter on every transaction, and second, those events must be firing consistently via CAPI or a working pixel. Meta cannot run value optimisation on purchase events that are missing value data or arriving only sporadically.
Why CAPI Is the Foundation, Not an Optional Enhancement
Browser pixel alone is no longer sufficient for reliable value optimisation on Meta. The Conversions API was designed specifically to address the tracking gaps that browser-based measurement cannot solve: iOS 14+ privacy restrictions, ad blocker interference, and the 7-day attribution window that truncates late-converting purchase data.
When a pixel event is blocked or lost, Meta receives no value data for that conversion. When a CAPI event fires, it arrives server-side regardless of what is happening in the user's browser. Meta's own best practices documentation recommends running both CAPI and pixel simultaneously with deduplication enabled: the redundancy ensures that if one signal pathway fails, the other captures the event. The result is higher Event Match Quality and a more complete dataset for value optimisation to learn from.
Meta offers three CAPI setup options: the Conversions API Gateway (code-free, configured in Events Manager), partner integrations through platforms like Shopify, and direct code integration for custom implementations. For most DTC brands on Shopify, the partner integration route is fastest: setup takes under an hour and does not require a developer. The signal engineering fundamentals article covers the full technical architecture for brands building a custom stack.
CAPI Without Deduplication Creates Double-Reporting
Running CAPI alongside the pixel requires deduplication: a shared event_id passed in both the browser and server events so Meta can identify and discard duplicates. Without this, Meta counts the same purchase twice, inflating conversion numbers and distorting the value signals the algorithm learns from. Meta's deduplication setup is covered in the CAPI implementation documentation.
Highest Value vs ROAS Goal: The Two Bid Strategies
Once value optimisation is active and purchase values are flowing, you choose between two bid strategies: Highest Value and ROAS Goal. They share the same underlying optimisation objective: find buyers who spend more: but impose different constraints on delivery.
Highest Value tells Meta to spend your full budget while maximising the purchase values it acquires. There is no floor on ROAS: Meta will enter any auction where it predicts a high-value purchase, regardless of whether the overall return meets a specific target. This strategy is the correct starting point for accounts new to value optimisation: it builds learning history without the constraint of a ROAS target that the algorithm has not yet calibrated to.
ROAS Goal (Meta's minimum ROAS bid strategy) adds a profitability floor. You set a minimum return: for example 2.5, meaning $2.50 in purchase value for every $1 spent: and Meta only enters auctions where it predicts that return can be achieved. As Meta's documentation notes, if the ROAS Goal is set too high for available auction inventory to meet, delivery may stop entirely and your budget will go unspent. Set initial ROAS Goal targets conservatively: at or slightly below your Highest Value historical ROAS.
The Signal Flow: From Purchase to Meta's Algorithm
Understanding the exact path a purchase value takes from your website to Meta's bidding model makes it clear where setup failures happen and how to prevent them.
The value parameter is the most critical field in the CAPI purchase event. It is this number that Meta's algorithm uses to weight the event in its learning model. A purchase event without a value field contributes nothing to value optimisation: Meta cannot use it to learn which audiences produce high-revenue buyers. Every purchase event sent via CAPI must include: `event_name: Purchase`, `value` (the transaction amount), `currency`, `event_id` (for deduplication), and as much customer information as available: `em` (hashed email), `ph` (hashed phone), `fn` / `ln` (first and last name). More customer information parameters improve Event Match Quality, which improves attribution accuracy, which strengthens the value signals the algorithm learns from.
Setting Up Value Optimisation: The Correct Sequence
Verify purchase events include value data
In Meta Events Manager, navigate to your Pixel or dataset and check the Purchase event details. Every event should show a non-zero, varied value in the value field. If all events show the same value or zero, your pixel or CAPI implementation is not passing dynamic purchase values. Fix this before enabling value optimisation: the algorithm cannot learn from uniform or missing value data.
Set up or verify CAPI alongside your pixel
Use Meta's CAPI Gateway in Events Manager for a code-free setup, or connect through your Shopify/platform integration. Run CAPI and pixel in parallel with deduplication via shared event_id values. Aim for an Event Match Quality score of Good (6–7.9) or Great (8–10). Low EMQ means events are not matching to Meta accounts reliably, which reduces attribution and weakens value signals. Meta's setup comparison guide covers all three implementation paths.
Enable value optimisation and configure value sets in Events Manager
Navigate to Events Manager → your dataset → Settings → Value Optimisation. Enable it for your Purchase event. Meta will auto-generate a minimum of four value ranges. You can configure up to eight ranges for finer granularity: each range counts toward your domain's event slot limit (eight events maximum per domain). Review the generated ranges to ensure they reflect your actual order value distribution.
Create a campaign using Highest Value bid strategy
In Ads Manager, create a Sales campaign, select Purchase as the conversion event, and choose Highest Value as the bid strategy. Do not set a ROAS Goal at this stage. Run for a minimum of four weeks with consistent budget. The algorithm needs sufficient purchase volume to calibrate its value predictions. Set a review date at week 5: do not evaluate performance or make changes during the learning period.
Introduce ROAS Goal after 4 to 6 weeks of stable Highest Value performance
Calculate your actual ROAS from the Highest Value phase (Purchase value / spend). Set your initial ROAS Goal at or slightly below this baseline: Meta recommends starting conservatively to avoid delivery stopping entirely. Raise the ROAS Goal gradually in 10 to 15% increments as performance stabilises. According to Meta's documentation, if your ROAS Goal cannot be met in available auctions, delivery will pause and budget will go unspent.
Event Match Quality: The Number That Determines Signal Strength
Event Match Quality (EMQ) is Meta's measure of how well your conversion events can be matched back to a Meta account. A higher EMQ means more of your purchase events are successfully attributed to specific users, which gives the algorithm a larger and more accurate dataset to learn from. Meta's best practices documentation recommends targeting a Good or Great EMQ score before relying on value optimisation.
EMQ is calculated from the customer information parameters included in your events. The parameters with the highest impact are hashed email (em) and hashed phone number (ph). Adding first name (fn), last name (ln), and ZIP code incrementally improve the score. An EMQ of 4 or below means a significant portion of your purchase events are not matching to Meta accounts: the algorithm is effectively blind to what those customers look like, which means value optimisation is learning from an incomplete picture of your buyer population.
The practical fix for low EMQ is almost always server-side: ensure your CAPI implementation is passing all available customer information parameters with every purchase event, and that the values are being hashed correctly (SHA-256 lowercase). Meta's Events Manager shows EMQ per event type in real time, making it easy to diagnose which parameters are missing. The first-party data activation guide covers the broader data infrastructure required for reliable signal quality across both Google and Meta.
Value Optimisation With Advantage+ Sales Campaigns
Meta's Advantage+ Sales Campaigns (formerly Advantage+ Shopping Campaigns) is the recommended campaign structure for most DTC ecommerce advertisers in 2026. It combines automated audience targeting with Meta's AI optimisation across all placements, and fully supports value optimisation. When value optimisation is enabled and CAPI is sending purchase values, Advantage+ Sales Campaigns uses those values to guide both delivery and creative selection toward higher-revenue buyer profiles.
The Meta Advantage+ suite applies automated optimisations across audience, placement, and creative within a single campaign. For value optimisation specifically, this means Meta's algorithm has maximum flexibility to find high-value buyers wherever they appear across Facebook, Instagram, Messenger, and Audience Network: without the restriction of manually defined audience segments. The trade-off is reduced transparency into which audiences are producing results, which is why monitoring purchase value by cohort (not just ROAS) is essential.
For DTC brands using predictive lifetime value signals, Advantage+ Sales Campaigns and CAPI create the delivery pipeline. The pLTV bidding on Meta guide covers how to pass predicted 12-month customer revenue as the conversion value: the upgrade that shifts the algorithm from optimising for first-order spend to optimising for long-term customer value. AdZeta's ValueBid™ framework delivers this signal in real time via CAPI, enabling Meta's model to learn which profiles produce customers who are still buying 18 months later.
Common Configuration Mistakes
Relying on pixel alone without CAPI
iOS 14+ restrictions cause pixel-only setups to miss 15–30% of purchase events. Value optimisation running on incomplete event data produces a skewed model. Set up CAPI as a parallel signal source with deduplication. This is the single highest-impact fix for most Meta value optimisation underperformance.
Not passing the value parameter in purchase events
Value optimisation requires every Purchase event to include a value field with the actual transaction amount. Events without value data are counted as conversions but contribute nothing to the value learning model. Verify in Events Manager that each Purchase event shows a non-zero, varied value: not a uniform number.
Setting ROAS Goal too high at launch
A ROAS Goal set above what available auction inventory can support will cause delivery to pause and budget to go unspent. Meta's documentation is explicit about this risk. Start at or below your Highest Value historical ROAS and raise gradually. Most accounts need four to six weeks of stable Highest Value performance before introducing a ROAS Goal.
Running CAPI without deduplication
CAPI alongside the pixel without deduplication creates double-counted purchase events. Meta receives the same conversion twice, which inflates conversion numbers and distorts value signal quality. Pass a matching event_id in both browser and server events. Meta's Events Manager Diagnostics tab shows deduplication rate in real time.
Low customer information parameters reducing EMQ
An EMQ below 6 means a significant portion of events are not matching to Meta accounts. Adding hashed email and phone number to every CAPI event is the most impactful fix. Each additional parameter (fn, ln, zip) incrementally improves matching. Low EMQ means the algorithm is learning from an incomplete buyer population: it will find fewer of your best customers.
Key Takeaways
- Meta's value optimisation requires purchase values in your conversion events, value sets configured in Events Manager, and a minimum of 30–50 weekly purchases before the algorithm has sufficient data to learn reliably.
- CAPI is a prerequisite for reliable value optimisation, not an optional enhancement. iOS 14+ pixel signal loss means browser events alone miss 15–30% of purchases. Run CAPI and pixel in parallel with deduplication enabled.
- Highest Value is the correct starting bid strategy. Run it for four to six weeks before introducing a ROAS Goal. Setting a ROAS Goal too high causes Meta to pause delivery entirely if it cannot find auctions meeting the target.
- Event Match Quality (EMQ) determines how well Meta's algorithm can attribute conversions. Target an EMQ of Good (6–7.9) or Great (8–10). Hashed email and phone number in every CAPI event are the highest-impact parameters for improving EMQ.
- Advantage+ Sales Campaigns is the recommended campaign structure for DTC value optimisation in 2026. It gives Meta maximum flexibility to find high-value buyers across all placements while value optimisation guides the algorithm toward revenue, not volume.
- The upgrade from first-order purchase value to predicted 12-month LTV as the CAPI conversion value is where the 15% average ROAS lift from standard VBB becomes a 20–30% CAC reduction through pLTV-based acquisition.
Further Reading
pLTV Bidding on Meta Ads: What Actually Works in 2026: the technical implementation guide for upgrading beyond first-order AOV to predictive lifetime value signals via CAPI.
What Is Value-Based Bidding? A Complete Guide for DTC Brands: the foundational guide to how value-based bidding works across both Google and Meta.
Value-Based Bidding vs Target CPA: Which Strategy Is Right for Your DTC Brand: how to choose between conversion-count and revenue-based optimisation, and the correct progression between strategies.