Key takeaways
- Product Value Optimization tells Smart Bidding which products to value more, but it does not increase real transaction revenue.
- UK ecommerce advertisers should prepare margin bands, stock priorities and custom labels before using product multipliers.
- Adjusted conversion value must be reported separately from actual tracked revenue, or ROAS will become misleading.
- Performance Max accounts with broad product feeds face the biggest risk because spend can shift quickly across products.
- The right first test is a contained product group with clear margin, stock or lifetime value justification.
Product Value Optimization is not a cosmetic Google Ads test. It is Google giving retailers a new way to tell automated bidding which products deserve more budget, and that matters because Shopping and Performance Max already decide too much from incomplete revenue data.
For UK ecommerce advertisers, the hidden PPC impact sits in margin. A campaign can hit target ROAS whilst quietly scaling low-profit products. That is not growth. It is paid media flattering the dashboard while cash disappears into cost of goods, returns and fulfilment. If you already rely on automation, read this alongside our Google Shopping Ads management guide, because this change makes product-level economics harder to ignore.
Our view is direct: retailers that feed Google clean product priorities will gain more control. Retailers that use multipliers as a shortcut for poor tracking will inflate reported value and make worse budget decisions faster.
What Product Value Optimization actually changes
Google Ads is testing controls that let retailers adjust the value assigned to selected products or product groups for automated bidding. The feature is being described for Performance Max and Shopping campaigns. The important part is that advertisers can steer value by product attributes such as brand or category without rebuilding campaign structure.
The beta description points to campaign-level multipliers. If a product normally reports a £100 conversion value, a 1.5 multiplier tells the bidding system to treat that conversion as £150 for optimisation. The customer still paid £100. Your margin did not change. Your ad platform has simply received a stronger instruction to pursue that item.
Google’s own examples cover high-margin products, seasonal promotions and overstock. That makes sense. Those are three different commercial goals, and revenue alone does not tell the algorithm which one matters most this week.
Why margin, not revenue, is the real story here
Product Value Optimization changes the conversation from campaign performance to product profitability. That is overdue. Too many ecommerce accounts still optimise towards gross revenue because it is easy to pass into Google Ads. The problem is that gross revenue treats a £100 order with £40 profit the same as a £100 order with £8 profit.
Here is the mechanism. Smart Bidding chases the conversion value you give it. If your feed and tracking only pass retail price, the system learns to buy traffic that produces retail price. It does not know that one SKU has supplier rebates, another has a return rate problem, and a third is dead stock tying up warehouse space. Product-level value adjustments turn those business realities into bidding signals.
That makes the feature powerful, but also dangerous. A multiplier changes what the algorithm thinks a sale is worth. It does not change the sale. If finance reads adjusted conversion value as real revenue, reported ROAS starts lying. A product can look stronger in Google Ads because you told Google to value it more, not because the market bought more of it or because profit improved.
This matters most in Performance Max because product, audience, creative and channel decisions already sit inside one automated system. If you increase the assigned value for an overstocked range, PMax will have a clearer reason to allocate impressions and clicks towards that range. Spend then shifts away from products with lower adjusted values, even when those products used to carry volume. That is the point of the feature, but it means the budget movement must be planned, not discovered after a poor trading week. If you are still finding your feet with the format, our Performance Max explained for UK SMEs guide is a useful primer.
Across the UK ecommerce accounts we audit, we see the same pattern: reported ROAS is often thinner than owners expect once under-tracking is factored in, and it says nothing about margin, repeat purchases or offline sales. Treat reported last-click ROAS as a floor on returns, not a verdict on true profitability.
That is exactly why margin-led bidding matters. Adding product multipliers without a profit framework will make the account busier, not better. A higher adjusted value encourages more aggressive bidding. More aggressive bidding raises CPC tolerance. Higher CPC tolerance spends more budget in auctions that Google now believes are worth winning. If the adjusted value is wrong, the waste scales.
PPC Geeks’ View
The specific problem advertisers will face is adjusted-value confusion. Ecommerce teams will see higher conversion value in Google Ads after applying multipliers and mistake it for better revenue performance. Finance will then ask why sales, stock position or gross margin have not moved at the same rate. That reporting gap will create bad budget calls.
We see this most often in retail accounts running Performance Max with one large product feed, limited custom labels and Smart Bidding aimed at a blended ROAS target. The campaign looks tidy. The reporting looks simple. Underneath, Google is mixing high-margin hero products, clearance stock, accessories, repeat-purchase lines and low-margin range fillers into one optimisation pot.
That setup works only when the business goal is genuinely blended revenue. Most retailers do not operate that way. Merchandising wants to clear stock. Finance wants margin. Marketing wants volume. Operations wants fewer returns. Product Value Optimization gives PPC teams a lever to represent those trade-offs, but only if the feed already separates products into meaningful groups. If your Merchant Center data cannot distinguish margin bands or stock priorities, the new lever has nothing useful to pull.
Do not use product multipliers to make weak ROAS look stronger. Use them to tell Smart Bidding which sales are genuinely worth paying more to win.
— Lee Sinclair, Head of Operations, PPC Geeks
This is exactly the type of issue we look for in a free Google Ads audit, especially where automation, tracking or campaign structure is affecting performance. The immediate takeaway is simple: before you touch multipliers, define which product groups deserve more bidding pressure and prove that definition with margin, stock or lifetime value data.
How to prepare your account before the rollout
Start with your product economics, not the Google Ads interface. Build a list of product groups where a higher bid tolerance is commercially justified. Use gross margin bands, stock ageing, return rates, supplier funding, seasonality and repeat-purchase value. If that information lives outside the ad account, pull it into the planning sheet first.
Then audit your feed labels this week. If you cannot isolate high-margin, overstock, seasonal and range-builder products, add custom labels before using Product Value Optimization. Our custom labels for Google Shopping setup guide covers the practical structure. Do not rely on brand and category alone unless those attributes genuinely match the commercial priority. Category is often too broad. Brand is often politically neat but financially weak.
Next, create a multiplier register. For every product group, write down the original value, the multiplier, the reason, the expected commercial outcome and the date applied. Keep this outside Google Ads as a control document. When results change, you need to know whether performance moved because demand changed, bids changed, stock changed or reported value changed.
Separate reporting into three columns: actual tracked revenue, adjusted conversion value and estimated gross margin. This is non-negotiable. If your monthly report only shows the adjusted value, you have made the account easier for automation and harder for humans. That is a bad trade. Our guide on how to calculate the conversion rate accurately is a useful reminder that a clean number beats a flattering one.
Run the first test on a contained product group. Pick one high-margin range or one overstock group with enough conversion volume to read. Apply the multiplier at campaign level where the beta allows it, then compare spend share, CPC, conversion volume, actual revenue, adjusted value and margin proxy against a clean pre-test period. Do not judge the test on ROAS alone.
Before presenting results internally, label the feature correctly. Product Value Optimization is a bidding input, not a profit report. The Search Engine Watch report on the beta makes clear that the latest sighting is not a general launch, so UK retailers should prepare the operating model now rather than promise a release date. Google’s own conversion value rules documentation shows the wider reporting issue: adjusted values can affect both optimisation and reporting, so teams must separate original and adjusted value before calling performance improved.
Finally, update your trading meeting agenda. Add a standing PPC item for product priority changes. If merchandising changes the clearance list on Monday but paid media learns on Friday, automation spends four days optimising against stale priorities. Product value controls make that communication gap more expensive.
What this means for your campaigns
Product Value Optimization is a useful step because it recognises a truth retailers have lived with for years: not every pound of revenue is worth the same. Google Ads has been excellent at chasing tracked value, but tracked value is only as commercial as the data behind it.
The advertisers that benefit will already know their product economics. They will use multipliers sparingly, document every adjustment and report actual revenue separately from adjusted bidding value. The advertisers that struggle will apply broad uplifts to make automated bidding work harder, then wonder why spend has moved towards products that look better in Google Ads than they do in the P&L.
If you run Shopping or Performance Max, treat this test as a prompt to fix your feed segmentation, conversion values and reporting before the feature arrives more widely. When you want a second pair of eyes on the setup, our Google Ads agency team can pressure-test it with you.
Not sure how exposed your campaigns are? A free Google Ads audit will surface the practical gaps quickly. For the detail behind this, see Google’s do’s and don’ts of product feed optimisation and Microsoft’s best practices for Shopping campaigns.
Frequently asked questions
What is Product Value Optimization in Google Ads?
Product Value Optimization is a Google Ads test that lets retailers adjust the value assigned to selected products or product groups for automated bidding. It is designed for Shopping and Performance Max campaigns so advertisers can steer spend towards products with stronger commercial priorities.
Does Product Value Optimization increase ecommerce revenue?
No. It changes the value signal passed to bidding. A £100 sale remains a £100 sale, even if Google Ads treats it as £150 for optimisation. Advertisers still need to measure actual revenue, margin and advertising cost.
Which advertisers should care most about this test?
UK ecommerce advertisers using Performance Max or Shopping campaigns should care most, especially retailers with varied product margins, seasonal stock, overstock issues or supplier-funded ranges.
How should retailers prepare for Product Value Optimization?
Retailers should map product groups by margin, stock priority, return risk and repeat-purchase value. They should also add feed labels and build reporting that separates actual tracked revenue from adjusted conversion value.
Is Product Value Optimization available to all UK advertisers?
No general UK launch has been confirmed in the source reporting. Treat it as a beta signal and prepare the data structure now, rather than building plans around a fixed release date.
