GA4 Content Groups

GA4 Content Groups let WooCommerce store owners see which product categories drive revenue, but most stores see “(not set)” because Content Groups require explicit configuration that standard tracking plugins skip. There are three fix paths: GTM hardcoded rules (requires GTM expertise), gtag.js customization (requires a developer), or server-side automatic mapping using WooCommerce’s own category taxonomy data. Server-side mapping through a first-party tracking server like Transmute Engine eliminates maintenance entirely—sending accurate content_group parameters with every page_view and purchase event without code changes.

GA4 does not offer native content grouping settings like Universal Analytics did—you must send the content_group parameter via GTM with each pageview. Most WooCommerce stores skip this setup and end up scrolling through hundreds of URLs unable to answer basic questions: do blog posts convert better than product pages? Content groups aggregate pages into categories (Products, Blog, Category Pages) so you can make content strategy decisions from data. Setup requires GTM with either a RegEx table variable or data layer approach. Content group data appears in GA4’s Pages and Screens report 24-48 hours after implementation. For WooCommerce, use separate groups for product categories and blog categories.