gecko-dev/mobile/android/docs/activitystreamtelemetry.rst
Michael Comella 3e9f59b825 Bug 1404460: Add POCKET_ENABLED_TO_LOCALE to asUserPrefs telemetry. r=liuche
After speaking with liuche, we decided it'd be better to add a bit to determine
this rather than combining it with the isPocketEnabled field (which would be
loss of data) or cross-referencing the locale of the submitted event when
checking the Pocket value during telemetry analysis (which is hard to get right
and likely to get out of date).

MozReview-Commit-ID: JKFrdEsEbyp

--HG--
extra : rebase_source : bc20193ca29238cbde5361a840cbd367b492a346
2017-10-02 17:01:10 -07:00

285 lines
9.7 KiB
ReStructuredText

.. -*- Mode: rst; fill-column: 80; -*-
============================
Activity Stream UI Telemetry
============================
Building on top of UI Telemetry, Activity Stream records additional information about events and user context in which they occur.
The ``extras`` field is used for that purpose; additional information is structured as JSON blobs.
Session
=======
Activity Stream events are recorded as part of the "activitystream.1" session.
Global extras
=============
A concept of a "global" extra is meant to support recording certain context information with every event that is being sent, regardless of its type.
``fx_account_present``, values: true, false
Indicates if Firefox Account is currently enabled.
``as_user_preferences``, values: (bit-packed) value of preferences, and related settings, enabled
Each preference is assigned a value that is a unique power of 2, and value of as_user_preferences is the sum of all enabled preferences values.
Some values are taken directly from Android SharedPreferences: these are prefixed with "(SharedPrefs)"". All preferences
measured (with their values) are:
- (SharedPrefs) pref_activitystream_pocket_enabled: 4
- (SharedPrefs) pref_activitystream_visited_enabled: 8
- (SharedPrefs) pref_activitystream_recentbookmarks_enabled: 16
- Is Pocket enabled in the user's current locale: 32
**Important note on Pocket:** A user's ability to override ``pref_activitystream_pocket_enabled`` will be influenced by whether
or not Pocket is shown so when checking that preference, it is also recommended to check whether Pocket is enabled in the user's
current locale. We initially limited the locales that get Pocket recommendations in `bug 1404460`_.
.. _bug 1404460: https://bugzilla.mozilla.org/show_bug.cgi?id=1404460
Extra information available for various event types
===================================================
Action position
---------------
Common to most recorded events is the 0-based ``action_position`` extra. For non-menu interactions it
indicates position of an item being interacted with. For example, click on a third top site of a
second page will have ``action_position = 6``, given that the first page had 4 top sites.
Additionally for Top Site interactions, 0-based ``page_number`` is also recorded.
For menu interactions, or interactions with menu items, it will indicate position of a top site or a
highlight for which the menu is being displayed.
Top Site interactions
---------------------
Three event types are recorded:
1) User clicked on a Top Site: event="loadurl.1", method="listitem"
2) User long-clicked on on a Top Site: event="show.1", method="contextmenu"
3) User swiped left/right (only for Activity Stream topsites): event="action.1", method="list", extras="swipe_forward"/"swipe_back"
For each click event (1/2), in addition to global extras, the following information is recorded:
.. code-block:: js
extras: {
...
"source_type": "topsites",
"source_subtype": "pinned"/"suggested"/"top",
"action_position": number, /* 0-based index of a top site being interacted with */
"page_number": number, /* 0-based index of a page on which top site appears */
}
Subtype indicates a reason an item which is being interacted with appeared in the Top Sites:
- "pinned": a pinned top site, specifically a non-positioned "Activity Stream pinned" site
- "suggested": a suggested top site, one of the default ones displayed when there's not enough browsing history available
- "top": a frecency-based top site, based on browsing history. Neither "pinned" nor "suggested".
**Important note on the suggested source_subtype:** "suggested" will only be returned the first time a user clicks on a
particular suggested site: for all subsequent clicks on this same site, "top" will be returned (assuming the site is
never pinned). The reason is that once a suggested site has been visited once, it becomes part of a user's history and
is no longer suggested.
Top Stories (Pocket) interactions
---------------------------------
Two event types are recorded for row items (links):
1) User clicked on a Story item: event="loadurl.1", method="listitem"
2) User clicked on the menu button: event="show.1", method="contextmenu"
For both event types, in addition to global extras, the following information is recorded:
.. code-block:: js
extras: {
...
"source_type": "pocket",
"action_position": number /* 0-based index of a story being interacted with */
}
For "loadurl.1" event, the following extra information is also recorded:
.. code-block:: js
extras: {
...
"count": number, /* total number of stories displayed */
}
For "show.1" event, the following extra information is also recorded:
.. code-block:: js
extras: {
...
"interaction": "menu_button"/"long_click"
}
When the user opens the context menu with...
- the 3-dot menu, "menu_button" is recorded
- a long click, "long_click" is recorded
One event type is recorded for interaction with the Top Stories section title UI:
1) User clicks on the "MORE" link in the Top Stories section title: event="action.1", method="button"
In addition to global extras, the following information is included:
.. code-block:: js
extras: {
...
"source_type": "pocket",
"item": "link_more"
}
Highlight interactions
----------------------
Two event types are recorded:
1) User clicked on a Highlight: event="loadurl.1", method="listitem"
2) User clicked on the menu button: event="show.1", method="contextmenu"
For both event types, in addition to global extras, the following information is recorded:
.. code-block:: js
extras: {
...
"source_type": "highlights",
"source_subtype": "visited"/"bookmarked",
"action_position": number, /* 0-based index of a highlight being interacted with */
}
Subtype indicates reason an item being which is being interacted with appeared in the Highlights:
- "visited": a website has been visited recently
- "bookmarked": a website has been bookmarked recently
For "loadurl.1" event, the following extra information is also recorded:
.. code-block:: js
extras: {
...
"count": number /* total number of highlights displayed */
}
For "show.1" event, the following extra information is also recorded:
.. code-block:: js
extras: {
...
"interaction": "menu_button"/"long_click"
}
When the user opens the context menu with...
- the 3-dot menu, "menu_button" is recorded
- a long click, "long_click" is recorded
Context Menu interactions
-------------------------
Every interaction with a context menu item is recorded using: event="action.1", method="contextmenu"
For all interactions, in addition to global extras, the following information is recorded:
.. code-block:: js
extras: {
...
"item": string, /* name of a menu item */
"source_type": "topsites"/"highlights",
"source_subtype": string, /* depending on type, one of: "pinned", "suggested", "top", "visited", "bookmarked" */
"action_position": number, /* 0-based index of a top site or highlight item which owns this menu */
}
Possible values for "item" key (names of menu items), in no particular order:
- "share"
- "add_bookmark"
- "remove_bookmark"
- "pin"
- "unpin"
- "copy"
- "homescreen"
- "newtab" (private tab actions are collapsed into "newtab" telemetry due to our privacy guidelines)
- "dismiss"
- "delete"
Learn More interactions
-----------------------
A click on the "Learn more" link is recorded using: event="loadurl.1", method="listitem".
In addition to the global extras, the following information is recorded:
.. code-block:: js
extras: {
"source_type": "learn_more"
}
Full Examples
=============
Following examples of events are here to provide a better feel for the overall shape of telemetry data being recorded.
1) User with an active Firefox Account clicked on a menu button for the third highlight ("visited") [prefs enabled: top-stories, bookmarks, visited] :
::
session="activitystream.1"
event="show.1"
method="contextmenu"
extras="{
'fx_account_present': true,
'as_user_preferences': 28,
'source_type': 'highlights',
'source_subtype': 'visited',
'action_position': 2,
'interaction': 'menu_button'
}"
2) User with no active Firefox Account clicked on a second highlight (recent bookmark), with total of 7 highlights being displayed [prefs enabled: bookmarks] :
::
session="activitystream.1"
event="loadurl.1"
method="listitem"
extras="{
'fx_account_present': false,
'as_user_preferences': 16,
'source_type': 'highlights',
'source_subtype': 'bookmarked'
'action_position': 1,
'count': 7
}"
3) User with an active Firefox Account clicked on a third pinned top site [prefs enabled: (none)] :
::
session="activitystream.1"
event="loadurl.1"
method="listitem"
extras="{
'fx_account_present': true,
'as_user_preferences': 0,
'source_type': 'topsites',
'source_subtype': 'pinned',
'action_position': 2,
'page_number': 0
}"
4) User with an active Firefox Account clicked on a "share" context menu item, which was displayed for a regular top site number 6 [prefs enabled: visited, bookmarks] :
::
session="activitystream.1"
event="action.1"
method="contextmenu"
extras="{
'fx_account_present': true,
'as_user_preferences': 24,
'source_type': 'topsites',
'source_subtype': 'top',
'item': 'share',
'action_position': 5
}"