Custom Labels Google Shopping: A Practical Setup Guide

You've got thousands of products in one Google Shopping campaign, and the reporting tells you the blended story: revenue, cost, and ROAS across everything. A bestseller, a low-margin range-builder, and an end-of-line product may receive broadly similar treatment even though your commercial priorities are completely different.

That's where custom labels in Google Shopping earn their place. They won't repair a weak product title or solve a disapproval, but they can give your feed a naming system that connects merchandising decisions with campaign structure, bidding, and reporting. The important work happens before you upload anything. Decide what each label means, define the values, and only then apply them consistently.

What Custom Labels Actually Do in Google Shopping

Custom labels are five retailer-defined product attributes, named custom_label_0 through custom_label_4, that sit in your Merchant Center product data. Google allows advertisers to use them for reporting and bidding in Shopping, Performance Max, and Demand Gen campaigns. Each product can carry one value in each field, with values limited to 100 characters, and advertisers can create up to 1,000 unique values for each custom-label attribute across an account, as set out in Google's custom label guidance.

The labels are not customer-facing. Shoppers won't see high-margin or clearance in the Shopping ad, and the labels don't directly change product visibility, search matching, or product ranking. Their job is to let you separate products according to business logic that standard feed attributes don't capture cleanly.

What labels can change

A well-built label structure can help you:

• Separate product groups: Filter campaigns or listing groups by values such as high-margin, bestseller, or clearance.
• Control bidding decisions: Give commercially important product clusters different targets, budgets, or bid approaches.
• Improve reporting: Compare performance by margin band, season, stock state, or product role rather than relying on catalogue-wide averages.
• Support exclusions: Remove products from a campaign when their stock position or profitability makes advertising inappropriate.

Google's documentation confirms that custom labels are available as five separate slots, rather than a fixed list of prescribed categories. You decide whether custom_label_0 represents margin, seasonality, or something else. That flexibility is useful, but it creates the main risk too: inconsistent naming quickly makes the data difficult to trust.

Custom labels won't fix feed disapprovals, weak photography, inaccurate availability, poor conversion tracking, or insufficient performance data. They also won't make an unprofitable product profitable. They make it possible to organise products so your campaign decisions reflect those realities instead of hiding them inside one blended catalogue.

Designing a Label Taxonomy Before You Touch the Feed

The most common mistake is opening a spreadsheet and filling custom_label_0 with whatever seems useful that day. That creates a field full of unrelated values, followed by increasingly complicated rules to interpret it. Design the taxonomy first, then give the feed team and PPC team the same written definition of every slot.

Google provides up to five custom-label fields per product, so each slot needs to answer one clear business question. Google recommends defining label values before applying them consistently across Shopping and Performance Max campaigns, as explained in its Google Ads custom-label documentation.

A practical UK retailer taxonomy could look like this:

This is a starting point, not a universal template. A furniture retailer may need price banding, while a beauty brand may prioritise promotional status or replenishment behaviour. The right question is always, “What decision will this value change?”

Naming rule: Use lowercase, hyphenated values such as high-margin and low-stock. Avoid spaces, mixed casing, abbreviations, and values that mean different things to different teams.

Keep each slot single-purpose. A value such as margin-low-bestseller combines two dimensions, making it harder to report on margin independently from product role. Put low in the margin field and bestseller in the product-role field instead.

Use the same naming convention in primary feeds, supplemental feeds, feed rules, spreadsheets, and campaign filters. A taxonomy becomes useful when it works as a small contract. The merchandising team knows what the label means, the feed process applies it predictably, and the PPC team knows which action the value enables. Guidance on keeping this structure organised is also covered in product feed management practice.

If a label can't be tied to a bid decision, an audience or listing-group filter, a budget choice, or a reporting question, it probably shouldn't occupy one of the five slots.

Adding Custom Labels Inside Merchant Center Feeds

Start with the join key, not the label value. A supplemental feed can only overlay data when its product identifier matches the identifier in the primary source. For most Merchant Center setups, that means id. Some retailers use a channel-specific offer identifier or SKU, but the value must match the product record that Merchant Center already knows.

Google supports custom labels in product data sources, including text and XML feeds, and also supports them through supplemental data sources and feed rules. The field headers must be written exactly as custom_label_0, custom_label_1, custom_label_2, custom_label_3, or custom_label_4. Values are free-form, but each value is limited to 100 characters under Google's Merchant Center specification.

Three practical implementation routes

Primary feed: Add the custom-label columns directly to the product rows if your ecommerce platform, feed management tool, Content API connection, or scheduled file gives you reliable control. This keeps the data in one place, but platform-generated feeds can overwrite manual edits during the next refresh.

Supplemental feed: Create a separate file containing the matching id and the custom-label columns you need. Merchant Center overlays those values on the primary product source. This is usually the cleanest route when Shopify, Magento, WooCommerce, or another platform owns the main feed and you don't want to modify its export.

Feed rules: Use Merchant Center's rule engine for straightforward conditions based on existing attributes such as price, availability, sale price, or product category. Rules are useful for simple logic, but complex commercial data usually belongs in an upstream feed or ERP process.

A typical supplemental CSV might contain:

The file doesn't need to repeat title, price, image, or description data. It only needs the identifier and the attributes you're adding. Once the source is uploaded and linked, Merchant Center must process the update before campaign filters can use the new values. A UK feed implementation guide from Hallam notes that supplemental-feed label changes can take a few hours to take effect after confirmation.

Check the result in Merchant Center's product diagnostics rather than moving straight into campaign edits.

A useful verification sequence is simple:

1. Confirm the supplemental source is linked to the correct primary source.
2. Check that the product IDs match exactly.
3. Open a sample of products from each intended label value.
4. Review diagnostics for processing errors or missing attributes.
5. Confirm that the expected products appear under the relevant label before changing campaign structure.

For a broader Merchant Center workflow, see this practical guide to Google Merchant Center feed management.

The video below shows the type of feed workflow involved in maintaining product data and labels.

Using Custom Labels to Drive Bidding and PMax Segmentation

A label has no value until it changes a decision. high is just text in a feed. Its commercial value appears when the PPC team uses it to isolate products, set an appropriate target, protect spend, or compare performance against a relevant group.

For Standard Shopping, labels can support campaign subdivisions and product-group reporting. For Performance Max, they can help organise listing groups and asset-group structures, but remember that bidding targets are applied at campaign level. If different product clusters need different targets, separating them into campaigns is usually clearer than placing multiple economic groups inside one campaign.

Consider a fashion retailer with three margin bands. The retailer might decide that core high-margin lines can support a more ambitious return target, seasonal products need a balanced approach while demand is active, and clearance products should be handled defensively. The exact targets must come from the retailer's own economics and measurement, not from a generic benchmark.

A label-to-action map

The useful comparison isn't margin versus product type as a matter of account preference. It's whether the split answers the question you're trying to solve. If profitability is the concern, a product-type split may group products that look similar but have very different costs, returns, and promotional pressure. A margin label is closer to the commercial decision.

For a fashion account, one sensible structure might place high-margin core products in one PMax campaign, seasonal products in another, and clearance in a controlled campaign or excluded set. The target values should be agreed with finance or ecommerce leadership, then reviewed when costs, pricing, or stock conditions change.

PMax campaign control needs careful handling because a listing group doesn't carry an independent tROAS inside a shared campaign. If each cluster needs a different target, use separate campaigns rather than assuming the label alone creates separate bidding logic. The practical constraints and control options are discussed in this Performance Max campaign guide.

Automating Label Assignment With Feed Rules and Scripts

Manual tagging is reasonable for a small initial test. It becomes fragile when products change price, stock, margin, promotion, or seasonal status. The answer isn't to fill all five fields immediately. Automate only the labels that are fed by dependable source data, and keep the rules simple enough to audit.

Feed rules for predictable conditions

Merchant Center feed rules can read existing product attributes and write a value into a custom-label field. For example, a rule might identify products with a particular availability state and write low-stock into custom_label_3. Another might use a price band, sale status, or product category to assign a campaign value.

Build rules in an order that makes conflicts visible. A broad rule that writes core should not overwrite a more specific rule that writes clearance. Test the logic against representative products, including products with missing values and products that meet more than one condition.

A workable rule structure looks like this:

1. Read the source attribute, such as stock state or price.
2. Apply the narrowest condition first.
3. Write one defined value to one custom-label slot.
4. Preserve the existing value where no condition applies.
5. Review the processed result before activating campaign changes.

Scripts and external business data

Margin often lives outside Merchant Center, inside an ERP, product-information system, or finance spreadsheet. In that case, an integration or scheduled script can calculate the relevant band and update the supplemental feed or Merchant Center data source.

The logic can remain straightforward:

• Read product ID and gross-margin data.
• Assign high, medium, or low according to the retailer's approved thresholds.
• Write the result to custom_label_0.
• Compare the new value with the previous value.
• Publish only validated changes.

Scripts that interact with Merchant Center or the Content API need appropriate access, error handling, and respect for platform processing and rate limits. They also need a clear approval process. A technically successful upload can still create commercially harmful changes if the ERP field is blank, delayed, or mapped to the wrong SKU.

Production safeguard: Keep an export of the previous labels and record the date, source, rule, and operator for every change.

The dangerous automation isn't the complicated one. It's the rule that runs successfully while overwriting valid labels with blanks, generic defaults, or stale values. Add a checkpoint before activation, test on a controlled product set, and make rollback possible. PPC Geeks' PPC reporting and management resources can also help teams connect feed changes with account-level monitoring, but the taxonomy itself still needs one accountable owner.

Troubleshooting Common Custom Label Problems

Most broken label systems don't need more fields. They need an audit. Five slots give you room to segment a catalogue, but they don't protect you from poor naming, conflicting logic, or stale product data.

The failures that repeatedly appear

• Inconsistent casing: New, new, and NEW can fragment filters and reporting. Standardise values to lowercase.
• Misspelled values: best-seller, bestseller, and best seller may represent the same intention while behaving like separate values. Keep one approved spelling.
• Trailing spaces: Spreadsheet exports can hide whitespace at the end of a value. Trim it before upload.
• Overloaded slots: A value such as margin-low-bestseller combines dimensions that should be reported separately. Put margin and product role in different fields.
• Missing updates: A seasonal product can remain marked peak after demand or stock conditions change. Refresh the source and validate the processed result.

Another poor choice is labelling by a dimension Merchant Center already handles adequately, such as broad product type, when the business question concerns margin or stock. Custom labels should add commercial context, not duplicate existing categorisation without a clear campaign purpose.

The five-slot limit is a design constraint, not an invitation to compress every idea into one field. If teams need more dimensions, rank them by the decisions they influence and retire low-value labels. Fewer clean values are more useful than a complete but confusing taxonomy.

A quick audit should start in Google Ads. Pull a product or segment report using the custom-label dimensions, sort the unique values, and look for spelling variations. Check how many products sit in each value, then compare those assignments with current promotions, stock states, and seasonal plans. Finally, inspect a sample of products in Merchant Center to confirm the feed output matches the campaign view.

If a label value has no campaign filter, bid decision, exclusion rule, or reporting use, remove it. Unused taxonomy creates maintenance work without creating control.

Reporting and Ongoing Optimisation Around Custom Labels

Custom labels become valuable when the team checks whether they still describe the catalogue accurately. A feed can be technically healthy while its commercial labels are wrong. A product can move from core to clearance, from well-stocked to low-stock, or from an unproven line to a reliable performer without the product title or category changing.

Build a Google Ads report with Custom Label 0 through Custom Label 4 available as dimensions where the campaign type supports them. Review conversions, conversion value, cost, and ROAS by label, then compare those results with the margin or stock data that gave the label its meaning. Revenue alone can flatter low-margin products, so the report needs to support the commercial question behind the taxonomy.

Keep a change log beside the report. Record which values changed, why they changed, which feed or rule made the change, and when the campaign structure was updated. Without that record, a performance shift can look like market volatility when it came from moving a product group between campaigns.

A maintenance rhythm that works

• Review margin assignments: Check that the current cost and pricing data still support each margin band.
• Retire expired seasonal values: Remove campaign labels that no longer represent an active trading period.
• Recheck bestseller status: A product's role can change as demand, stock, and promotion change.
• Audit low-stock products: Confirm that labels match current availability before continuing spend.
• Compare reporting with Merchant Center: Investigate products whose campaign label differs from their current feed or merchandising status.

The PPC Geeks KPI reporting guide is useful context for deciding which account measures should sit alongside label-level performance. The main principle is simple: don't judge the taxonomy by how tidy the spreadsheet looks. Judge it by whether it helps you make a faster, more defensible bidding or merchandising decision.

A good label system is a living segmentation layer. It connects feed data, campaign structure, margin thinking, stock decisions, and reporting without changing what shoppers see. Start with the dimension that matters most commercially, verify it carefully, and add complexity only when the next label will change what you do.

PPC Geeks can audit your Merchant Center feed, design a practical custom-label taxonomy, and connect it to Shopping or Performance Max campaign structure and reporting. If your catalogue is being managed as one blended bucket, visit PPC Geeks to discuss a feed and PPC setup built around your margins, stock, and trading priorities.