fenix/docs/telemetry.md

# 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](https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/pings.md) component and [documented in the Android Components repository](https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/baseline.md).

## Metrics ping

Fenix creates and tries to send a "baseline" ping. It is defined inside the [`metrics.yaml`](https://github.com/mozilla-mobile/fenix/blob/master/app/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`](https://github.com/mozilla-mobile/fenix/blob/master/app/metrics.yaml) file.

## Activation

Fenix sends an activation ping once, at startup. Further documentation can be found in the [`activation` ping](activation.md) 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`)
Closes #263: Integrate service-glean component. 2019-01-31 17:27:36 +01:00			`# Telemetry`

For #865 - Documents the OpenedApp event 2019-03-13 00:06:36 +01:00			`Fenix uses Mozilla's telemetry service (Glean) and LeanPlum to measure feature performance and engagement.`
Closes #263: Integrate service-glean component. 2019-01-31 17:27:36 +01:00
			`## Baseline ping`

Fixes #983 - Changes broken link 2019-04-04 00:49:19 +02:00			`Fenix creates and tries to send a "baseline" ping when the app goes to the background. This baseline ping is defined by the [Glean](https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/pings.md) component and [documented in the Android Components repository](https://github.com/mozilla-mobile/android-components/blob/master/components/service/glean/docs/pings/baseline.md).`
Documents new telemetry events 2019-03-19 22:58:49 +01:00
			`## Metrics ping`

			Fenix creates and tries to send a "baseline" ping. It is defined inside the [`metrics.yaml`](https://github.com/mozilla-mobile/fenix/blob/master/app/metrics.yaml) file. This ping includes things like wether or not Fenix is currently the default browser.
For #865 - Documents the OpenedApp event 2019-03-13 00:06:36 +01:00
			`## Events`

Addresses metrics nits 2019-03-22 07:05:28 +01:00			Fenix sends event pings that allows us to measure feature performance. These are defined inside the [`metrics.yaml`](https://github.com/mozilla-mobile/fenix/blob/master/app/metrics.yaml) file.

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 16:40:22 +02:00			`## Activation`

			Fenix sends an activation ping once, at startup. Further documentation can be found in the [`activation` ping](activation.md) docs.

Addresses metrics nits 2019-03-22 07:05:28 +01:00			`## 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`)