Custom labels are five optional product-feed fields, named custom_label_0 through custom_label_4, that let you tag each product with a value you define and then group those products for bidding inside an ad platform. They mean nothing to shoppers and never change which searches a product matches; they exist only to organize your catalog for campaign management and reporting.
If you sell more than a handful of products, custom labels decide whether you can steer budget toward your highest-margin and best-selling items. Skip them and your feed stays one undifferentiated block, so a low-margin clearance item can burn the same spend as the product that funds your quarter.
A custom label is a free-form attribute you attach to a product in your feed so an ad platform can sort that item into a group you control. Each product carries one value per label, and you choose what every label means, because the platform defines none of them. The whole point of the attribute is that you decide the segmentation logic.
Every feed gets five of these slots, numbered custom_label_0 through custom_label_4, and each slot holds a single text value per product. Advertisers typically map one slot to a business dimension such as margin tier, another to seasonality, and a third to sale status, so a single product can belong to several segments at once. Values stay invisible to shoppers and never influence product matching or categorization.
Custom labels sit alongside standard feed attributes like title, price, and product type, but those describe the product while custom labels describe your strategy for it. Where a product category tells the platform what an item is, a custom label tells it how you want to bid. That distinction is why custom labels drive campaign planning and reporting.
Custom labels move from your feed into your bidding structure in a fixed order, and the ad platform reads them only after the feed refreshes.
Define segments: Decide what each label slot represents, such as margin or season, and set the exact values you will use.
Tag products: Write the chosen value onto each product by hand, through a feed rule, or with a tool that scores items and writes the label back.
Submit the feed: Sync the feed to Google Merchant Center so the platform ingests the new values on its next processing run.
Group and bid: In Google Ads, subdivide a Shopping or Performance Max campaign by a label value, then apply a distinct bid or budget to each group.
The output tells you how each self-defined segment performs and where budget works hardest. It says nothing about whether a product matches a query, because custom labels have no effect on matching.
Custom labels decide how precisely you can spend an advertising budget. When you buy ad placements across thousands of products, the question is always which items deserve more money and which should be held back, and custom labels are what let you act on that answer inside the campaign. That precision is the difference between an efficient account and one that quietly overspends.
Protect margin: Without a margin label, a smart bidding strategy optimizes toward revenue or conversions and can pour spend into high-volume products that lose money on every sale.
Control seasonality: A season label lets you pause or throttle out-of-season items on a schedule, so a winter catalog stops drawing budget in July while summer lines scale up.
Report by strategy: Segmenting by custom label lets you read performance by business priority such as bestsellers or clearance, which turns a flat product report into a decision you can act on the same day.
Growth marketers use custom labels to split a Shopping feed by profit margin and shift budget toward the products that actually fund growth.
Demand gen leads use custom labels to flag high-intent product lines so Performance Max campaigns prioritize them during a launch.
Content strategists use custom labels to tag seasonal collections so campaign reporting lines up with the editorial calendar they plan against.
A custom label is a feed attribute, which means its value lives in your product data and updates only when the feed is refreshed, so a change you make in the morning will not reach the ad account until the next scheduled processing run.
Each label carries one open-ended value you define, so consistent spelling and casing across every product is what makes a segment usable, because the platform treats Winter and winter as two separate groups.
A product group is the structure you create in the ad platform from a label value, and it is the only place where bids, budgets, and segment-level reporting actually attach, so the label is useless until a group is built from it.
Steer budget toward high-margin products instead of spreading spend evenly across the catalog.
Exclude out-of-season items automatically so they stop consuming budget.
Create product groups in Google Ads and Performance Max from any dimension you define.
Report performance by business priority instead of generic product category.
Apply distinct bids to bestsellers, clearance, and new arrivals in a single campaign.
Set up your first segment with a free feed rule in Google Merchant Center.
Map one dimension per slot: assign custom_label_0 to margin and custom_label_1 to season, so each group stays clean and you can combine them later.
Keep values short and standardized: use a fixed vocabulary like High, Medium, Low, because inconsistent casing splits one segment into several.
Automate volatile labels: score fast-changing dimensions such as stock age or ROAS with a scheduled rule, since manual updates fall out of date within days.
Leave stable labels to feed rules: handle season or price band with a free Merchant Center rule, which runs on every refresh with no extra tooling.
Document what each slot means: record the dimension and allowed values somewhere the whole team sees, so no one repurposes a slot and breaks reporting.
Avoid using a custom label for data that already has a standard attribute. Putting color or product type into a custom label duplicates what the platform already reads and leaves you maintaining two versions of one field, a mistake experienced advertisers still make when they rush a feed setup.
AirOps: AirOps tracks how your products and brand surface across AI answer engines, so you can see where your organic catalog shows up while your custom-label segments drive the paid side.
Google Merchant Center: This is where you store and refresh your product feed, set the custom label values, and run free feed rules that assign them automatically.
Google Ads: This is where custom label values become product groups you can subdivide, bid on separately, and report by segment across Shopping and Performance Max campaigns.
Audit your catalog: Export your product feed and list the business dimensions that drive spending decisions, such as margin, season, and bestseller status. You can do this in a spreadsheet this week with no budget approval.
Pick your slots: Assign each dimension to a specific label number, from custom_label_0 to custom_label_4, and write down the exact values you will allow for each.
Tag a pilot segment: Apply one label to a small, high-stakes slice of the catalog first, so you can confirm the values flow through before touching everything.
Build the product group: In Google Ads, subdivide a campaign by your new label value and set a distinct bid or budget for the segment.
Measure and expand: Watch segment performance for a few weeks, confirm the split changed spend the way you intended, then roll the approach out to the rest of your labels.
Custom labels are five self-defined feed fields that let you group products for bidding inside an ad platform.
You set them by writing a value into each product, through a spreadsheet, a feed rule, or an automated tool.
A label does nothing until you build a product group from its value and the feed has refreshed.
Inconsistent or stale values quietly fracture a segment and send budget to the wrong products over time.
The payoff comes from tagging the dimensions that change spending decisions, like margin and season, first.
Custom labels and product categories do different jobs, even though both sit in your feed. A product category, set through the Google product category or your own product type, tells the platform what an item actually is, and it influences how the item is classified and sometimes which queries it can match. A custom label carries no such meaning. It is an open field where you record your own strategy for a product, such as its margin band or its season, and the platform never reads it for classification or matching. The practical difference shows up when you build groups: categories let you segment by what you sell, while custom labels let you segment by how you want to spend. Most advertisers use both together. They rely on categories for the structure the platform understands, and they add custom labels for the business distinctions, like profit tier, that categories can never capture on their own.
How often you update custom labels depends entirely on what each label represents. A stable dimension like season changes a few times a year, so a single feed rule that runs on every refresh keeps it current with no ongoing work. A volatile dimension is different. If a label tracks stock age, ROAS, or bestseller status, the underlying data can shift daily, and a value you set last month may now point budget at the wrong products. For those labels, an automated process that recalculates and rewrites the value on a daily or weekly schedule is the only way to stay accurate at any real catalog size. A useful rule of thumb is to match the update frequency to how fast the data moves: set seasonal and structural labels once, and refresh performance-driven labels on a schedule. Updating everything constantly wastes effort, and updating performance labels too rarely slowly erodes the segmentation you built them for.
Custom labels show different results across campaigns because the label itself does nothing; the campaign structure around it does the work. The same label value can sit in one campaign with an aggressive bid and in another with a conservative one, so identical products perform differently depending on how each campaign is configured. Budget caps matter too. A segment that looks like a weak performer may simply be starved of spend in a campaign that prioritizes other groups. Audience and placement settings add more variance, since Performance Max decides where to show products based on signals that have nothing to do with your labels. Timing is another factor, because a value written before the last feed refresh may not yet be live everywhere you expect. When results diverge, check the campaign settings, the budget allocation, and the feed refresh status before you conclude the label itself is the problem.
No, custom labels cannot change which searches your products appear for. They have zero effect on matching, ranking, or classification, so adding or editing a label will never make a product eligible for a query it could not already match. The things that drive matching are your product title, description, attributes, and the overall relevance of the item to the search. If you want a product to surface for more queries, that is where the work belongs: improve the title, enrich the attributes, and make sure the product data is complete and accurate. What custom labels do control is money and reporting. Once a product already matches a query, a label lets you decide how aggressively to bid on it and how to measure it against other segments. So treat labels as a spending and analysis layer, and treat your core feed content as the lever for visibility. Confusing the two leads to editing labels when the real fix is better product data.
A good custom labels setup is one where every label maps to a real spending decision and nothing else. The strongest signal of quality is restraint: you use only the slots you need, each one represents a single clear dimension, and the values follow a fixed, documented vocabulary that the whole team recognizes. A good setup also matches maintenance to volatility, so stable dimensions run on simple feed rules and performance dimensions update on an automated schedule. You can gauge quality by asking a direct question about any label: does its value change how I bid or how I read results? If the answer is no, that label is clutter and should go. Coverage matters too, because a label that only tags a fraction of the catalog produces skewed reporting. Aim for labels that are complete, consistent, and tied to margin, season, or performance, since those are the dimensions that actually move return on ad spend.