Shopify Category Metafields Now Work in Analytics

Until now, the colour, material, fit and other attributes attached to a product through its category lived on the product page and nowhere else in the reporting stack. A merchant who wanted to know whether organic cotton outsold polyester, or which colourways were carrying a range, had to export sales data and rebuild the answer in a spreadsheet. That step has gone. Those attributes now sit in the Analytics dimension and filter menus alongside custom metafields, and for any store that has already categorised its products there is nothing to turn on.

A companion entry published the same day extends the idea to metaobjects. If a metaobject is attached to a product, variant, customer or order through a metafield, its fields can now group and filter a report in the same way. Shopify's own examples are a designer's country, a warranty term and a customer loyalty tier, and the detail is in the metaobject fields release note. Taken together, the two changes turn structured product and customer data that many stores already hold into something they can analyse without leaving the admin.

How it works

Category metafields come from Shopify's Standard Product Taxonomy. When a product is assigned a standard category, the taxonomy unlocks a set of attributes specific to that category. A shirt, for example, can carry size, neckline, sleeve length type, fabric, target gender and colour. Shopify Magic adds some of these by default based on the product details, and the values themselves are stored as metaobject entries that a merchant can rename or customise. Shopify publishes the full taxonomy as an open repository on GitHub, which is the quickest way to see which attributes a given category offers.

In Analytics, those attributes now appear in a Category metafields group in the report configuration panel, next to a separate Custom metafields group. They can be added as a dimension to break a report down by attribute value, or used as a filter to restrict a report to one value, such as a single colour or material. The same fields are available in Reports, in Explore and in the ShopifyQL query editor. Where a product has more than one value for an attribute, Analytics keeps those values together on one row, so a sale is not counted twice.

Custom metafields worked in reports before this release and still work the same way, with one condition that catches people out: each custom metafield definition needs its "Filter or group data in Analytics" option switched on before it appears in the menus. According to Shopify's guidance on filtering and editing reports, custom metafields are supported on four resource types (products, variants, customers and orders) and only for certain field types, including single and multi-line text, integers, decimals, ratings, dates, true or false, colour, URL, product references and lists of text or numbers.

Metaobject fields reach reports through a reference. The metafield on the product, variant, customer or order must be a single metaobject reference or a list of metaobject references. Fields reached through a Mixed reference metafield cannot be used, and not every metaobject field type is reportable. In the report builder you choose Metaobjects, then the resource, then the definition, then the field: Designer, then Country, for example. Metaobjects the merchant created are enabled by default and can be switched off per definition under Settings > Metafields and metaobjects. Metaobjects created by an app stay off until the merchant or the app turns Analytics on for that definition.

Examples and use cases

The obvious first use is merchandising. A clothing retailer can open a sales report, add Colour as a dimension and see which colours sell across the whole catalogue rather than product by product. Adding Material as a filter set to organic cotton narrows the same report to one fabric. Swap the dimension for Fit or Size and the question changes without a single export. For a brand planning reorders or next season's range, that is the difference between a rough impression and a figure that can be checked.

Metaobjects open up questions about the things around the product. A homeware retailer that stores each designer as a metaobject, referenced from the product, can group sales by the designer's country and compare how different parts of its range perform. A business selling electrical goods with a warranty term held in a metaobject can check whether longer-warranty lines sell differently from the rest. On the customer side, a loyalty tier stored as a metaobject and referenced from the customer record lets a merchant compare sales by tier inside the same reports it uses for everything else.

Gaps in the data become visible too. Report filters support a None value for empty entries, which gives a quick read on how much sales activity sits on products that have never been given a particular attribute. For a store with a long tail of older or imported products, that is a useful audit of how complete the catalogue data really is.

What this means for UK merchants

For UK stores the timing is useful. With the run-up to Christmas trading under way, being able to cut recent sales by colour, material or size inside Shopify makes replenishment and range decisions quicker to check. And because orders and sales were untouched by the recent change to how Shopify counts sessions in Analytics, sales reports grouped by attribute compare cleanly across the 21 September boundary in a way that session-based metrics do not.

The bigger point is that product categorisation now pays back in more than one place. Shopify's documentation says the standard category is used to unlock category metafields, to organise products and build collection conditions, to make selling easier on channels such as Google and Facebook that expect a standardised product type, and to drive the return reasons that also surface in Analytics. Category metafields, in Shopify's own words, help make products more discoverable on your site, on marketplaces and on search engines. Clean attribute data has always been part of solid Shopify SEO work and of a healthy Google Merchant Center feed, where the Google product category attribute does a similar job. It now also produces reports a merchant can act on, which makes the case for doing the tidy-up properly much easier to make.

Customer data deserves the same thought. Many UK merchants have spent the past year building retention around their customer records, whether through a loyalty scheme, segmented email or the SMS marketing automations Shopify added to Messaging in May. Where the data that decides who gets what, such as a loyalty tier, lives in a customer metafield or a referenced metaobject, it can now be read against sales in the standard reports rather than in a separate tool.

Practical considerations

The reports are only as good as the attribute data behind them. Products created through a CSV import or an app can save as uncategorised, which means they carry no category metafields and will not appear under an attribute at all. If a Shopify store build or migration is coming up, make category assignment part of the product import plan rather than a clean-up job afterwards. Shopify Magic's automatic suggestions are a starting point rather than a guarantee, so a store that has accepted them wholesale should spot-check a sample before relying on attribute reports for buying decisions. Multi-value attributes also need reading with care: a product listed in two colours appears on a combined row rather than being counted under each colour, which avoids double counting but means the single-colour rows do not tell the whole story on their own.

A few limits are worth knowing before building anything. Not every report can be edited: all default Finance reports except the United States sales tax report, all default Fraud reports, most default Orders reports and the Web Performance report cannot be filtered or have their columns changed, so attribute analysis belongs in sales reports and custom reports. Shopify also greys out dimensions that do not fit the chosen metric, so an attribute offered in a sales report may not be available against a payments metric. Filters and dimensions added to a report are temporary until the report is saved as a custom report. Metaobjects created by apps stay out of Analytics until someone turns them on, so if a key piece of product data is managed by an app, check the definition's Analytics setting or ask the developer. Shopify says the main Analytics features are available on any subscription plan, but staff need Analytics permissions to see the reports.

FAQ