Context
Instrumentation audit (2026-08-11, verified in served HTML and in-browser — no dataLayer, no gtag, no analytics network requests):
| Surface |
Analytics |
nextcommerce.com |
GA4 via GTM (GTM-WJG65C6) |
docs.nextcommerce.com |
none |
developers.nextcommerce.com |
none |
guides.nextcommerce.com |
none |
Docs is a large content surface — and per epic nextcommerce-site#92, it's also where AI crawlers and evaluating agents spend much of their time. Shop Sync onboarding runs through guides. All of it is currently unmeasured: docs traffic can't inform content priorities, and we can't see which docs pages evaluation sessions actually read.
Work
- Decide the measurement approach for the three subdomains — simplest coherent option: the same GTM container → GA4 property
G-MQ16RMT4C6 with cross-domain measurement configured, so a session that moves site → docs → guides stays one session. (Cross-domain config is part of the GA4 admin work in nextcommerce-site#96 — coordinate.)
- Add the container/tag to each build: this repo (docs portal),
developer-docs, and guides.
- Confirm pageviews arrive from all three hostnames and that hostname is usable as a report dimension.
Lighter-weight alternative if GA4 everywhere feels heavy: Cloudflare Web Analytics is already collecting on the apex via zone injection and could be extended to the subdomains — but then docs traffic lives in a different tool than site traffic. Decide once, deliberately.
Done
All three subdomains report into an agreed analytics destination, cross-domain sessions survive the hop from nextcommerce.com, and one report can rank docs/guides pages by traffic.
Context
Instrumentation audit (2026-08-11, verified in served HTML and in-browser — no
dataLayer, nogtag, no analytics network requests):nextcommerce.comGTM-WJG65C6)docs.nextcommerce.comdevelopers.nextcommerce.comguides.nextcommerce.comDocs is a large content surface — and per epic nextcommerce-site#92, it's also where AI crawlers and evaluating agents spend much of their time. Shop Sync onboarding runs through guides. All of it is currently unmeasured: docs traffic can't inform content priorities, and we can't see which docs pages evaluation sessions actually read.
Work
G-MQ16RMT4C6with cross-domain measurement configured, so a session that moves site → docs → guides stays one session. (Cross-domain config is part of the GA4 admin work in nextcommerce-site#96 — coordinate.)developer-docs, andguides.Lighter-weight alternative if GA4 everywhere feels heavy: Cloudflare Web Analytics is already collecting on the apex via zone injection and could be extended to the subdomains — but then docs traffic lives in a different tool than site traffic. Decide once, deliberately.
Done
All three subdomains report into an agreed analytics destination, cross-domain sessions survive the hop from nextcommerce.com, and one report can rank docs/guides pages by traffic.