Direct card views are not tracked, causing incomplete profile analytics #495

Activity

1. github-project-automation

   added this to DevCardon Jun 6, 2026
2. github-project-automation

   moved this to Todo in DevCardon Jun 6, 2026
3. Ridanshi commented on Jun 6, 2026

   

   Ridanshi

   on Jun 6, 2026

   ContributorAuthor

   More actions

   I investigated this issue and would like to work on it.

   The current analytics implementation appears to track profile views without consistently recording direct card visits.

   I plan to:

   • review analytics collection paths
   • preserve existing reporting behavior
   • add tracking for direct card access routes
   • add regression coverage for analytics consistency

   Please assign this issue to me.
4. yachikadev commented on Jun 20, 2026

   

   yachikadev

   on Jun 20, 2026

   Contributor

   More actions

   thanks for flagging this — I dug into the code and can confirm the exact root cause:

   apps/backend/src/services/publicService.ts has three functions serving card/profile data, and only two of them record analytics:

   • getPublicProfile() (GET /api/u/:username) — creates a cardView record
   • getUserCard() (GET /api/u/:username/card/:cardId) — creates a cardView record
   • getCardById() (GET /api/u/card/:cardId — the direct shared-card link, called by apps/web/src/pages/CardPage.tsx) — only fetches and returns the card, no cardView.create() call at all

   // publicService.ts, lines 60-63
   export async function getCardById(app: FastifyInstance, cardId: string): Promise<any> {
     const card = await app.prisma.card.findUnique({ where: { id: cardId }, include: { user: true, cardLinks: { include: { platformLink: true }, orderBy: { displayOrder: 'asc' } } } })
     return card
   }

   So this isn't a general "profile vs card" gap — it's specifically this one function missing the tracking + self-view-blocking logic that the other two already have.

   Would love to take this on if it's still unassigned — happy to add the fix + a test in apps/backend/src/__tests__/public.test.ts covering both the tracked and self-view-blocked cases, following the existing pattern. Can I get assigned?
5. Ridanshi

   added a commit that references this issue on Jun 21, 2026

   fix(analytics): track CardView events on direct card route

   ...

   This issue will close once commit 6b44b73 is merged into the 'main' branch.

   6b44b73