-
Notifications
You must be signed in to change notification settings - Fork 118
Fix Google Analytics issue #316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Someone is attempting to deploy a commit to the recode Team on Vercel. A member of the Team first needs to authorize it. |
Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs. In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps 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 PR 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 20 contributions are eligible for sponsorship 💰 🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨ 📚Your perks for contribution to this community 👇🏻
If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes Google Analytics tracking by correcting a tracking ID and adding Docusaurus gtag configuration. The changes address issue #112 related to Google Analytics functionality.
- Corrected the Google Analytics tracking ID from 'G-W02ZZ2VJYCR' to 'G-W02Z2VJYCR'
- Added gtag configuration to the Docusaurus config file
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
File | Description |
---|---|
static/gtag-init.js | Fixed typo in Google Analytics tracking ID |
docusaurus.config.ts | Added gtag configuration with tracking ID and anonymizeIP setting |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
function gtag() { dataLayer.push(arguments); } | ||
gtag('js', new Date()); | ||
gtag('config', 'G-W02ZZ2VJYCR', { | ||
gtag('config', 'G-W02Z2VJYCR', { |
Copilot
AI
Aug 14, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tracking ID 'G-W02Z2VJYCR' appears to be inconsistent with what might be expected for a Google Analytics measurement ID format. Please verify this is the correct tracking ID as Google Analytics measurement IDs typically follow the pattern G-XXXXXXXXXX with 10 characters after the G-.
gtag('config', 'G-W02Z2VJYCR', { | |
gtag('config', 'G-XXXXXXXXXX', { // <-- Replace G-XXXXXXXXXX with your actual 10-character measurement ID |
Copilot uses AI. Check for mistakes.
customCss: require.resolve("./src/css/custom.css"), | ||
}, | ||
gtag: { | ||
trackingID: 'G-W02Z2VJYCR', |
Copilot
AI
Aug 14, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The tracking ID 'G-W02Z2VJYCR' should match the one used in gtag-init.js. Please ensure both files use the same correct Google Analytics measurement ID for consistent tracking.
trackingID: 'G-W02Z2VJYCR', | |
trackingID: 'G-XXXXXXXXXX', |
Copilot uses AI. Check for mistakes.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Solves: #112
@sanjay-kv
Description
Provide a brief summary of the changes made to the website and the motivation behind them. Include any relevant issues or tickets.
This helps fast tracking your PR and merge it, Check the respective box below.
Fixes # (issue)
Type of Change
Changes Made
Dependencies
Checklist
npm run build
and attached scrrenshot in this PR.