[jdx]

Summary

• Adds the Google tag manager script to the shared VitePress head configuration.
• Configures measurement ID G-WD1RRC0F8C so the docs site includes analytics on every page.

Validation

• npm run docs:build

Note: the docs worktree did not have node_modules, so I installed the declared docs dependency with npm install --no-save --no-package-lock to run the build, then removed generated docs/node_modules and docs/.vitepress/dist before committing.

---

Note

Low Risk
Low risk: docs-only change that injects third-party analytics scripts; main risk is privacy/compliance and any unintended script loading impact on the docs site.

Overview
Adds Google Analytics tracking to the docs site by injecting the gtag.js loader and inline gtag('config', 'G-WD1RRC0F8C') initialization into the shared VitePress head config, enabling page-wide analytics on every docs page.

^{Reviewed by Cursor Bugbot for commit 3584219. Bugbot is set up for automated code reviews on this repo. Configure here.}

[greptile-apps]

Greptile Summary

This PR adds Google Analytics 4 (GA4) tracking to the aube docs site by inserting the standard gtag.js snippet into VitePress's shared head configuration with measurement ID G-WD1RRC0F8C. The two-part snippet — an async external script loader and an inline initialization block — follows the canonical GA4 pattern and integrates cleanly into the existing docs/.vitepress/config.mts.

• The VitePress head tuple format ([tag, attrs, content]) is used correctly for both the external and inline scripts.
• The async: \"\" attribute on the loader script follows the correct VitePress convention for boolean HTML attributes.
• The measurement ID is consistent between the loader URL and the gtag('config', ...) call.
• No functional regressions to existing config sections (favicon, manifest, theme-color, nav, sidebar) are introduced.

Confidence Score: 5/5

Safe to merge — change is a well-formed, standard GA4 integration with no functional risk to the docs build.

The snippet exactly matches the canonical GA4 pattern, measurement IDs are consistent across both script elements, the VitePress head tuple format is used correctly, and the change is scoped to a single config file with no logic impact.

No files require special attention.

Important Files Changed

Filename	Overview
docs/.vitepress/config.mts	Adds standard GA4 gtag.js snippet (external loader + inline init) to the VitePress head array; implementation is correct and consistent.

Sequence Diagram

sequenceDiagram
    participant Browser
    participant GTM as gtag.js CDN
    participant GA as Google Analytics

    Browser->>GTM: GET googletagmanager.com/gtag/js?id=G-WD1RRC0F8C (async)
    GTM-->>Browser: gtag library
    Browser->>Browser: execute inline init script
    Browser->>GA: gtag('config', 'G-WD1RRC0F8C') → page_view event
    GA-->>Browser: 200 OK (beacon)

Loading

_{Reviews (1): Last reviewed commit: "add google analytics tag" | Re-trigger Greptile}