# GA4 custom channel groups for ecommerce store traffic Build rule-based channel groups in GA4 Admin so paid social, marketplaces and email split cleanly in acquisition reports and purchase explorations. - Date: 2026-10-22 - Category: Analytics ## Table of contents - Why GA4 custom channel groups ecommerce stores need their own rules - How GA4 custom channel groups ecommerce reporting actually works - Production checklist for GA4 custom channel groups ecommerce - What breaks when GA4 custom channel groups ecommerce rules fight reality - How to measure GA4 custom channel groups ecommerce after launch - Related work on this site - FAQ - What are GA4 custom channel groups ecommerce teams allowed to create on Standard? - Do GA4 custom channel groups ecommerce reports change historical data? - Can GA4 custom channel groups ecommerce replace default channel group in every report? - How do GA4 custom channel groups ecommerce relate to purchase and item reporting? GA4 custom channel groups ecommerce teams ask for when the default Paid Social bucket hides Meta prospecting next to TikTok Shop traffic. I am a Gold Coast web developer with 18 years on Magento, Shopify and WooCommerce catalogues. Merchandisers do not want another spreadsheet that re-labels source and medium every Monday. They want purchase revenue in GA4 split the same way media plans and agency decks already talk about channels. This note is for stores that already send clean [GA4 ecommerce events](https://alanvo.com/blog/ga4-ecommerce-events/) and have argued about [GA4 attribution models](https://alanvo.com/blog/ga4-attribution-ecommerce/) at least once. Custom channel groups do not fix bad UTM hygiene. They give you a stable, rule-based layer on top of source, medium, campaign, and source platform so acquisition reports and explorations match how the business actually buys traffic. ## Why GA4 custom channel groups ecommerce stores need their own rules GA4 custom channel groups ecommerce stores need because Google's default channel group is fixed and often too coarse for multi-market catalogues. Google's [Default channel group](https://support.google.com/analytics/answer/9756891) article is clear: you cannot edit those predefined channels in the Admin UI. Paid Search, Organic Social, and Email stay as Google defines them unless you build something else. That works until you run brand versus non-brand search in separate Google Ads accounts, or you send Klaviyo flows with `utm_medium=email` while SMS uses another medium string your agency invented three years ago. [Custom channel groups](https://support.google.com/analytics/answer/13051316) let you define up to fifty channels per group using AND and OR rules on fields such as source, medium, campaign name, campaign id, source platform, manual ad content, and even the default channel group itself. Google applies rules in list order: the first matching channel wins. That ordering detail is not cosmetic. If you put a broad "Paid social" rule above a narrow "Meta remarketing" rule, remarketing sessions never get their own row. Standard GA4 properties get two custom groups in addition to the predefined default. Analytics 360 properties get five. Plan which two groups matter before you burn both on experiments. I usually keep one group aligned to the media plan (paid brand search, paid non-brand, marketplaces, affiliates) and one for lifecycle email versus SMS versus loyalty app deep links. Custom groups can be applied retroactively in reporting, which is the feature marketing remembers from the GA4 launch blog. Historical sessions recompute when you open a report or exploration. That does not rewrite tags on the site. It reclassifies traffic you already collected, as long as source and medium were captured correctly at session start. ![GA4 custom channel groups ecommerce charts on a widescreen monitor](../../images/blog/ga4-custom-channel-groups-ecommerce-1.jpg) ## How GA4 custom channel groups ecommerce reporting actually works GA4 custom channel groups ecommerce reporting works by attaching rule-based labels to sessions, then letting you use those labels anywhere the default channel group already appears. Google documents supported reporting fields in the custom channel groups help page: campaign id, campaign name, default channel group, manual ad content, medium, source, and source platform. You build channels in Admin under Data display, then Channel groups. You need Editor access or above on the property. Each channel is one display name plus a filter expression. Expressions can nest AND groups (only OR inside) and OR groups (no further nesting of AND/OR). A typical paid search split might use OR across rows: one channel where medium matches `cpc` and campaign name contains `-brand-`, another where medium matches `cpc` and campaign name does not contain `-brand-`. Google's examples include an AI assistants channel built from source and campaign patterns, which matters if referral traffic from chat tools shows up as `(direct) / (none)` until you tighten rules. After you save a group, it shows up as a dimension in Acquisition reports that already support default channel group, as a secondary dimension on reports like Events, inside Explorations, in audience conditions, and in custom report tables. Google notes custom channel groups are not available in the Key events paths report yet, and cost or click metrics are not available when you filter on manual ad content alone. You can mark one custom group as the property primary channel group. Google's help text explains that primary replaces the editable default over time: future hits populate the primary channel group dimension using your selected group's rules. Changing primary is forward-looking for that dimension's definition history, so document the switch date in your analytics runbook the same way you document a GTM container version. For API and BigQuery users, the [Data API schema](https://developers.google.com/analytics/devguides/reporting/data/v1/api-schema) exposes custom groups with scoped names such as `sessionCustomChannelGroup:ID`. That pairs with [GA4 BigQuery export](https://alanvo.com/blog/ga4-bigquery-ecommerce-export/) when you need purchase revenue by custom channel outside the UI. The Admin API also exposes channel group resources if you automate governance across many properties. Ecommerce measurement stays separate. Purchase, add_to_cart, and item parameters still follow the [Measure ecommerce](https://developers.google.com/analytics/devguides/collection/ga4/ecommerce) event model. Channel groups classify how the session arrived; they do not replace item-level parameters or transaction_id on purchase. Join channel dimensions to purchase events in explorations or SQL, not inside the item array. ![Spreadsheet and coffee while reconciling revenue](../../images/blog/ga4-custom-channel-groups-ecommerce-2.jpg) ## Production checklist for GA4 custom channel groups ecommerce A store is ready for GA4 custom channel groups ecommerce work when UTMs on paid links, email tools, and affiliate parameters match a written convention, and when DebugView shows consistent session source and medium on a test purchase path. 1. Export the last ninety days of session source, medium, and campaign name from an exploration or BigQuery. Sort by sessions and revenue. That list is your channel rule inventory, not guesswork. 2. Draft channel names with merchandising and media leads before you touch Admin. Keep display names under eighty characters per Google's API limits if you might automate later. 3. Order rules from most specific to most broad. Place remarketing, brand search, and single-partner affiliate rules above catch-all Paid Social or Referral rows. 4. Include a final "Unassigned custom" or "Other paid" channel with a deliberate rule so nothing silently falls through to Unassigned in the custom group while default channel still shows Paid Search. 5. Mirror critical rules with a RegEx Table or lookup in GTM only if you also need clean values in non-GA4 tags. The channel group reads Analytics dimensions, not your dataLayer variable names. 6. On Shopify, confirm the custom pixel or app preserves UTM parameters on checkout URLs where Shop Pay or wallets strip query strings. Broken UTMs make channel groups lie even when rules are perfect. 7. On WooCommerce, check that order attribution plugins and GA4 tags agree on campaign fields. [WooCommerce order attribution](https://alanvo.com/blog/woocommerce-order-attribution/) can expose first-touch data the GA4 session channel will not match if sessions cross midnight. 8. On Magento and Adobe Commerce, validate Google Ads auto-tagging and manual campaign ids on catalog feeds that deep-link with different query strings per category. 9. Build one exploration: session custom channel group by purchase revenue and transactions. Pin it next to the default channel group view so stakeholders see what changed. 10. If you set a custom primary channel group, record the date and notify anyone using Looker Studio tiles keyed on default channel group only. Google warns that channel groups with a very large number of fields can slow reports. Prefer a few well-ordered channels over fifty micro-segments you never action. ## What breaks when GA4 custom channel groups ecommerce rules fight reality GA4 custom channel groups ecommerce setups break when teams treat retroactive relabeling as a substitute for UTM fixes, or when rule order hides whole campaigns. ![Analytics graphs on a laptop in a dark office](../../images/blog/ga4-custom-channel-groups-ecommerce-3.jpg) The first failure mode is duplicate or missing UTMs on email and SMS. Lifecycle tools love default `utm_source=Klaviyo` while another flow uses `source=newsletter`. Your custom Email channel only catches half the list. Fix the send templates and GTM UTM builder before you add a fifteenth OR clause. The second failure is `(not set)` medium on paid social link-in-bio traffic. Default channel group may call it Organic Social while your custom group expects `medium=paid-social`. Session-level channel dimensions will not match Ads manager until you standardize link parameters or add a rule on source platform where Meta and Google document values. The third failure is cross-domain checkout. A session that starts on `www` and purchases on `checkout` still needs consistent linker or tag configuration so campaign parameters survive. Channel groups cannot infer a campaign that never landed on the session. The fourth failure is comparing custom channel purchase revenue to Google Ads conversion value on the hour. GA4 uses its own attribution and reporting identity settings. Custom channels describe acquisition labels, not Ads last-click credit. Align on [GA4 attribution](https://alanvo.com/blog/ga4-attribution-ecommerce/) before exec reviews. The fifth failure is hitting the two custom group limit on Standard properties, then deleting a group that powered a Looker Studio custom table. Google prompts Analytics 360 users about custom tables tied to deleted groups. Standard users still lose explorations pinned to that dimension. ## How to measure GA4 custom channel groups ecommerce after launch You measure GA4 custom channel groups ecommerce success when purchase revenue by custom channel reconciles with known campaign spend bands and when Unassigned custom traffic shrinks week over week. Run a weekly exploration with rows as your custom channel group, columns as event count for `session_start` and key event count for `purchase`, plus purchase revenue. Compare the same date range using default channel group as a secondary dimension on high-volume channels only. Large deltas mean rule order or UTM gaps, not "GA4 is wrong." Segment by landing page plus custom channel for top SKU categories. Magento layered navigation and Shopify collection ads often send traffic to different paths with the same campaign name. Merchandisers care whether revenue came from category ads or product ads even when medium stays `cpc`. If you export to BigQuery, schedule a query that counts sessions with each custom channel id and sums purchase value where event_name equals purchase. Join to Ads spend outside GA4. The UI exploration is enough for many clients; BigQuery is for when finance wants one CSV. ![Team looking at a dashboard on a wall screen](../../images/blog/ga4-custom-channel-groups-ecommerce-4.jpg) Use [GA4 DebugView](https://alanvo.com/blog/ga4-debugview-tracking/) after changing primary channel group. Trigger a test session from a tagged email link and confirm source, medium, and campaign on the first event. Channel assignment happens from session traffic data, not from purchase event parameters. Track annotation lines in GA4 when you reorder rules or switch primary group. Retroactive reporting helps, but humans still need to know why April looks different from May. ## Related work on this site I ship these channel splits on the same storefronts where we already fixed tags and feeds. On [retail conversion work](https://alanvo.com/work/retail-conversion/), clean acquisition labels were part of making GA4 revenue trustworthy enough for trading meetings. [Their Nibs](https://alanvo.com/work/their-nibs/) needed lifecycle and paid social separated before merchandising could trust session channels beside Shopify's own analytics. [Offporter](https://alanvo.com/work/offporter/) runs multi-channel traffic into WooCommerce, where affiliate and referral rules in a custom group stopped everything landing in Referral. If purchase totals still drift after channel groups look sane, walk backward through ecommerce event design and BigQuery export before you add more channels. ## FAQ ### What are GA4 custom channel groups ecommerce teams allowed to create on Standard? GA4 custom channel groups ecommerce teams on Standard GA4 can create two custom channel groups per property in addition to Google's predefined default group, with up to fifty channels in each group, per Google's [custom channel groups limits table](https://support.google.com/analytics/answer/13051316). Analytics 360 properties allow five custom groups. Plan your media-plan group and your lifecycle group before you use both slots on tests. ### Do GA4 custom channel groups ecommerce reports change historical data? Yes. Google's help center states custom channel groups can apply retroactively in reports and explorations. Sessions you already collected reclassify when rules change, based on stored source, medium, campaign, and related fields. They do not fix missing UTMs retroactively. If historical medium was `(not set)`, no new rule invents a campaign name that was never recorded. ### Can GA4 custom channel groups ecommerce replace default channel group in every report? You can set a custom group as the property primary channel group so future primary channel group values follow your rules, but some reports and integrations still reference default channel group explicitly. Use custom groups as primary dimensions in Acquisition and Explorations, and teach stakeholders which dimension Looker Studio tiles use. Key events paths still do not support custom channel groups as of Google's current documentation. ![Phone and laptop showing the same store metrics](../../images/blog/ga4-custom-channel-groups-ecommerce-5.jpg) ### How do GA4 custom channel groups ecommerce relate to purchase and item reporting? Channel groups classify session acquisition using traffic-source dimensions described in Google's [traffic-source dimensions](https://support.google.com/analytics/answer/15567068) guide. Ecommerce purchase value still comes from `purchase` events and the items array per [Measure ecommerce](https://developers.google.com/analytics/devguides/collection/ga4/ecommerce). In explorations, combine session-scoped custom channel with purchase revenue metrics, or export to BigQuery and join on user pseudo id and timestamp with the usual identity caveats. HTML version: https://alanvo.com/blog/ga4-custom-channel-groups-ecommerce/