No campaign ID, but if you look in the ServerSideAccountCreation data, these guys all have the returnto query "article_action=photo-upload" for upload button, "article_action=edit" for edit button, or "article_action=watch" for watchlist star (that's how we've been tracking signups from various features). So there were 1,711 total users who signed up on mobile on the 25th[1] – 156 from upload button, 614 from edit, 384 from the watchlist star, and the remaining 500 or so from the left nav login link. 1. select * from ServerSideAccountCreation_5487345 where event_displayMobile = "1" and timestamp >= '20130725000000' and timestamp <= '20130726000000' On Mon, Jul 29, 2013 at 9:59 AM, Dario Taraborelli < dtaraborelli(a)wikimedia.org&gt; wrote: -- Maryana Pinchuk Product Manager, Wikimedia Foundation wikimediafoundation.org

On Mon, Jul 29, 2013 at 10:26 AM, Maryana Pinchuk &lt;mpinchuk(a)wikimedia.org&gt;wrote;wrote: That is one issue using a campaign identifier would fix. Once the user clicks a signup page link with a campaign name, it's stored in their session cookie, so even if they bounce around it's retained. The only case where it would be lost is if they click another campaign URL after they clicked the first one. -- Steven Walling https://wikimediafoundation.org/

On Mon, Jul 29, 2013 at 6:22 PM, Matthew Flaschen &lt;mflaschen(a)wikimedia.org&gt;wrote;wrote: It does but seems buggy. If I visit http://en.m.wikipedia.org/wiki/Mobilize, click the hamburger, click login (the URL is https://en.m.wikipedia.org/w/index.php ? title=Special:UserLogin &returnto=Mobilize &returntoquery=welcome%3Dyes ), then click Create account, the form URL is https://en.m.wikipedia.org/w/index.php ? title=Special:UserLogin &type=signup &returnto=Mobilize &returntoquery=welcome%3Dyes This is all great. But after I create an account, I end up on a generic account creation page and the Return to is wrong: The user account for SpageTest mobile 0730-7 (talk) has been created. Return to Special:UserLogin<https://en.m.wikipedia.org/wiki/Special:UserLogin> . ... Somehow mobile is ignoring the returnto and returntoquery. Seems like a bug. Maybe CentralAuth/SUL2 changes have affected Mobile's behavior. Maryana, did Mobile intend something cool to happen with welcome=yes ? If I visit http://en.m.wikipedia.org/wiki/Mobilize?welcome=yes nothing awesome happens, AFAICT. That's the generic flow. Wherever you provide your own link to create an account, as Steven said you should set a campaign ?campaign=Maryana42 [1] and you probably want to set the returnto and returntoquery to something interesting [2]. (Currently the mobile site doesn't load the small piece of JS that sets the campaign session cookie, but it could.) [1] https://meta.wikimedia.org/wiki/Research:Account_creation_campaigns [2] https://www.mediawiki.org/wiki/User:S_Page_%28WMF%29/Return_to If anyone in Mobile has questions about this put them in touch with me. Hmm, isn't this Kenan's job now? :-) Cheers, -- =S Page software engineer on E3

On Tue, Jul 30, 2013 at 6:36 PM, S Page &lt;spage(a)wikimedia.org&gt; wrote: Argggh. That shouldn't be happening. There are all sorts of problems with using returntoquery to do campagin-like things – Kaldari was complaining about some of them yesterday. This wasn't one I'd encountered before, but it's pretty awful :( Thanks for catching it! Depends on your definition of cool – that's only supposed to be triggered when you visit the main page after signing up/logging in (which only happens when the mobile site doesn't know what else to do with you), and all it does is display a large "Welcome, $USERNAME!" message at the top of the page (which, of course, a Wikipedian immediately complained about: https://bugzilla.wikimedia.org/show_bug.cgi?id=46442). The fact that this string is now appended to every account creation returnto query, whether it returns to the main page or not, is yet another shortcoming of mobile's pseudo-campaigns. I'm writing up a story for the next iteration (after Wikimania) to switch mobile to real campaign tracking. I guess the first step is getting that campaign session cookie JS onto MobileFrontend, and the second step is to put the devs in touch with you :) Not quite yet, but getting there :) He's CC'ed. -- Maryana Pinchuk Product Manager, Wikimedia Foundation wikimediafoundation.org