Page MenuHomePhabricator

Update Android account creation analytics
Closed, DeclinedPublic

Description

Proposal for MobileWikiAppCreateAccount2 (no sampling) in order to be able to answer the following questions:

  • whether people have made accounts through the app
  • verify that the account was made through the Android app specifically
  • whether people continue using these accounts in order to edit (both through Android app or on web)

Spec draft:

  • last_status
    • example values:
      • "start" if user went into "Create an account" screen but then cancelled
      • "captcha" if user saw a captcha but did not finish the process
      • "finish" if user successfully created an account
    • Notes: "start" and "captcha" are different steps at which the user abandoned the process
  • source
    • how user came to the process
    • examples:
      • "rl-sync" if they tried to enable reading list syncing
      • "menu"
      • "onboarding"
      • any other possible values???
  • (maybe) user_id of the newly created account, may be null if user did not complete account creation process
  • provided_email: a Boolean flag indicating whether the user provided an email address when signing up
  • app_install_id
  • client_dt

Instead of the user_id field, it would actually be a lot better to store information in the [[ https://www.mediawiki.org/wiki/Manual:User_properties_table | user_properties table ]] indicating that the account was created on the Android app. The Growth team uses this table to store survey responses, so maybe we could also?

Event Timeline

Question for @Dbrant: would the app be able to store data in [user_properties table](https://www.mediawiki.org/wiki/Manual:User_properties_table)? Might need to be a separate API call after an account is created since we probably can't include that data in the account creation API call. Would rather do that than store a user_id in event data.

The Growth team uses that table to store survey responses so the idea here is to use it to store some kind of app-analytics => account created via android app property-value pair (with the idea that maybe iOS would be interested in doing the same) to enable us to analyze editing activity of users who created their account through the app specifically.

@mpopov We can theoretically make an API call and set a new userjs-option that contains the data, e.g. userjs-accountcreatesource = Android v270

However, that table is per-wiki, so is that really any better than providing the user_id in the event?

(unless this is a different table that I'm not aware of? Which API were you thinking this would use?)

I need to do some investigation as part of T226565 because there's a chance we may already have relevant data after all and may not need this work to be done.

Looks like we can ditch this. What we already have is good enough.