MMA (Mobile Marketing Automation)

Mozilla wants to engage with users more. MMA is the project for this purpose. When a user performs a certain UI action (or set of UI actions), she will see a prompt and have a chance to interact with it. For example, if a user uses Firefox 10 times a week, but Firefox is not her default browser, we'll prompt the user the next time when she launches our app, and guide her to set us as default browser.

Mozilla is using a third party framework called "Leanplum" in order to achieve this. Leanplum is a San Francisco company, founded in 2012. We put their SDK in our codebase via Carthage.

The SDK is documented at https://www.leanplum.com/docs/android

There are four major components in Leanplum SDK.

Events : Events are fired when users perform certain actions.
User Attributes: User Attributes are set on a per-user basis, and inform us about an aspect of the user.
Deep Links: Actions that users can perform to interact with the Message.
Messages: User Interaction points that we want to engage with users that help them use Firefox better.

An Event or a series of Events plus some User Attributes may trigger a Message, and when the user acts on the Message, a Deep Link may be processed.

Data collection

Who will have Leanplum enabled?

Everyone with Telemetry enabled.

Where does data sent to the Leanplum backend go?

The Leanplum SDK is hard-coded to send data to the endpoint https://www.leanplum.com. The endpoint is defined by com.leanplum.internal.Constants.API_HOST_NAME at https://github.com/Leanplum/Leanplum-Android-SDK/blob/master/AndroidSDKCore/src/main/java/com/leanplum/internal/Constants.java#L32

The user is identified by Leanplum using a random UUID generated by us when Leanplum is initialized for the first time. See: https://github.com/mozilla-mobile/fenix/blob/master/app/src/main/java/org/mozilla/fenix/components/metrics/LeanplumMetricsService.kt This unique identifier is only used by Leanplum and can't be tracked back to any Firefox users.

What data is collected and sent to the Leanplum backend?

The Leanplum SDK collects and sends the following information at various times while the SDK is in use.

Sent every time when an event is triggered:

  "action" -> "track"                   // track: an event is tracked.
  "event" -> "Launch"                   // Used when an event is triggered. e.g. E_Saved_Bookmark.
  "info" -> ""                          // Used when an event is triggered. Basic context associated with the event.
  "value" -> 0.0                        // Used when an event is triggered. Value of that event.
  "messageId" -> 5111602214338560       // Used when an event is triggered. The ID of the message.

Sent when the app starts:

  "action" -> "start"                   // start: Leanplum SDK starts. heartbeat
  "userAttributes" -> "{                // A set of key-value pairs used to describe the user.
    "Focus Installed" -> true           // If Focus for Android is installed.
    "Klar Installed" -> true            // If Klar for Android is installed.
    "Fennec Installed" -> true          // If Fennec for Android is installed.
  }"
  "appId" -> "app_6Ao...."              // Leanplum App ID.
  "clientKey" -> "dev_srwDUNZR...."     // Leanplum client access key.
  "systemName" -> "Android"                 // Fixed String in SDK.
  "locale" -> "zh_TW"                   // System Locale.
  "timezone" -> "Asia/Taipei"           // System Timezone.
  "versionName" -> "55.0a1"             // Fennec version.
  "systemVersion" -> "10.3.1"            // System version.
  "deviceModel" -> "Galaxy"             // System device model.
  "timezoneOffsetSeconds" -> "28800"    // User timezone offset with PST.
  "deviceName" -> "sdaswani-31710"       // System device name.
  "region" -> "(detect)"                // Not used. We strip location so this is will be the default stub value in Leanplum SDK.
  "city" -> "(detect)"                  // Same as above.
  "country" -> "(detect)"               // Same as above.
  "location" -> "(detect)"              // Same as above.
  "newsfeedMessages" -> " size = 0"     // Not used. New Leanplum Inbox message(Leanplum feature) count.
  "includeDefaults" -> "false"          // Not used. Always false.

Sent every time a session is renewed or has a state change:

  "action" -> "heartbeat"               // heartbeat: every 15 minutes when app is in the foreground
                                        // pauseSession: when app goes to background
                                        // resumeSession: when app goes to foreground

Sent for every Message:

  "userId" -> "b13b3c239d01aa7c"        // Set by Fennec, we use random uuid so users are anonymous to Leanplum.
  "deviceId" -> "b13b3c239d01aa7c"      // Same as above.
  "sdkVersion" -> "2.2.2-SNAPSHOT"      // Leanplum SDK version.
  "devMode" -> "true"                   // If the SDK is in developer mode. For official builds, it's false.
  "time" -> "1.497595093902E9"          // System time in second.
  "token" -> "nksZ5pa0R5iegC7wj...."    // Token come from Leanplum backend.

Notes on what data is collected

User Identifier

Since Device ID is a random UUID, Leanplum can't map the device to any know Client ID in Fennec nor Advertising ID.

User Attributes

Key	Description	Data Review
`default_browser`	A string containing the name of the default browser if property of Mozilla or an empty string	#3459
`focus_installed`	A boolean indicating that Firefox Focus is installed	#3459
`klar_installed`	A boolean indicating that Firefox Klar is installed	#3459
`fennec_installed`	A boolean indicating that Fennec is installed	#3459
`fxa_signed_in`	A boolean indicating that the user is signed in to FxA	#4568
`fxa_has_synced_items`	A boolean indicating that the user has opted to sync at least one category of items with FxA	#4568
`search_widget_installed`	A boolean indicating that the user has at least one search widget placed on the home screen	#4694

Events

Most of the Leanplum events can be mapped to a single combination of Telemetry event (Event+Method+Extra). Some events are not collected in Mozilla Telemetry. This will be addressed separately in each campaign review. There are three elements that are used for each event. They are: event name, value(default: 0.0), and info(default: ""). Default value for event value is 0.0. Default value for event info is empty string.

Here is the list of current Events sent, which can be found here in the code base: https://github.com/mozilla-mobile/fenix/blob/master/app/src/main/java/org/mozilla/fenix/components/metrics/LeanplumMetricsService.kt

Event	Description	Data Review
`E_Opened_App_FirstRun`	The first launch after install	#3459
`E_Opened_App`	Whenever the App is launched.	#3459
`E_Interact_With_Search_URL_Area`	The user interacts with search url area.	#3459
`E_Opened_Bookmark`	The user opened a bookmark	#3632
`E_Add_Bookmark`	The user added a bookmark	#3632
`E_Remove_Bookmark`	The user removed a bookmark	#3632
`E_Collection_Created`	The user created a new collection	#4626
`E_Collection_Tab_Opened`	The user opened a tab from a previously created collection	#4626
`E_Sign_In_FxA`	The user successfully signed in to FxA	#4626
`E_Sign_Out_FxA`	The user successfully signed out of FxA	#4626
`E_Cleared_Private_Data`	The user cleared one or many types of private data	#4626
`E_Dismissed_Onboarding`	The user finished onboarding. Could be triggered by pressing "start browsing," opening settings, or invoking a search.	#3459

Deep links

Deep links are hooks utilized by marketing to direct users to certain portions of the application through a link. They can also be invoked by other applications or even users directly to access specific screens quickly.

Here is the list of current deep links available, which can be found here in the code base: https://github.com/mozilla-mobile/fenix/blob/master/app/src/main/AndroidManifest.xml

Deep link	Description
`fenix://home`	Opens to the Fenix home screen
`fenix://settings`	Opens to the top level settings screen
`fenix://turn_on_sync`	Opens to the turn on sync screen. Only valid if the user is not signed in to FxA
`fenix://settings_search_engine`	Opens to the search engine settings screen
`fenix://settings_accessibility`	Opens to the accessibility settings screen
`fenix://settings_delete_browsing_data`	Opens to the delete browsing data settings screen
`fenix://enable_private_browsing`	Opens to the Fenix home screen and enables private browsing
`fenix://open?url={DESIRED_URL}`	Creates a new tab, opens to the browser screen and loads the {DESIRED_URL}
`fenix://make_default_browser`	Opens to the Android default apps settings screen. Only works on Android API >=24

Messages

Messages are in-app prompts to the user from Leanplum. The user interaction of that prompt will be sent to the Leanplum backend (such as "Accept" or "Show") to track overall engagement with the Message. The Message is downloaded from Leanplum when the Leanplum SDK is initialized at App start, assuming the fulfillment criteria for the Message is met. As mentioned before, the fulfillment criteria is a set of required Events and User Attributes. The fulfillment criteria are set in the Leanplum backend.

We currently don't have any messages planned for Firefox Preview

13 KiB Raw Blame History