🛍️ WooCommerce Subdomain Architecture

How to Setup GA4 Cross-Subdomain Tracking (blog.domain.com to shop.domain.com)

By Dimsquid EngineeringPublished Aug 5, 20268 min read

Many high-growth e-commerce brands host their main blog or content hub on blog.yourbrand.com and run their WooCommerce store on shop.yourbrand.com. While both subdomains share a root domain, web browsers and Google Analytics 4 can still split user sessions if cross-subdomain parameters and cookie domain flags are misconfigured.

1. Why Subdomains Suffer Session Fragmentation

By default, when GA4 initializes, it sets the cookie domain to auto. In theory, this writes the _ga cookie on the root domain (.yourbrand.com). However, if your WordPress blog or WooCommerce setup uses third-party payment gateways, iFrames, or external cart redirects, session attribution drops back to (direct) / (none).

2. Passing Meta & TikTok Parameters Across WooCommerce Subdomains

GA4 is only half the battle. If a user clicks a Facebook Ad targeting blog.yourbrand.com, Meta sets _fbc on the blog subdomain. When the user navigates over to shop.yourbrand.com to complete checkout, the Meta Pixel on WooCommerce requires explicit fbclid URL parameter forwarding.

⚡ Pro Feature

3. Pro Plan: Multi-Subdomain Support Engine

GA4 Linker (Pro Plan) allows you to input multiple custom WooCommerce subdomains (e.g. blog.brand.com, shop.brand.com), forwarding _gl, fbclid, and ttclid automatically.

Get Pro Plan ($149/yr) →