Skip to content

Conversation

@uiuxxx
Copy link
Contributor

@uiuxxx uiuxxx commented Oct 16, 2025

  • Adds Fathom tracking to navigational elements and items on Pool List page of the app.

@vercel
Copy link

vercel bot commented Oct 16, 2025

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

Project Deployment Preview Comments Updated (UTC)
mono-beets-test-v3 Ready Ready Preview Comment Oct 21, 2025 4:28pm
mono-beets-v3 Ready Ready Preview Comment Oct 21, 2025 4:28pm
mono-cow-v3 Ready Ready Preview Comment Oct 21, 2025 4:28pm
mono-frontend-v3 Ready Ready Preview Comment Oct 21, 2025 4:28pm
mono-test-v3 Ready Ready Preview Comment Oct 21, 2025 4:28pm

💡 Enable Vercel Agent with $100 free credit for automated AI reviews


return (
<Button ref={ref} {...props} display="flex" gap="2" variant="tertiary">
<Button
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The filters button doesn't seem to be working after this change, the handler function probably just eats the click event.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed here: 22f7c8b

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know why we have to do that (events should propagate unless otherwise stated), but it should do for now.

}, [isOpen, onClose])

const handleToggle = () => {
trackEvent(AnalyticsEvent.ClickNavBuild)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The track event code does not seem to differentiate between prod and the dev environments. That could probably skew the results a little.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In Fathom.tsx on Line 60, it looks like Fathom is only tracking these domains, so I think dev environments are not being tracked, right? If not, I could use some help here.

cs 2025-10-21 at 17 07 03@2x

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see there is some code before that which mades it only run on prod:

// Optional: Only track on production; remove these two lines if you want to track other environments
if (!isProd) return

The zen.balancer.fi does not point to anything though, we can remove it.

}) {
const { linkColorFor } = useNav()

const handleLinkClick = (analyticsEvent?: string) => {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some of the code where we are tracking events is shared with Beets, do we want to track Beets events?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch. We definitely do not want to track events from Beets.

I have updated the code to only track on Balancer events here :3c7a918

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is probably better to wrap the trackEvent function with our own one, so we don't have to add the if (isBalancer) ... logic everywhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants