-
-
Notifications
You must be signed in to change notification settings - Fork 389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Atlassian's Global Analytics Service (GASv3) API in Jira #2358
Comments
Is the issue here that Privacy Badger should be blocking the requests? If so, can you check whether "segment.io" is present in your snitch map at all? (just step 3 here) |
Yes, the issue is that I think Privacy Badger should be blocking those requests. It doesn't look like |
Possibly related: #367 |
Looks like these are POST requests. Related to #794, which is probably about looking into GET request query strings. |
If we were to implement this, we'd probably want to ignore user-initiated form submissions (#2221 (comment)). |
I think this is part of Atlassian's Global Analytics Service (GASv3). https://www.atlassian.com/engineering/cloud-overview
So then this is first party tracking but maybe integrated into third parties on the backend? Does How would Privacy Badger know that these are tracking requests? |
Noticed that some new endpoints appear to be sending data over to
segment.io
when using Jira, which isn't being blocked by privacy badger:https://*.atlassian.net/gateway/api/gasv3/api/v1/p
https://*.atlassian.net/gateway/api/gasv3/api/v1/t
The text was updated successfully, but these errors were encountered: