-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
Revisit gigya.com blocking rules? #169
Labels
Comments
@timtucker Sorry for the late reply. I will take a look at this issue later, thanks for providing the info. |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Submit Form
Issue(s):
Type
x
in between[ ]
and make sure there isn't any space between brackets. Example; for Your Selected Issue(s), type like this -[x]
You can select more than one category of issues if you need to!
Domain(s):
If you are submitting this issue for whitelist/blacklist issue, send me the domain(s) for whitelisting/blacklisting here. Kindly use the Code Tag to prevent tracking.
Details:
You can attach any screen shot or log of the issue or advert, this will help to highlight it.
As of January 2021, SAP retired the tracking functionality from their Gigya product (Signals / Counters) along with all their "social engagement" functionality, which mostly just leaves their login & user management functionality.
From quick testing, our site uses their SDK for logins and I'm no longer seeing the calls to the counters domains / endpoints. The remaining blocking rules for gigya.com could probably be revisited.
See this announcement from SAP:
https://help.sap.com/viewer/8b8d6fffe113457094a17701f63e3d6a/GIGYA/en-US/4172960b70b21014bbc5a10ce4041860.html
The text was updated successfully, but these errors were encountered: