Description
Can Special:AllEvents be added to the allowlist used in the pageview definition to obtain the benefits of using the pageview pipeline on that page?
Context: Campaigns-Product would like to measure pageviews and referrals on the Event list (T365407). Specifically, they need pageviews to the event list page on those wikis where they're currently deployed and page views from the event list page to the individual event pages such as Desafío Uruguay. Right now, there’s no data available out of the box for Special:AllEvents (T240676).
We're discussing tracking event list pageviews as part of planning for getting the campaigns-product team setup with a Superset dashboard (T365404). Note: in the next fiscal year the team will be working on/with wiki project pages and they will also need pageviews and referral traffic data on those pages (to/from the event list and generally).
Completion checklist
(At any point, just ask for help)
- Add allevents to this list per this request
- Add unit tests by adding new lines in the pageview test data, use examples like this to sanity check the change
- (somewhat optional) to be safe: do a side-by-side comparison
- Build refinery-source locally
- understand the way that webrequest refine runs the pageview UDF
- copy the custom jars you just built and need to run the pageview UDF to a statXXXX machine
- run the new pageview UDF and the old one over an hour of wmf_raw.webrequest, looking for any discrepancies
- Merge and Deploy Refinery Source (get review from Data Engineering too)
- Update the Airflow job to point to the new Refinery Source version (add a new artifact and change this reference)
- Merge and Deploy Airflow