Bug 1423185 - Update document for the event when user finish first run on-boarding. r?liuche Data review request comment: 1. What questions will you answer with this data? We want to know when the user exit on-boarding. So we can start to A/B testing on other contextual hints. We don't want to overlap them. 2. Why does Mozilla need to answer these questions? Are there benefits for users? We need this information to know if users had done on-boarding 3. What alternative methods did you consider to answer these questions? Why were they not sufficient? I can't think of any. 4. Can current instrumentation answer these questions? No 5. List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories on the found on the Mozilla wiki. I can't find one for Android 6. How long will this data be collected? Choose one of the following: We want to permanently monitor this data. (Joe Cheng) 5. What populations will you measure? All Fennec users 6. Which release channels? All channels 7.Which countries? All countries 8. Which locales? All locales 9. Any other filters? Please describe in detail below. No 10.Please provide a general description of how you will analyze this data. We'd like to use Leanplum to cross-reference those events 11.Where do you intend to share the results of your analysis? We'll use it internally MozReview-Commit-ID: 2s7Hnc97dhp

--- a/mobile/android/docs/mma.rst
+++ b/mobile/android/docs/mma.rst
@@ -146,16 +146,21 @@ List of current Events related data that
 * App start but Fennec is not set as default browser
 {
   "event" : "E_Launch_But_Not_Default_Browser"
 }
 * General app start event
 {
   "event" : "E_Launch_Browser"
 }
+* The user just dismissed on-boarding
+{
+  "event" : "E_Dismiss_Onboarding"
+}
+
 Deep Links:
 Deep links are actions that can point Fennec to open certain pages or load features such as `show bookmark list` or
 `open a SUMO page`. When users see a prompt Leanplum message, they can click the button(s) on it. These buttons can
 trigger the following deep links
 * Link to Set Default Browser settings (firefox://default_browser)
 * Link to specific Add-on page (http://link_to_the_add_on_page)
 * Link to sync signup/sign in (firefox://sign_up)
 * Link to default search engine settings (firefox://preferences_search)