snowplow / snowplow/snowplow-javascript-tracker
Make handling of proxies non-lossy
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 590
- Forks
- 232
- Avg merge
- 2h 22m
- Merged PRs (30d)
- 3
Description
At the moment, our handling of proxies is lossy.
It's lossy because we report someone viewing a Google Brazilian translation of www.football.com as simply a direct page view of www.football.com which is not the whole truth.
It would be nice to log the proxy URL and the original URL; and include anything we have figured out about the proxy (e.g. this is a Google BR proxy translating en_US to br_PT).
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 tracing how the tracker identifies and records page views and proxy URLs. Determine where the proxy URL, original URL, and any available proxy details can be retained without losing information; done means proxy-mediated views report both URLs and known proxy metadata rather than only the destination page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- analytics, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100