Integration · Ad channel
Google product category in Meta catalogs
Meta’s catalog documentation defines google_product_category as the item described according to Google’s product taxonomy, and links to Google’s own taxonomy file. It is optional, and Meta uses it for things like building product sets. The practical upshot: the IDs you generate for Google can go into your Meta catalog unchanged.
What this comes down to
- Meta defines
google_product_categoryagainst Google’s taxonomy and links to Google’s file. - It is optional in Meta catalogs.
- Meta uses it to help create product sets, and in the US for size and return-window requirements.
- Shopify documents that its Meta channel fills the value automatically.
The short version
- Generate the category IDsRun your product list through the Bulk Mapper to get one Google category ID per product.
- Add the column to your catalog dataAdd a google_product_category column to the data feed or sheet your Meta catalog reads, keyed by the same product IDs.
- Check the catalogAfter the next update, check the catalog’s item details and diagnostics for the category values.
Same attribute, same taxonomy
Meta’s product-categories page describes the Google product category as representing the item according to Google’s product taxonomy, and points to the same taxonomy-with-ids file Google publishes. There is no separate Meta list to map to for this field: a valid Google category ID is a valid value.
That makes a multi-channel feed simpler than it looks. Generate the category once — with the Category Finder for a few products or the Bulk Mapper for a catalog — and use the same column in both feeds.
What Meta uses it for
- Creating product sets from catalog items by category.
- In the United States, determining size requirements for categories that need them.
- In the United States, determining the return window that applies.
The Google category is one of the catalog’s optional attributes. Meta’s product-categories page, linked under Sources, is the place to check the current list of what it drives in your market.
If you sell through Shopify
Shopify’s documentation for its Meta sales channel says the Google product category is filled automatically. If the automatically chosen value is not the one you want, the Shopify integration page covers setting it explicitly.
One column, two catalogs
The simplest way to keep Google and Meta consistent is to keep categories in one place. Hold the category ID for each product in a single sheet or column keyed by product ID, and build both feeds from it. When a category changes — because a product was misfiled, or the taxonomy moved — it changes in both catalogs at once, and there is no second copy to drift.
That works because the product IDs are what both channels key on. If your Google and Meta catalogs use different ID formats for the same product, map them once and keep the mapping beside the category column.
Categories and product sets
Meta lists building product sets among the uses of the category. In practice that means a filter on the category field can gather, for example, everything under Apparel & Accessories > Shoes into one set for a campaign — which is only as clean as the categories underneath it. A catalog where half the shoes sit in a parent category and half in leaf categories needs a looser filter, and a looser filter catches things it should not.
Check before you send it anywhere
A wrong category now reaches two channels instead of one, so the review step matters more, not less. The Bulk Mapper keeps strong matches (a confidence score of 0.90 or more) in the upload-ready file and puts weak ones in needs-review.csv. Clear that short list before the column goes into either catalog.
Questions
Does Meta use the same category IDs as Google?
For google_product_category, yes: Meta defines the field against Google’s taxonomy and links to Google’s taxonomy file.
Is google_product_category required on Meta?
No, it is optional. Meta uses it for product sets and, in the US, for size and return-window requirements.
Sources
Read next
- How to find the right Google product category (with ID)A practical walkthrough: read the taxonomy, pick the most specific category that is still true, and get the numeric ID your product feed needs.
- Google product category: use the ID or the full path?Google accepts either the numeric ID or the full category path, not both. Why the ID is the safer choice, and how Microsoft treats each.
- google_product_categoryAn optional product-feed attribute that places a product in Google’s fixed product taxonomy, sent as a numeric category ID or as the full category path.
- Google product taxonomyThe fixed, published tree of product categories — 5,595 entries under 21 top-level branches — from which every google_product_category value must come.
- Google product category on ShopifyTwo category columns, two taxonomies. Filling Shopify’s does not fill Google’s, and a blank cell on re-import erases it.
- Google product category on WooCommerceCore WooCommerce has no Google feed. The category is extension meta: invisible to category editors, reachable by CSV round-trip.