5 reasons you should use metafields in your Google Shopping feed

Shopify product metafields let you store custom product data that the default Shopify fields cannot hold. When you map that data to your Google Shopping feed, you give Google Merchant Center richer, more accurate information about each product. That improves how your products appear in Google Shopping Ads and free listings, reduces feed errors, and makes your campaigns easier to manage.

This post covers five reasons to use product metafields in your Google Shopping feed, how to set them up in Shopify, and four apps that sync metafield data directly to Merchant Center.

What are Shopify product metafields?

A metafield is a custom data set you add to a Shopify product. Each metafield has a namespace and key that form a unique identifier, a value, and a type that controls the format of the data held. Common types include text, number, true or false, URL, and date.

Shopify's standard product fields cover the basics: title, description, price, SKU, and barcode. Metafields fill the gaps. If you need to store a material, a warranty period, a care instruction, or a compatibility list, a metafield definition is where that datum lives in your store.

Once a metafield definition exists in Shopify, it appears on the product edit page. You can enter values manually or update them in bulk via CSV export and import. Most Google Shopping feed apps can then read those metafield values and map them to the product data attributes Google expects.

Reason 1: Send product data that standard Shopify fields cannot hold

Google's product data specification holds dozens of required and optional attributes beyond title and price. Many of them have no direct match in the default Shopify product fields.

GTIN is a good example. Shopify stores barcode information in its barcode field, but if you use that field for internal codes, or if your barcode format does not match GTIN requirements, wrong or missing GTIN data goes into your feed. A product metafield lets you store the right GTIN value separately and map it to the right attribute in Merchant Center.

According to Matt Lawson, Director of Performance Ads Marketing at Google, providing the accurate GTIN for a product in your feed can increase conversion rate for that product by up to 20%. Google's own data also shows that merchants who added valid GTINs saw up to 40% more clicks and exposure across additional Shopping ad formats a figure cited by GS1 UK and independently validated by DataFeedWatch's research across thousands of merchant accounts.

The same logic applies to attributes like age_group, gender, material, pattern, and color when color needs to be a standardised value rather than freeform text. Brand is another field that can cause mismatches if the Shopify vendor field is populated inconsistently. Create a metafield definition for each of these, add the appropriate value per Shopify product, and map the metafield to the corresponding Google attribute in your feed app.

This keeps your storefront data and your feed data separate. You can update a feed value without changing what shoppers see on your product page. That separation is one of the most useful features of working with product metafields in a Google Shopping context.

For a full list of the attributes available in the Google Shopping Feed specification, Shopify's guide to Google Shopping product data feeds is a great place to start and will help you understand which fields can be covered by metafields.

Reason 2: Fix product category mismatches that affect campaign performance

Google uses product_category to decide which campaign settings, bidding rules, and shopping features apply to your products. A wrong or too-broad category places your products in the wrong auctions, against the wrong competitors, and can block eligibility for features like promotions or vehicle ads.

Shopify's product type field exists for this purpose, but it is a freeform text field. Many stores use it for internal labels rather than Google's product category taxonomy. That mismatch goes straight into your Google Shopping Feed.

A product metafield mapped to google_product_category gives you a clean, dedicated field for the correct Google taxonomy value. You can set a specific category per product without touching your internal product type labels, and you can choose a different value for each item based on what it actually is rather than how your admin has organised it.

When the product category in your feed is correct, Merchant Center can identify the right competitor set for price competitiveness reports, apply the correct tax and shipping rules, and surface your products in the valid filter section on Google Shopping. Wrong categories are one of the most common reasons for poor feed performance in accounts that otherwise look healthy. GoDataFeed's 2024–2025 audit data across merchant accounts found that 1 in 5 Shopping listings in a typical apparel catalog has at least one active disapproval and category mismatches are among the root causes that go undetected because Google's Merchant Center surfaces them in Diagnostics rather than pushing alerts to the merchant.

Reason 3: Sync variant-level data without manual workarounds

Shopify variants share the parent product's description and many of its attributes. If you sell a jacket in four colors and three sizes, each size and color combination is a variant. Shopify lets you set a price and SKU per variant, but custom attributes like material, fill weight, or care instructions are stored at the product level and shared across all variants by default.

That creates a problem when you need different feed values for different variants. This metafield solves this. You create a metafield definition at the variant level, enter a unique value for each namespace and key combination, and each variant gets the correct information in your Google Shopping Feed rather than inheriting a shared default.

This is especially useful for apparel and footwear, where size, color, and material combinations drive how products are matched to search queries in Google Shopping. It also matters for electronics, where compatible models or regional specifications can vary by variant. A variant metafield with valid namespace and key lets you map those differences precisely, and the feed app reads each variant as a separate product with its own correct data.

DataFeedWatch's guide to matching Shopify fields with Google Shopping attributes covers the most common field mapping decisions in detail, specially how to handle variants.

Reason 4: Improve custom labels for better campaign structure

Custom labels in Google Shopping let you segment products for bidding and campaign management. You can use them to group products by margin, by season, by stock level, or by any other criterion that matters to your business. Google's product data specification includes five custom label fields: custom_label_0 through custom_label_4.

Shopify has no native field for custom labels. The most common workaround is to use tags, but tags serve many purposes in Shopify admin, making them hard to filter cleanly in a feed app. A dedicated metafield per custom label gives you a simple, structured column in your product data that maps directly to the Merchant Center attribute.

For example, a metafield with namespace "google" and key "custom_label_0" that stores values like "high-margin," "clearance," or "seasonal" gives your feed app a reliable source to read from. You can update values in bulk from a CSV export without changing any other product setting. The idea is to keep label data clean and separate from operational fields like tags or product type.

This makes it possible to run one that targets only high-margin products, or to set a different bidding rule for products you want to clear, without manual workarounds or complex feed rules in Merchant Center. DataFeedWatch's post on custom labels for Google Shopping covers twelve useful segmentation approaches you can apply with this setup.

Reason 5: Reduce feed rules and fix disapproval errors at the source

Feed rules in Merchant Center let you transform and correct product data after it leaves your store. They are useful when you cannot change the source data. But every feed rule adds a step that can break, run incorrectly, or behave differently than expected.

If your feed already contains accurate values, you do not need a rule to fix them. A metafield that stores the accurate datum, mapped correctly in your feed app, sends Google exactly what it expects with no transformation layer in between.

You can thank a well-structured metafield for reducing the number of rules you need to maintain. This has a direct effect on data quality. Merchant Center flags products for missing or incorrect attributes, and those flags lead to disapprovals. If a required field is missing because a feed rule that was supposed to add it failed silently, you will not find out until you check the Diagnostics section. Working from a clean source reduces the surface area for that kind of error.

DataFeedWatch's Multichannel Marketing Report 2023 found that around 7% of all products submitted to Google Shopping are disapproved due to critical errors, with invalid GTIN values affecting nearly half of all merchants (48.43%) and policy violations affecting 44%. Platform-level data shows the error rate is notably higher for WooCommerce (8.27%) and Magento (10.00%) than for Shopify (5.47%), but none of those numbers reach zero without clean source data. Fewer feed rules also make your account easier to audit. When something goes wrong with a product's data, the question is whether the issue is in the source, in a feed rule, or in how Merchant Center interpreted the result. Start with a good source, and that question becomes simpler to answer and faster to fix.

How to set up product metafields in Shopify

Open your Shopify admin and go to the Settings menu. Select Custom Data from the left-hand section. Click Products to add a metafield definition at the product level, or click Variants to add one at the variant level.

Click Add Definition. Enter a name, a namespace, and a key. The namespace groups related metafields together. A common convention is to use "google" as the namespace for all feed-related fields. The key is the specific field name, such as "custom_label_0" or "gtin." Choose a content type and format, then save.

Once the metafield definition exists, it appears on each product's edit page. You can skip to main content on that page and scroll to the metafields section to enter values directly. To update values in bulk, go to your Shopify admin, select Products, and run an export. The CSV includes a column for each metafield definition. Fill in the values, then import the updated file.

To connect the metafield to your Google Shopping Feed, open your feed app and find the field mapping or attribute mapping section. Select the Google attribute you want to populate, then choose the metafield as the source. The app reads the metafield value for each product and includes it in the feed it submits to Merchant Center.

Four Shopify apps that support metafield mapping

These four apps support metafield mapping to Google Merchant Center. They each handle the sync between your Shopify store and your Google Shopping Feed in a slightly different way.

Multiple Google Shopping Feeds (by WoolyTech) lets you create several feeds from a single Shopify store. This is a good option if you sell across different countries or product categories and need separate feeds for each channel. The paid Boutique plan at $5.95/mo supports up to 1,000 products across 2 feeds; the Business plan at $25.95/mo covers up to 10,000 products and 6 feeds.

Google Shopping Feed 2 is a simpler tool suited to stores with a smaller catalog that want basic feed management with custom field support.

Simprosys Google Shopping Feed is a widely used option with a straightforward setup for connecting metafields to Google attributes. Rated 4.9 stars across more than 4,300 reviews on the Shopify App Store as of 2026, it supports Microsoft, Meta, and Pinterest feeds from the same account. Pricing tiers start at $4.99/mo for up to 500 products and scale to $17.99/mo for up to 10,000 products; variants are not billed separately, which matters significantly for apparel or footwear catalogs.

‍

DataFeedWatch is a more advanced feed management platform. It supports complex mapping rules, filtering, and multi-channel feeds across 2,000+ integrated shopping channels in 60+ countries, and has been used by major brands including Adidas, Decathlon, and KENZO. This is the right choice if you also sell on other channels and want a single tool to manage them. Starting price is $64/mo for a 15-day trial, with plans scaling by SKU count up to agency-level tiers.

The right app depends on the size of your catalog, the number of markets you sell in, and how much control you need over your feed rules. All four can read Shopify item metas and map them to the right Merchant Center attributes.

Where to start

Before you create any metafield definition, identify which attributes are missing from your current feed. Open Merchant Center and go to the Diagnostics section. Filter by disapprovals and warnings related to missing or incorrect product data. That list tells you exactly where to start.

Then match each missing attribute to a metafield definition. Set a consistent namespace and key convention and keep it the same across your entire store. Build the definitions in Shopify, populate the values for your best-selling products first, connect them in your feed app, and submit the feed to Merchant Center.

The most useful attributes to add as metafields in most cases are GTIN, google_product_category, custom labels, color as a standardised value, and material. Start with those. Additional attributes based on your specific product category can come next once the core data is valid.

Once the feed is running cleanly, use the data to inform your outreach structure. Products that share a custom label can be grouped into a single campaign or ad group, making it simple to set bids based on margin or seasonality. That is where clean metafield data starts to improve performance in a way you can measure directly.

‍