snowplow / snowplow/snowplow-javascript-tracker
Browser features are only checked once on tracker initialization
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 590
- Forks
- 232
- Avg merge
- 2h 22m
- Merged PRs (30d)
- 3
Description
So if a user disables cookies partway through their session, cookies will still show up as enabled in all events for that page view. This was presumably originally done to improve performance and save the overhead of looking up that data for every event. But it might be worth deploying a test version with this changed, to see if we notice any differences.
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 at src/js/tracker.js around line 196, where browser features are checked during tracker initialization, and trace how those values are used when events are sent. Confirm the expected behavior when cookies are disabled during an existing page view and verify that browser-feature values in later events reflect the change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- analytics, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100