This card tracks the work wiring up eventlogging for external link clicks in Wikipedia Zero when the API and client are updated and the EL schema under discussion in T115398 is finalized.
Description
Description
Details
Details
Related Changes in Gerrit:
Customize query in gerrit
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Dbrant | T120116 Better analytics for preloads and Wikipedia Zero support. | |||
| Resolved | • Mholloway | T123748 Add EventLogging in the Android App to track external link clicks per partner | |||
| Declined | Yurik | T115398 For Wikipedia Zero partners - Create ability to measure number of external link clicks per partner | |||
| Resolved | • Mholloway | T119126 Replicate custom Zero exit interstitial behavior in Android App | |||
| Resolved | • Mholloway | T123744 Update ApiZeroBanner to make custom partner info and exit warnings available to the apps |
Event Timeline
Comment Actions
Change 269876 had a related patch set uploaded (by Mholloway):
WIP: Add EventLogging for Wikipedia Zero exit interstitial actions
Comment Actions
Change 270413 had a related patch set uploaded (by Mholloway):
Log action extlink-always when user switches off Zero exit warnings
Comment Actions
Change 270438 had a related patch set uploaded (by Mholloway):
Log extlink action when appropriate
Comment Actions
Change 270438 abandoned by Mholloway:
Log extlink action when appropriate
Reason:
rebase hell, starting over
Comment Actions
Change 270971 had a related patch set uploaded (by Mholloway):
Log extlink action when appropriate
Comment Actions
Change 269876 merged by jenkins-bot:
Implement custom strings and EventLogging for Wikipedia Zero
Comment Actions
Change 270413 merged by jenkins-bot:
Log action extlink-always when user switches off Zero exit warnings
Comment Actions
@Mholloway There is not enough information in this ticket for a third party to be able to test. Please add preconditions and steps to verify if you want this ticket tested by QA.
Comment Actions
Hi @Nicholas.tsg,
Sorry about that. There is some backend setup necessary for testing these and we haven't quite worked out the details on how we want to do that yet for third party testing, but we're working on it. I would say these will be ready for testing by the end of this week at the latest. I'll update again here with instructions when they are ready for testing.