GTM. Zones for multi-brand retail. Share one container across storefronts.

What this means for your store

Copy-pasting the same consent and GA4 setup into five brand containers is how Measurement IDs end up on the wrong domain. GTM zones attach child containers to a parent workspace: each brand zone loads only its tags and variables, while shared policies - consent, base GA4 config, internal traffic filters - live in the parent. One governance path, less drift across storefronts.

Scenario on a real storefront

A US apparel group runs three Shopify Plus stores under one holding company. Parent GTM holds consent and shared triggers; each brand zone gets its own Measurement ID and paid-social folder:

Parent container GTM-PARENT
  Zone: Brand A → child GTM-BRANDA
  Zone: Brand B → child GTM-BRANDB
  Zone: Brand C → child GTM-BRANDC

Parent tag: Consent Initialization (All Pages, all zones)
Zone Brand A tag: GA4 Configuration → G-AAAA
Zone Brand B tag: GA4 Configuration → G-BBBB

// Child containers publish independently; parent references latest approved version

What to do next

• Keep shared consent logic in the parent so GDPR and US state opt-out rules stay consistent across brands.
• Name zones brand + environment (brand-a-prod) - vague labels cause wrong IDs in production.
• Document the dataLayer contract each zone expects; one brand's checkout rewrite should not break another's purchase event.

Bottom line

Zones scale GTM for multi-brand retail without three unrelated containers. Centralize governance in the parent; let each brand own its conversion and media tags.