fix: analytics tracking

[dk-a-dev]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
dkdev	Ready	Preview, Comment	Feb 27, 2026 10:35am

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the application's analytics capabilities by integrating Vercel Analytics to track page views. It ensures that each navigation event, triggered by changes in the URL hash, is recorded, providing valuable data on user interaction and route transitions.

Highlights

• Vercel Analytics Integration: The track function from @vercel/analytics has been imported to enable custom event tracking.
• Pageview Tracking Implemented: Pageview events are now tracked using track("Pageview", ...) whenever the URL hash changes, capturing navigation within the application.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• src/App.tsx
  • Imported the track function from @vercel/analytics.
  • Added a call to track within the handleHashChange function to log pageview events with the current path.

Activity

• No specific activity has been recorded for this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces analytics tracking for page views, which is a great addition. The implementation correctly hooks into hash changes to detect navigation in the single-page application. My review includes a suggestion to normalize the path sent to the analytics service. By using a canonical path for each page, you can ensure data consistency and avoid fragmentation in your analytics reports, leading to more accurate insights.

[gemini-code-assist]

For analytics consistency, it's better to track a canonical path for each page. The current implementation might send different paths for the same page (e.g., / and /#about for the "About" page, or paths with different casing like /#About).

Using the newPage variable, which holds the normalized page name, to construct a canonical path would ensure that each page view is attributed to a consistent URL in your analytics. This prevents data fragmentation and provides a clearer picture of page performance.

Suggested change

	track("Pageview", { path: window.location.pathname + window.location.hash });
	track("Pageview", { path: `${window.location.pathname}#${newPage}` });