fenix/docs/telemetry.md
Alessio Placitelli 0d82431195 Generate the activation ping and send it with Glean (#1707)
This fetches the Google Advertising ID, salts it and
then applies hashing before sending a ping with it,
at startup. Hashing and salting are used in order
to prevent ourselves to correlate advertising IDs
from the same user running different products we
own off a single device. We will never send the
client_id and the Google Advertising ID in the same
ping.
2019-05-03 09:40:21 -05:00

1.4 KiB

Telemetry

Fenix uses Mozilla's telemetry service (Glean) and LeanPlum to measure feature performance and engagement.

Baseline ping

Fenix creates and tries to send a "baseline" ping when the app goes to the background. This baseline ping is defined by the Glean component and documented in the Android Components repository.

Metrics ping

Fenix creates and tries to send a "baseline" ping. It is defined inside the metrics.yaml file. This ping includes things like wether or not Fenix is currently the default browser.

Events

Fenix sends event pings that allows us to measure feature performance. These are defined inside the metrics.yaml file.

Activation

Fenix sends an activation ping once, at startup. Further documentation can be found in the activation ping docs.

Leanplum Events

Event Leanplum Key extras
OpenedApp E_Opened_App source*
  • source: The method used to open Fenix (For exmaple: app_icon, custom_tab or link)