DB schema for card views and platform clicks

[ShantKhatri]

Summary

Set up the two core tables analytics is built on: card_view and platform_click.

Contexts

This is the foundation for every other analytics issue. Needs to support hashed, non-reversible session tokens so no individual viewer is ever identifiable.

Tasks

• Create card_view table (id, card_id, session_token, source, event_id, timestamp)
• Create platform_click table (id, card_id, platform, session_token, timestamp)
• Add indexes on card_id and timestamp for both tables
• Define what counts as a "unique view" and document it

Acceptance Criteria

• Migrations run cleanly up and down
• Schema reviewed against privacy note (no reversible tokens)
• Tests added
• docs updated

Area

backend

[github-actions]

Hi @ShantKhatri,

Thanks for opening this issue.

Please reply with one of the following areas so the issue can be routed to the appropriate team member:

- /backend
- /web
- /mobile
- /devops

Once an area is selected, the corresponding label will be added automatically.