Brad, I used the "loginCTA" campaign data just a couple weeks ago to track the effects of a change to the design of the call to action on Special:UserLogin.[1] Since the Editing department is (theoretically at least) responsible for accounts and signups, I imagine I'll have reasons to use it in the future as well. So I definitely vote for keeping it. It's not critical data, though, so if it makes more sense to put the instrumentation back in next week's train, that's fine. (I went on vacation last Thursday and only got back today, so I didn't have a chance to see this and comment before the patch got merged.) [1]: https://phabricator.wikimedia.org/T126307#2303154 On Tue, May 31, 2016 at 12:49 PM, Steven Walling &lt;steven.walling(a)gmail.com&gt; wrote: -- Neil P. Quinn <https://meta.wikimedia.org/wiki/User:Neil_P._Quinn-WMF>, product analyst Wikimedia Foundation

Ah, I had understood from your initial message that it wouldn't be hard keep it and you'd be willing to do so as long as someone found it useful. We can continue the discussion on Phabricator. [1] [1]: https://phabricator.wikimedia.org/T136727 On Wed, Jun 1, 2016 at 11:59 AM, Brad Jorsch (Anomie) &lt;bjorsch(a)wikimedia.org > On Wed, Jun 1, 2016 at 1:40 PM, Neil P. Quinn &lt;nquinn(a)wikimedia.org&gt; > >> I used the "loginCTA" campaign data just a couple weeks ago to track the >> effects of a change to the design of the call to action on >> Special:UserLogin.[1] Since the Editing department is (theoretically at >> least) responsible for accounts and signups, I imagine I'll have reasons to >> use it in the future as well. So I definitely vote for keeping it. >> >> It's not critical data, though, so if it makes more sense to put the >> instrumentation back in next week's train, that's fine. >> > > To put the campaign back, someone will have to figure out a good way to > let an extension mess with the link in > LoginSignupSpecialPage::getAuthForm(). Options include > > - Sticking a new hook in there to mess with the link and/or the HTML. > - Rearranging the code so it's done as an HTMLInfoField instead of > being appended as HTML using HTMLForm->addFooterText(), so you can use the > existing 'AuthChangeFormFields' hook to mess with it. > > > -- > Brad Jorsch (Anomie) > Senior Software Engineer > Wikimedia Foundation > -- Neil P. Quinn <https://meta.wikimedia.org/wiki/User:Neil_P._Quinn-WMF>, product analyst Wikimedia Foundation