feat(analytics): enable Google Analytics 4 via docs.json integrations.ga4 - #2267
Draft
GigaHierz wants to merge 1 commit into
Draft
feat(analytics): enable Google Analytics 4 via docs.json integrations.ga4#2267GigaHierz wants to merge 1 commit into
GigaHierz wants to merge 1 commit into
Conversation
….ga4 Refs #2249 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
Author
|
|
This was referenced Aug 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The hole, and the fix
docs.jsonhad no analytics configuration at all ("integrations" in docs.json → falseatbdf40b37; grep forga4|gtm|googleAnalytics|posthog|amplitude|mixpanel|segment|plausible|fathom→ 0 hits), so page analytics were lost when the Mintlify plan changed. This adds Mintlify's documented GA4 block:The measurement ID is not new:
G-0CXEKQ81V2was the docs' GA4 property indocusaurus.config.jsfrom 2021-09-21 (c931a1bf) until the Docusaurus removal on 2025-09-17 (b555aecb). Reusing it keeps the historical series in one property instead of starting a new one. (An older IDG-W2H8BZBELDexisted for one month in 2021-08 and was replaced; not used here.)What this does NOT do / residual risk
G-0CXEKQ81V2. If nobody on the team can access it any more, this ships events into a property we can't read — the ops box below is the check.Judgement calls
Issues
Refs #2249 — closes the code box (
integrations.ga4.measurementIdadded). Still open: GA account ownership confirmed/shared with the DevRel team; Realtime verification after deploy; owner recorded.Stacking / conflicts
Branched off
main, independent of my other open PRs. Touchesdocs.jsontop-level only (lines 10–15); no overlap with navigation edits.Verification evidence
mint broken-linksoutput is pasted in the first comment (run on this head). There is no test seam for a config key in a static-docs repo; mutation testing does not apply — the real check is GA4 Realtime after the preview/production deploy.Remaining ops steps
G-0CXEKQ81V2(Admin → Property details) and share access with the DevRel team; if access is lost, create a new property and swap the IDChecklist
maindocs.jsonparses;mint broken-linksrun on this headG-0CXEKQ81V2? If not, say so and I'll swap in the new ID.