Erin has use cases here:
This task will be rewritten as we talk with analytics engineering and get more info.
We are interested in storing banner history event data in some form within the Fundraising data ecosystem so that we can blend it with other elements of fundraising data for analysis.
Currently, this data is stored within Hive. It has been whitelisted by the Analytics Engineering team to allow for storage longer than 90 days and is kept in the event_sanitized.centralnoticebannerhistory schema.
Data we are interested in accessing internally is documented here: https://meta.wikimedia.org/wiki/Schema:CentralNoticeBannerHistory Particularly within the "l" property. This information can be combined with FR-internal data to answer interesting questions such as outlined in an old blog post, here https://blog.wikimedia.org/2017/10/03/fundraising-banner-limit/
Additional information related to banner interactions which would be helpful to have internally are banner status codes: https://www.mediawiki.org/wiki/Extension:CentralNotice/Statuses,_reasons_and_status_codes
(It's possible these could/should be two separate asks).