snowplow / snowplow/snowplow-javascript-tracker
Add support for 'sticky' global contexts
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 590
- Forks
- 232
- Avg merge
- 2h 22m
- Merged PRs (30d)
- 3
Description
This idea came after speaking to a customer in Germany who:
- Is relaying all their client-side events to Amplitude
- Would like all of the events following a search, across multiple page loads, to track the original search
We now have global contexts, but of course they are only global within a given page load. (This is different to e.g. mobile app global contexts which are across the whole app lifecycle.)
It would be interesting to use something like localStorage to make it possible for global contexts to survive across page loads - i.e. be 'sticky'.
Contributor guide
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
Start by locating the global-context implementation and the client-side tracker lifecycle, then determine how contexts are currently scoped to a page load. Define the persistence and clearing behavior for a localStorage-backed context, including what should happen across subsequent page loads, before identifying suitable tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- analytics, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100