What Client Events do we want to Track?
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 14
- Forks
- 0
- Avg merge
- 16h 28m
- Merged PRs (30d)
- 6
Description
+ [ ] Page/Resource requested - solved: https://github.com/dwyl/hits-elixir (_the only difference is that we will be using **PostgreSQL** as the **Data Layer** instead of a log **file** so we will be able to run "**standard**" SQL queries in order to render graphs/charts!_)
+ [ ] DOM Load (page has loaded) - this us to test latency
+ [ ] Scroll up/down/side
+ [ ] Mouse-movement events
+ [ ] Click
+ [ ] Anchor
+ [ ] Internal Link
+ [ ] _External_ Link
+ [ ] ``
+ [ ] Window re-size
+ [ ] Key-up (in forms)
+ [ ] Focus/blur on inputs
+ [ ] Back Button?
+ [ ] Retention?
+ [ ] Actions
+ [ ] Newsletter signup
+ [ ] Registration/Auth
+ [ ] Returning Visitor? `cookies` 🍪 or fingerprint 🖐️ ? https://fingerprint.com/blog/browser-fingerprinting-techniques/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files, tests, or entry points are named. Start by reviewing the linked hits-elixir project and the fingerprinting reference, then turn the listed client events, retention questions, and visitor identification options into an agreed tracking scope; done means the event set and data-layer requirements are decided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, postgresql
- Domain
- analytics, databases, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100