Google Merchant Center custom labels for Shopify: setup, sync problems, and migration checks

Verified as of July 10, 2026

Google says Merchant Center provides five optional custom-label fields, custom_label_0 through custom_label_4, that advertisers use to group products for reporting and bidding in supported campaign types such as Shopping and Performance Max. Google says the values are not shown to shoppers, accepts values from 1 to 100 characters, and counts up to 1,000 unique values per custom-label field across the account.

Shopify documentation says the Google & YouTube channel does not use the legacy Google Shopping metafields in the product CSV, including the Custom Label 0 through Custom Label 4 columns. Another app may use them, but merchants should ignore those columns unless the app managing the feed specifically instructs them to populate the fields.

Custom labels are routing instructions for campaigns, not product-data fixes. A label can tell Google Ads that a product belongs to a high-margin group. It cannot tell Google whether the product page exposes the correct price, availability, identifier, shipping promise, return policy, or structured product data.

Quick answer

Google Merchant Center provides five optional custom-label fields: custom_label_0, custom_label_1, custom_label_2, custom_label_3, and custom_label_4. Advertisers use them to group products for reporting and bidding in Performance Max, Shopping, and Demand Gen campaigns. The values are private campaign data: they are not displayed to shoppers and do not change the content of your Shopify storefront.

Each product can have one value in each field. The difficult part is rarely choosing a label name. It is proving which system owns the value, whether Merchant Center received it, and whether your Shopping or Performance Max filters still match after a feed, app, or product-ID change.

A typical five-field labeling scheme

• custom_label_0 — margin: high, medium, low.
• custom_label_1 — product lifecycle: new, evergreen, clearance.
• custom_label_2 — season: summer, holiday, year_round.
• custom_label_3 — price band: under_50, 50_100, over_100.
• custom_label_4 — inventory priority: priority, standard, limited.

Do custom labels increase traffic or conversions?

Not directly. Custom labels are internal campaign controls. They can help an advertiser isolate products, compare performance, change bids, or include and exclude groups of products. That can support better campaign decisions, but the label itself does not add keywords, change product-page copy, improve organic SEO, correct a Merchant Center disapproval, repair a price or availability mismatch, add a missing GTIN, make a blocked page crawlable, or guarantee more traffic.

That distinction matters because campaign segmentation can be working exactly as configured while the products inside the segment still have storefront or feed-quality problems.

Custom labels are not Shopify tags

• Shopify tag — organizes products, collections, and Shopify workflows. It does not automatically become a Google custom label.
• Shopify metafield — stores additional product or variant data. It reaches Merchant Center only when an integration explicitly maps it.
• Merchant Center custom label — groups products for Google Ads reporting and bidding. This is the advertising attribute.
• Merchant Center data-source or feed label — identifies products associated with a particular source or market grouping. This is a separate concept from custom labels.
• Storefront badge — shopper-facing copy such as New or Bestseller. It has no connection to custom labels.

The Shopify custom-label CSV trap

Shopify product CSV files can contain legacy columns named Google Shopping / Custom Label 0 through Google Shopping / Custom Label 4. Their presence does not prove that the Google & YouTube channel sends those values to Merchant Center. Shopify explicitly states that its Google & YouTube channel does not use those Google Shopping metafields.

This creates a common failure pattern: a merchant exports the product CSV, fills in the custom-label columns, imports the CSV back into Shopify, and the values appear to exist in Shopify — but Merchant Center never receives them. The value was entered into a field the active feed integration does not consume.

The only reliable proof is the processed product data in Merchant Center — not the existence of a tag, metafield, or CSV column in Shopify.

Where should Shopify custom labels come from?

Start by identifying the system that owns your Merchant Center product data. The usual flow is Shopify product data, then a feed or integration, then the Merchant Center product, then the Google Ads product or listing group. The label must be created or mapped somewhere in that chain.

Option 1: a feed app or feed-management platform

• Use this route when your feed app explicitly supports mapping Shopify data — such as a tag, metafield, cost calculation, or inventory rule — into the Google custom-label fields.
• Confirm which Shopify field the app reads and whether the rule runs at product or variant level.
• Confirm how frequently the label is recalculated and whether the app replaces existing Merchant Center values.
• Confirm whether multiple feed sources are submitting the same product. Do not assume every Shopify app uses the same fields or mapping rules.

Option 2: Merchant Center attribute rules

Google now calls feed rules attribute rules. Attribute rules can populate an attribute from an existing source value, a static value, or conditional logic — for example, assigning a price-band custom label based on the submitted price. Google says the Advanced Data Source Management add-on must be enabled, and rules are configured against a particular product source and can be tested before being applied.

Attribute rules work best when the label can be reliably derived from data Merchant Center already receives. They are less suitable for information Merchant Center does not know, such as true contribution margin, strategic inventory priority, or an internal launch plan.

Option 3: a supplemental data source

A supplemental data source can add or update attributes on products that already exist in a primary data source. It cannot create products by itself. This can be useful when a merchant maintains custom labels in Google Sheets, a file, or another operational system.

The matching details matter. Google requires the supplemental product ID to match the primary product ID exactly, and the feed or data-source label and language must align with the primary source for the data to attach. If the Shopify integration later changes those product IDs, the supplemental file can continue processing successfully while matching none of the intended products.

Option 4: Merchant API or another API integration

• A custom integration can compute and submit labels directly, which gives the merchant the most control.
• It also creates responsibility for stable product IDs, variant-level assignment, refresh schedules, and error handling.
• Plan for source priority, campaign dependencies, and migration before the integration goes live.
• Treat the integration that writes the label as its source of truth.

What about the Shopify Google & YouTube app?

First confirm what the app currently sends for your account and product setup. Do not assume that a Shopify tag, custom metafield, or legacy Google Shopping CSV field is automatically mapped — Shopify documentation specifically warns that the Google & YouTube channel does not use the legacy Google Shopping metafields in the product CSV.

When a required custom-label mapping is not available through the app, use an explicit supported route such as an attribute rule, supplemental source, feed-management integration, or API.

Product-level versus variant-level labels

Google treats submitted variants as separate products with separate IDs, while related variants share an item_group_id. A small red shirt and a medium blue shirt can have different product IDs but the same item-group ID. That affects custom labels.

Suppose only the red variants are in clearance. Applying clearance to the parent Shopify product may label every variant, depending on the integration. Applying it at the variant level can label only the affected offers. A supplemental source must use the individual Merchant Center IDs that correspond to those variants.

Before creating the rule, decide whether the business decision applies to the entire Shopify product, a specific variant, all variants in an item group, a particular country or market, or a specific feed or data source.

How to design a label structure that remains useful

• Give every field one documented meaning. Do not mix margin and lifecycle values inside the same field — custom_label_0 should always mean margin if that is what you documented.
• Use a controlled vocabulary. Choose one version of each value, such as high_margin, and do not mix variants like high margin, High-Margin, best_margin, and high. Google custom-label values are not case-sensitive, but a controlled vocabulary still prevents rule, spreadsheet, reporting, and maintenance errors.
• Automate dynamic labels. A label such as evergreen can stay stable for months, but top_seller, low_stock, or high_margin may change frequently. For every dynamic label, define the calculation, the source data, the refresh frequency, the system responsible for updating it, and the fallback when source data is unavailable.
• Group products rather than identify them. Do not put a unique SKU, product ID, or order-specific value into a custom label. Google counts only 1,000 unique values per custom-label field across the account; values beyond the limit are not taken into account for reporting, bidding, or product-group membership.

The label exists in Shopify but not Merchant Center

1. Open the affected product in Merchant Center and identify the primary product source.
2. Find the current Merchant Center product ID.
3. Confirm which integration is supposed to supply the custom label.
4. Inspect that source raw or submitted value, then check the processed value after all rules have run.
5. Common causes: the value sits in a legacy Shopify field the Google & YouTube channel does not use, a tag or metafield was never mapped, the wrong feed app owns the product, an attribute rule was created against a different data source, the product or variant ID does not match the supplemental source, or another source or rule replaces the value.
6. Do not keep editing Shopify until you know the active integration reads the field you are changing.

The label appears in Merchant Center but not Google Ads

• Check whether Merchant Center and Google Ads are linked to the expected accounts and whether the campaign uses the correct Merchant Center account.
• Check whether the listing or product group filters on the intended custom-label field and whether the filter expects a different value.
• Check whether the campaign is limited by a data-source or feed label.
• Check whether the affected variants carry the label or only the parent product does. A custom label can be present in Merchant Center while a campaign filter still points at an old value or a different label field.

The labels disappeared after an app reconnect or migration

• Compare the before-and-after state for representative products: product ID, item-group ID, data source, data-source or feed label, language, market or country, custom_label_0 through custom_label_4, approval state, Shopping product-group filters, and Performance Max listing-group filters.
• A source or product-ID change can break downstream rules and filters even when the products still appear in Merchant Center. Do not change product IDs, campaign filters, and supplemental joins independently — see the Merchant API migration checklist for the full comparison packet.
• If the labels look correct but Shopping performance changed, do not assume the labels are the root cause. Inspect the products behind the affected label group for price disagreement between page, schema, and feed, incorrect availability, missing or inconsistent GTINs, broken variant selection, missing shipping or return evidence, canonical or redirect problems, blocked crawlers, and landing-page failures.

A fast diagnostic sequence

1. Scan the public product URL. Run an affected product through StoreSteady to check the product page, structured data, policy evidence, canonical signals, and crawler-access conditions. If the scan finds a public product-data problem, fix that source first.
2. Verify the Merchant Center product. Open the exact offer or variant and record the ID, item-group ID, data source, custom labels, feed or data-source label, price, availability, identifiers, and current diagnostics.
3. Identify the custom-label owner. Determine whether the value comes from a feed app, Merchant Center attribute rules, a supplemental source, Merchant API, or another integration.
4. Compare the campaign filter. Inspect the Shopping product group or Performance Max listing group and confirm it references the current custom-label field and value, product IDs or item-group IDs, data-source or feed label, and country or market.
5. Change one source and retest. Do not edit Shopify, Merchant Center, supplemental files, and Google Ads simultaneously. Change the system that owns the incorrect value, allow the data to process, then retest the same product.

Where StoreSteady fits

StoreSteady does not create, rewrite, or manage your Google Ads custom labels, and the free public scan cannot see a private Merchant Center custom-label value by crawling your storefront. Its job in this workflow is to answer the earlier and often more important question: is this actually a custom-label problem, or is the product evidence behind the campaign already missing, inconsistent, or inaccessible?

The public scan checks product-page facts, price and availability signals, product identifiers, structured data, policy evidence, canonical and landing-page signals, and crawler access. Connected scans compare storefront-versus-source drift where supported data is connected. Merchant Center remains authoritative for the feed approval state and Google-specific disapproval codes; StoreSteady focuses on the public-commerce evidence that feed approval alone does not prove.

Related StoreSteady help

• Shopify Google & YouTube app Merchant API migration checklist
  Use the migration checklist when data sources, product IDs, feed labels, or campaign filters changed around the Content API shutdown.
• Shopify product IDs changed in Merchant Center
  Use the product-ID triage when supplemental joins and label rules stopped matching after an app reconnect.
• Incorrect product identifiers in Google Merchant Center
  Use the identifier guide when GTIN, MPN, or brand evidence disagrees across sources.
• Shopify products missing from Merchant Center
  Use the missing-products guide when whole products never arrive in Merchant Center, not just their labels.

Official source context

• Google custom_label_0 to custom_label_4 attribute
• Google Merchant Center product data specification
• Shopify product CSV and Google Shopping metafield guidance
• Google Merchant Center attribute rules
• Google Merchant Center supplemental data sources
• Google item_group_id attribute

Common questions