Hello, What are the problems you see with the beacon being blocked when it comes to extracting value from data? In most instances what we look when deriving insights are ratios. For example: "of the people that saw the red link how many clicked it". In this scenario, with an adequate sample sizes, insights can be extracted without any issues. EventLogging (since it's just an internal logging system)? Addblockers prevent requests to beacons, them being used for internal stats or otherwise (ad serving) so yes, it is pretty reasonable. A beacon does not necessarily imply it is used for adds [1] uses so that it is no longer blacklisted by ad blockers Any url we use it is likely to be blacklisted by blockers that use lists in the absence of it being explicitly whitelisted. So, a naming change will have just a short lived effect. Another way to proceed is the opposite: whitelist the url so it is not blocked by the blockers that -like adblocker- rely on lists. Now (since not all blockers work with lists. Example: Privacy Badger) that is by no means a 100% guarantee that data would not be blocked. Thanks, Nuria [1] https://en.wikipedia.org/wiki/Web_beacon On Tue, Sep 22, 2020 at 10:50 AM Ryan Kaldari <rkaldari(a)wikimedia.org> wrote: