matomo-org / matomo-org/plugin-TrackingSpamPrevention
Optionally block requests when visitorId is given but user has cookies disabled
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 18
- Forks
- 10
- Avg merge
- 20h 11m
- Merged PRs (30d)
- 1
Description
We know that when cookies are disabled, no visitorId will be set unless it is set manually.
If a user knows they have set the `disableCookies` in the tracking code for all sites, then we could block any tracking request that has a visitorId set as it has to be spam/bots.
When this happens we would also block all future requests for up to 24 hours similar to the max actions logic.
Contributor guide
No contributing guide indexed for this repository
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 the tracking code's disableCookies handling and the existing max-actions logic; no file or test is named in the issue. Done means requests with a visitorId are blocked when cookies are disabled, with subsequent requests blocked for up to 24 hours.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100