20 parts · 2 free / 18 member parts →
Continues from: PMax, Search, and Brand: Coordinate or Separate?
When the product pool is explainable
Confirm product sources are explainable before segmenting margin and stock
First confirm that current spend really lands in a product group or listing group entered through the feed, rather than brand leakage, a wrong page, or returning-customer recovery. If you already separated sources, bring the brand, non-brand Search, product, returning, and exploration reads; otherwise do that first. Explainable source only says which products to inspect; it does not say a high-revenue SKU has high contribution profit or belongs in the main scaling pool. This feed-margin bidding workflow then checks item ID, SKU margin, inventory days, refund reason, and label freshness.
If the source is still brand leakage or a wrong page, return to the previous article. If margin, inventory, or refund data is missing, mark observation and do not move budget. Make labels complex only when they change one clear budget action.
Confirm three inputs in the same PMax product pool
Google feed segmentation by margin: reconcile profit, stock, and label evidence first
Feed segmentation is not decorative product labeling. Reconcile product facts, contribution room, inventory, refunds, and label freshness before deciding which product group deserves budget and which stays in observation.
What this lesson answers
- Should Google Ads feed segmentation use category, price, or margin?
- How should custom_label_0 through custom_label_4 be assigned?
- Should high-revenue SKUs always enter the main scaling group?
- Does PMax spending on a few SKUs mean the segmentation is wrong?
- How often should feed labels be refreshed, and when should they be checked after an update?
- Can I change tROAS or budget immediately after feed segmentation?
- Can cost_of_goods_sold directly decide bidding?
- What fields belong in a feed-margin bidding review record?
Google Ads Pro Lesson 8
High-revenue SKUs are not always worth scaling. Feed labels should translate margin, inventory, refunds, fulfillment, and growth role into ad structure.
Set the pause line first: until margin sheet, inventory days, refund reasons, shipping subsidy, and discounts reconcile, do not treat strong ROAS as scale proof or move low-margin SKUs into the main scaling pool.
A feed is the product data a merchant sends to Merchant Center and ad systems; a custom label is a segmentation field written there for operating and media decisions; allowable CPA is the acquisition cost still tolerable after product cost, fulfillment, discounts, and refund reserve. They appear in product data, product grouping, and budget judgment respectively. Treating high revenue as high allowable CPA lets a loss-making SKU with the same ROAS absorb the main scaling budget.
Make one product row readable first
Before labels, calculate what one SKU can afford to pay for acquisition
A feed is the product data a merchant sends to Merchant Center. Its item ID, price, availability, and custom label can affect how a product enters Shopping or PMax product groups. Start with one 20oz bottle SKU and put selling price, product cost, fulfillment, discounts, refund reserve, inventory days, and recent orders together. A label is not decorative categorization. It should change one concrete budget or product-inclusion action.
Subtract product and service costs from revenue before asking what CPA is allowable. Two SKUs can both show ROAS 4.0 while one has contribution room and the other loses money as soon as ad cost is added. The segmentation table below teaches that difference. It does not turn high revenue into an automatic “scale” label.
If cost, inventory, refunds, or label-update time is missing, keep the SKU in observation. Do not let an old label move current budget.
Try it first
- Traits
- High margin, low refund, stable stock, mature page.
- Goal
- Stable profit and controlled scale.
- Budget
- Budget priority.
- Traits
- High volume and stable conversion, but average margin.
- Goal
- Hold revenue volume.
- Budget
- Can scale with guardrails.
- Traits
- Hero SKU, new product, or flagship.
- Goal
- Lift click intent and brand impression.
- Budget
- Conservative budget.
- Traits
- Tail inventory, end-of-season, or must-clear.
- Goal
- Release cash and storage.
- Budget
- Separate target.
Pro · Parts 2-19 · 18 parts
Members: full exercises and records
This part includes
- Stabilize identity before segmenting
- Fold refunds into the margin basis
- Observe before changing bids
Pro $20 / monthYearly $16 / month
Choose a plan, sign in with your email or Google account, and complete payment. You'll have instant access to all member benefits.
- Unlock every premium lesson
- Advanced tools and member resources
- Member-requested courses and ongoing updates
- Pro community and priority support
Checking your membership…
What's the difference between monthly and yearly?
Yearly plans save you 20% with annual payment. Monthly plans offer more flexibility for short-term needs.
FAQ
- Do the biggest SKUs always earn the main group?
No. High revenue only proves sell-through, not profit. Subtract product cost, fulfillment, discounts, payment fees, refund reserve, support cost, and ad spend before reading contribution room and allowable CPA; thin-profit SKUs should downgrade, observe, clear, or pause.
- After segmentation, should I observe or adjust the bid right away?
Do not change labels, listing group, tROAS, budget, and landing page in the same round. Confirm Merchant Center and Google Ads can read the labels, then observe budget migration; without a single-variable window, you cannot attribute the result to feed segmentation.
After product segmentation
- PMax, Search, and Brand: separate product and brand roles first: After feed segmentation, confirm brand traffic, product groups, and automated expansion are not mixed in one budget decision.
Sources
Sources: 5Last checked
Google Ads Help: article 11596074 (opens in a new tab)Checked
Google Ads Help: article 6275295 (opens in a new tab)Checked
Google Merchant Center Help: article 6324473 (opens in a new tab)Checked
Google Merchant Center Help: article 7052112 (opens in a new tab)Checked
Google Merchant Center Help: article 9017895 (opens in a new tab)Checked