Product value optimization: Google Ads beta checks
Google Ads product value optimization lets retailers signal product priorities. Check the beta's scope, agree on client goals, and plan a measured agency test.

Contents
Google Ads product value optimization gives retailers another way to tell automated bidding which products matter. For your agency, the hard part is agreeing on what a more valuable sale means to the client. A merchant may want to clear inventory while the account team is working toward profit. Settle that difference before testing, or the next client review could celebrate the wrong outcome.
What does product value optimization change?
Google's announcement describes conversion-value adjustments for selected products or attributes, including brands and categories. It names Performance Max and Shopping, and says advertisers can apply those priorities without changing campaign structure. Profit and seasonal stock clearance are among the intended uses.
The September coverage does not establish a September launch. Search Engine Roundtable reported on September 14 that Google had announced the feature in June; Search Engine Land covered the beta on September 17. Google's current announcement page does not display a publication date.
Check whether your client's account has access before promising a test. These sources do not provide a complete eligibility checklist or a verified setup path for every account. Treat availability as an account-level question that still needs an answer.
What should your agency agree with the merchant?
Start with one commercial objective and name the person who owns it. Your fulfillment team can translate a product priority into a proposed test, but the merchant needs to approve why that priority matters and when it stops being useful.
Search Engine Land flags a useful distinction: a bestseller need not produce the most incremental profit. Ask the client for the evidence behind the proposed product group, including current stock and the costs that reduce what each order earns.
Use this hypothetical homeware retailer to make that conversation concrete. Its tableware has strong demand, while a drinkware collection needs to sell before the assortment changes. These are invented planning conditions, not client results.
| Possible objective | Evidence your team would request | Reason to reconsider |
|---|---|---|
| Favor profitable tableware orders | Product costs, packing costs, and returns | Fulfillment leaves little profit |
| Clear the drinkware collection | Remaining stock and the replacement date | The collection sells out or its deadline changes |

What would the client notice in a useful test?
Your client should understand why the agency wants a different mix of orders. If the agreed goal is clearing the drinkware collection, the review should ask whether that stock is moving on acceptable commercial terms. A larger bidding value alone does not demonstrate that more money reached the business.
Keep actual order economics in the review. Request the merchant's order and inventory records, then account for packing, shipping, and returns using the client's agreed cost definitions. The time spent preparing an order belongs in that discussion too.

Adriaan Dekker's practitioner post and discussion raise questions about interpreting adjusted values. They do not establish how every reporting column behaves. Before your test, confirm how you will distinguish the value used for bidding from the merchant's sales records, and label both clearly in the client review.
How should your agency scope the first test?
Use a written test brief so the account manager and delivery team can explain the same decision. This is a proposed agency workflow, not Google's beta setup procedure.
- Confirm access and the supported options visible in the client's account. Record any unanswered product or reporting questions before proceeding.
- Select one product group with reliable attributes. Have the merchant approve the commercial goal and the products included.
- Save the current campaign settings and agree on which merchant records will judge the outcome. Choose a review window that accommodates the client's buying and returns cycle.
- Document other planned account changes. Keep the AI Max migration checklist and Performance Max video-resizing checks in separate change records so later analysis has context.
- Agree on a stop condition, such as depleted stock or unacceptable profit after costs, and name the person responsible for reviewing it.
The next client review should answer the question you settled at the start: did the chosen product priority help the business? A clear brief gives your team a way to evaluate that answer even if beta access has to wait.
Sources · 4
- Product Value Optimization — Google, undated page, read September 24, 2026. Confirms product and attribute adjustments, supported campaigns, and business use cases.
- Google Ads tests Product Value Optimization for AI bidding — Anu Adegbola, Search Engine Land, September 17, 2026. Read in browser. Confirms beta coverage and the distinction between bestsellers and incremental profit.
- Google Ads Product Value Optimization Beta — Barry Schwartz, Search Engine Roundtable, September 14, 2026. Reports an earlier June announcement and the practitioner sighting.
- Product value optimization beta: practitioner observation — Adriaan Dekker, LinkedIn, read September 24, 2026; only a relative date displayed. Describes product adjustments; discussion raises reporting concerns without establishing reporting mechanics.
Adrian Vale

PMax AI video resizing: opt out by September 4
Google Ads is using generative AI to auto-create missing PMax video aspect ratios by default. Agencies have until September 4 to opt client accounts out.

Google AI Max migration: the September 1 agency checklist
Google starts force-migrating campaign-level Broad Match and auto-created assets to AI Max on September 1. What agencies and their clients should expect.

Meta Marketing API v26 migration: the agency checks
Plan Meta Marketing API v26 migration with verified deadlines, placement and creative checks, and a client handoff that catches silent configuration changes.