You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Google Tag Manager / Google Analytics is loaded and initialized twice on every page load across the entire website. This results in duplicate pageview events, distorted bounce rates, and inaccurate traffic telemetry.
Root Cause:
In docusaurus.config.ts (lines 106–109), Docusaurus Classic Preset already enables Google Analytics via:
Furthermore, in static/gtag-init.js (line 9), debug_mode is passed as a string ("true" / "false") instead of a boolean (true / false).
Expected behavior
Google Analytics (gtag) should only be injected and initialized once via the Docusaurus Preset Classic configuration, avoiding redundant network requests and duplicate tracking calls.
Thanks for opening this issue! 🎉 We'll look into it as soon as possible, estimated time for response is 5–8 hrs.
Don't raise PR unless assigned to you.
In the meantime, please provide all necessary details and context to your issue — screenshots or videos of your changes help speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊
Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your issue goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.
We are here to help you on this journey of open source. Consistent contributions are eligible for sponsorship 💰
🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨
📚Resources which can help you know more about Github 👇🏻
Hi , I would like to work on this issue. I have gone through the reported problem and understand that Google Analytics is being initialized through both the Docusaurus configuration and manually injected scripts. I would be happy to investigate and fix the duplicate initialization. Could you please assign this issue to me?
Activity
github-actions commentedon Nov 11, 2026
Thanks for opening this issue! 🎉 We'll look into it as soon as possible, estimated time for response is 5–8 hrs.
Don't raise PR unless assigned to you.
In the meantime, please provide all necessary details and context to your issue — screenshots or videos of your changes help speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊
Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your issue goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.
We are here to help you on this journey of open source. Consistent contributions are eligible for sponsorship 💰
🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨
📚Resources which can help you know more about Github 👇🏻
End to End GitHub Beginner Playlist: GitHub Playlist.
Build your GitHub Profile: GitHub Profile Optimisation.
GitHub Handbook for dummies: GitHub Blog for Beginners.
github-actions commentedon Nov 11, 2026
Thanks for opening this issue. To help maintainers review it faster, please add the missing details below:
Khushbu677 commentedon Nov 11, 2026
Hi , I would like to work on this issue. I have gone through the reported problem and understand that Google Analytics is being initialized through both the Docusaurus configuration and manually injected scripts. I would be happy to investigate and fix the duplicate initialization. Could you please assign this issue to me?
github-actions commentedon Nov 11, 2026
👤 Issue assigned to @bobby404-K.
sanjay-kv commentedon Nov 14, 2026
@Khushbu677 there is couple of open issue available please check that this has been done by @bobby404-K
fix(analytics): remove duplicate gtag injection and redundant script (#…
github-actions commentedon Nov 14, 2026
✅ This issue has been closed. Thank you for your contribution!