Direct card views are not tracked, causing incomplete profile analytics

[Ridanshi]

Summary

Analytics tracking appears to record profile-level views while omitting direct card-view events.

As a result, card-level engagement metrics can be significantly underreported.

Affected Files

• analytics.ts
• card.ts

Root Cause

View tracking is implemented at profile-entry points but is not consistently invoked for direct card routes.

Users accessing cards directly bypass analytics collection.

Reproduction

1. Open a profile through its public profile route.
2. Observe analytics updates.
3. Open a card directly through its card URL.
4. Compare analytics behavior.
5. Observe missing card-view tracking.

Expected Behavior

Direct card visits should contribute to analytics.

Actual Behavior

Direct card traffic is omitted.

Why This Is Difficult To Detect

Most testing focuses on profile navigation paths.

Direct-link traffic is often overlooked.

Production Impact

• Underreported engagement
• Inaccurate analytics
• Misleading card performance metrics

Suggested Fix

Track analytics consistently across both profile and card entry points.

Severity

Medium

[Ridanshi]

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.