Generic task for documentation purposes until we can scope this further.

QuickSurveys appears to browsers with ad blockers, but does not register the event in the initiation or response schema (my earlier understanding was that adblockers blocked the tool, thus not displaying the survey at all, but this seems to be incorrect). This issue with ad blockers is a known problem with EventLogging, though the extent of it is unclear.

Externally linking surveys can help us to partially understand the extent of the problem; we're estimating around 10% for readers, to potentially 20% for editors (though this is early results for one survey on one project), where we can't connect response data to an event despite passing a token (indicating that a person saw and responded to a survey invite via QuickSurveys). An underlying issue is that on-wiki (not external) surveys may be serving an unknown amount of surveys which are not being logged. @YLiou_WMF and @TAndic can help to try and estimate the extent with external surveys we've conducted.

Additional information that may be relevant to this ticket based on conversations in working-with-data Slack channel:

• T263049: Avoid extra HTTPS connections for most Event Platform beacons it's possible that having events go to the same domain could help with this
• T401453: FY25-26 SDS2.1.2 Data Reliability - Debugging event loss SDS 2.1.2 is also working on debugging event loss and surveys may be able to help with additional contextualizing information
• From preliminary explorations, it seems that Firefox browsers are more underrepresented in editor surveys when comparing web requests to quicksurvey initiations