Amplify tracking cookies and circumventing adblock
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
I went to the interface today and noticed it places a cookie from the amplify analytics platform and the analytics network requests were being routed through a proxy endpoint, circumventing adblock
I would prefer activity not to be tracked by default
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 TypeScript code that initializes Amplify analytics and the proxy endpoint that routes analytics requests. Trace when the tracking cookie and requests are created, then verify that activity is not tracked by default and analytics requests are no longer routed in a way that circumvents adblock.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- analytics, frontend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100