snowplow / snowplow/snowplow-javascript-tracker
Support disable standard contexts at event-level
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 590
- Forks
- 232
- Avg merge
- 2h 22m
- Merged PRs (30d)
- 3
Description
What I have in mind is an argument in the event methods that disable standard contexts being sent with that event.
It would be useful to only send standard contexts with their relevant events, from a volume management point of view.
Additionally, in an implementation where there's a disconnect between the data analytics/BI team and the implementation team, the data would be simpler to consume if contexts were disabled where they aren't required.
(In other words, it would be useful to set up your tracking such that each event is sent with only those contexts which relate to it - especially where you've got a bigger team/distance between implementing tracking and consuming data)
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 event methods in the TypeScript tracker and reviewing how standard contexts are currently attached. Define the event-level control described in the issue and verify that contexts can be omitted for selected events while existing event behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100