As mentioned at T251464, EventLogging is currently blocked by EasyPrivacy (a popular add-on for ad blocking software) due to EventLogging sending its data to a URL that includes the blacklisted string "beacon/event". In some cases, this makes it difficult or impossible for us to get the analytics data we need to make product decisions, e.g. T240697. Two questions:

Is it reasonable to say that ad blockers should not be blocking EventLogging (since it's just an internal logging system)?
If the answer to #1 is "yes", could we change the URL that EventLogging uses so that it is no longer blacklisted by ad blockers?

Ryan Kaldari (they/them)
Director of Engineering, Product Department
Wikimedia Foundation