matomo-org / matomo-org/piwik-python-tracker
Support new `ca` tracking parameter for tracking requests that aren't page views
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
See https://github.com/matomo-org/matomo/issues/16569 to learn more about the problem it fixes and visit https://developer.matomo.org/api-reference/tracking-api for more documentation about the new `ca` parameter.
Basically, we should be sending `&ca=1` along any tracking request that isn't a page view. Practically, we should for now only send `&ca=1` along any event and content tracking requests.
The parameter isn't required but it helps for more accurate tracking for edge cases where a user suddenly disables eg an event, goal or ecommerce plugin but still keeps sending these requests. If the parameter is not sent, Matomo would turn the tracking request into a page view and track a page view even though the tracking request should be ignored.
Let me know if there are any questions about this.
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 code that constructs event and content tracking requests, then compare its parameters with the Matomo Tracking API documentation linked in the issue. Done means event and content requests include ca=1 while page-view requests remain unchanged; verify both request types if tests or examples are available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100