Add new analytics and performance tracking domains#3716
Merged
Conversation
Add new analytics and performance tracking domains
|
You could block them yourself; |
Contributor
Author
Sorry, perhaps my wording was a bit off; the blacklist was just a metaphor. What I meant was, since there's already a |
Contributor
|
I removed The information should be enough now. |
MkQtS
approved these changes
Jun 11, 2026
github-actions Bot
added a commit
to YW5vbnltb3Vz/domain-list-community
that referenced
this pull request
Jun 12, 2026
* https://github.com/v2fly/domain-list-community: update firebase and `google@cn` (v2fly#3723) Add new analytics and performance tracking domains (v2fly#3716) okx: add okx.ac (v2fly#3720)
github-actions Bot
added a commit
to xinbs/domain-list-community
that referenced
this pull request
Jun 12, 2026
* https://github.com/v2fly/domain-list-community: update firebase and `google@cn` (v2fly#3723) Add new analytics and performance tracking domains (v2fly#3716) okx: add okx.ac (v2fly#3720)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a resubmission and follow-up to my previously closed PR #3692.
I sincerely apologize for the delayed response and for not providing the background information in time. I was quite busy over the past few days, and more importantly, to be responsible to the community, I spent some time testing these blocked domains on my own router to ensure that blocking them wouldn't cause any side effects or issues with the normal operation of Unity-related programs like Unity Editor or Unity Hub. After a few days of testing, I can confirm that there are absolutely no negative impacts.
These domains, which should be blocked due to ads, tracking, or telemetry, are derived directly from the official Unity proxy exception list documentation:
Defining exceptions on a Web proxy (Unity Official Manual)
Below is the table summarizing the domains to be blocked and their exact purposes as described in the official documentation:
analytics.cloud.unity3d.comapi2.amplitude.comconfig.uca.cloud.unity3d.comcdp.cloud.unity3d.comprd-lender.cdp.internal.unity3d.comperf.cloud.unity3d.comperf-events.cloud.unity3d.comdashboard.unityads.unity3d.comI hope this explanation provides enough background context to support merging this PR. If there's any further information needed, please let me know and I will follow up promptly.
Please note that I am fully aware that
domain-list-communityis just a generic list provider; I am merely helping to maintain theAds/trackingcategory.