Summary
LinkID routes visitors from linkid.qzz.io/username/platform to their actual platform profile URL. Currently this redirect happens silently with no tracking — users have no visibility into how many times each of their links has been clicked, which platforms are getting the most traffic, or when those clicks occurred.
Problem
- There is no click tracking on the platform redirect handler (
app/[username]/[platform]/page.tsx).
- Users cannot measure the effectiveness of sharing their LinkID — they don't know if anyone is actually using their
/github or /linkedin links.
- The real-time dashboard mentioned in the README has no analytics dimension.
- Competitor products (Linktree, Bento) all provide click analytics as a baseline feature.
Proposed Solution
Database change (Prisma schema):
model LinkClick {
id String @id @default(cuid())
linkId String
link Link @relation(fields: [linkId], references: [id], onDelete: Cascade)
clickedAt DateTime @default(now())
referrer String?
@@index([linkId])
@@index([clickedAt])
}
Server-side (redirect handler):
Log a click record in the background when the redirect fires — non-blocking, so it does not add latency to the redirect.
Dashboard UI:
- Add a "Clicks" column to the link list showing total click count per link.
- Add a simple chart (using Recharts or a CSS-only bar visualization) showing clicks over the last 7 days per platform.
- Add a total profile views counter.
API:
GET /api/analytics/summary — returns total clicks, clicks per link, and a time-series for the last 7/30 days.
I am happy to implement this including the Prisma migration, API route, and dashboard UI. Could you please assign this issue to me?
Labels: enhancement, feature, analytics, GSSoC 2026
Summary
LinkID routes visitors from
linkid.qzz.io/username/platformto their actual platform profile URL. Currently this redirect happens silently with no tracking — users have no visibility into how many times each of their links has been clicked, which platforms are getting the most traffic, or when those clicks occurred.Problem
app/[username]/[platform]/page.tsx)./githubor/linkedinlinks.Proposed Solution
Database change (Prisma schema):
Server-side (redirect handler):
Log a click record in the background when the redirect fires — non-blocking, so it does not add latency to the redirect.
Dashboard UI:
API:
GET /api/analytics/summary— returns total clicks, clicks per link, and a time-series for the last 7/30 days.I am happy to implement this including the Prisma migration, API route, and dashboard UI. Could you please assign this issue to me?
Labels:
enhancement,feature,analytics,GSSoC 2026