feat(insights): top traffic sources per event in Builder Insights#4222
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
8 tasks
navillanueva
changed the title
alejandro99so
approved these changes
May 22, 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
2 participants
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.
What
Adds a Top traffic sources (90d) column to the Event history table on the Builder Insights dashboard (
/profile?tab=insights). Each row shows the top-3 channels that drove visitors to that hackathon, with visitor counts.How
getTopHackathonTrafficSourcesBatchinserver/services/hackathonTrafficSources.ts— single query returns top-N sources per hackathon using ClickHouseLIMIT N BY hackathon_id.utm_source / utm_campaigngranularity (andutm_contentif you want per-poster). Organic X/LinkedIn bucket toX (untagged)/LinkedIn (untagged)— those platforms strip the originating tweet/post from the Referer header so per-account attribution isn't possible without UTMs.\$directsentinel (no referrer + no real UTM) is excluded at the WHERE level so it never competes for a top-3 slot./hackathons/<uuid>or/events/<uuid>) — no new client-side instrumentation needed.