Focus android

metric-hub

Pre-defined metrics for focus_android. These metrics are defined in metric-hub

baseline_ping_count

Baseline pings

Counts the number of baseline pings received from each client.

Data Source: baseline

Definition:

COUNT(document_id)

metric_ping_count

Metrics pings

Counts the number of metrics pings received from each client.

Data Source: metrics

Definition:

COUNT(document_id)

first_run_date

First run date

The earliest first-run date reported by each client.

Data Source: baseline

Definition:

MIN(client_info.first_run_date)

active_hours

Active Hours

Total time Firefox was active

Data Source: baseline

Definition:

COALESCE(SUM(metrics.timespan.glean_baseline_duration.value), 0) / 3600.0

days_of_use

Days of use

The number of days in an observation window that clients used the browser.

Data Source: baseline

Definition:

COUNT(DISTINCT DATE(submission_timestamp))

daily_active_users

DAU

The number of unique clients that we received a baseline ping from each day, excluding pings originating from BrowserStack. To be comparable to DAU used for KPI tracking, this metric needs to be aggregated by submission_date. If the metric is NOT aggregated by submission_date, the metric is similar to a "days of use" metric. Note that data retention on focus_android.baseline has historically been only 180 days, which is shorter than other mobile baseline tables. For more details, refer to the DAU description in the Mozilla Data Documentation.

For questions, please contact bochocki@mozilla.com or firefox-kpi@mozilla.com.

Data Source: baseline_v2

Definition:

COUNT(DISTINCT CASE WHEN LOWER(metadata.isp.name) != 'browserstack' THEN client_info.client_id ELSE NULL END)

daily_active_users_v2

Focus Android DAU

This is the official DAU reporting definition. The logic is detailed on the Confluence DAU page and is automatically cross-checked, actively monitored, and change controlled. Whenever possible, this is the preferred DAU reporting definition to use for Focus Android. This metric needs to be aggregated by submission_date. If it is not aggregated by submission_date, it is similar to a "days of use" metric, and not DAU.

For more information, refer to [the DAU description in Confluence](https://mozilla-hub.atlassian.net/wiki/spaces/DATA/pages/314704478/Daily+Active+Users+DAU+Metric).
For questions please contact bochocki@mozilla.com or firefox-kpi@mozilla.com.

Data Source: focus_android_active_users_aggregates_view

Definition:

SUM(dau)

client_level_daily_active_users_v1

Focus Android Client-Level DAU

This metric reports DAU values similar (but not necessarily identical) to the official DAU reporting definition. It's generally preferable to use the official DAU reporting definition when possible; this metric exists only for cases where reporting client_id is required (e.g. for experiments). This metric needs to be aggregated by submission_date. If it is not aggregated by submission_date, it is similar to a "days of use" metric, and not DAU.

For more information, refer to [the DAU description in Confluence](https://mozilla-hub.atlassian.net/wiki/spaces/DATA/pages/314704478/Daily+Active+Users+DAU+Metric).
For questions please contact bochocki@mozilla.com or firefox-kpi@mozilla.com.

Data Source: baseline_v2

Definition:

COUNT(DISTINCT CASE WHEN LOWER(metadata.isp.name) != 'browserstack' THEN client_info.client_id ELSE NULL END)

client_level_daily_active_users_v2

Focus Android Client-Level DAU

This metric reports DAU values similar (but not necessarily identical) to the official DAU reporting definition. It's generally preferable to use the official DAU reporting definition when possible; this metric exists only for cases where reporting client_id is required (e.g. for experiments). This metric needs to be aggregated by submission_date. If it is not aggregated by submission_date, it is similar to a "days of use" metric, and not DAU.

For more information, refer to the DAU description in Confluence. For questions please contact bochocki@mozilla.com or firefox-kpi@mozilla.com.

Data Source: baseline_v2

Definition:

COUNT(DISTINCT CASE WHEN metrics.timespan.glean_baseline_duration.value > 0
                         AND LOWER(metadata.isp.name) != 'browserstack'
                        THEN client_info.client_id
                        ELSE NULL END)

client_level_daily_active_users_v3

Focus Android Client-Level DAU

Client-level DAU. The logic is detailed on the Confluence DAU page and is automatically cross-checked, actively monitored, and change controlled. This metric needs to be aggregated by submission_date. If it is not aggregated by submission_date, it is similar to a "days of use" metric, and not DAU.

Data Source: focus_android_active_users_view

Definition:

COUNTIF(is_dau)

ad_clicks

Ad Clicks

Counts clicks on ads on search engine result pages with a Mozilla partner tag.

Data Source: mobile_search_clients_engines_sources_daily

Definition:

{{agg_sum('ad_click')}}

ad_clicks_organic

Ad Clicks through organic traffic

Counts clicks on ads on search engine result pages that are not tagged with an eligible Mozilla partner code.

Data Source: mobile_search_clients_engines_sources_daily

Definition:

{{agg_sum('ad_click_organic')}}

searches_with_ads_organic

Organic Search With Ads Count

Total number of Organic Search With Ads Counts

Data Source: mobile_search_clients_engines_sources_daily

Definition:

{{agg_sum('search_with_ads_organic')}}

search_count

SAP search count

Number of searches performed through a Search Access Point.

Data Source: mobile_search_clients_engines_sources_daily

Definition:

{{agg_sum('search_count')}}

search_count_imputed

SAP search count (legacy to glean conversion)

Imputed SAP for converting historical search counts from legacy to glean

Data Source: mobile_search_clients_engines_sources_daily

Definition:

ROUND(SUM(IF(submission_date < '2023-01-01', search_count * 0.49, search_count)))

tagged_search_count

Tagged SAP searches

Counts the number of searches a user performed through Firefox's Search Access Points that were submitted with a partner code and were potentially revenue-generating. Learn more in the search data documentation.

Data Source: mobile_search_clients_engines_sources_daily

Definition:

{{agg_sum("tagged_sap")}}

tagged_follow_on_search_count

Tagged follow-on searches

Counts the number of follow-on searches with a Mozilla partner tag. These are additional searches that users performed from a search engine results page after executing a tagged search through a SAP. Learn more in the search data documentation.

Data Source: mobile_search_clients_engines_sources_daily

Definition:

{{agg_sum("tagged_follow_on")}}

searches_with_ads

Search result pages with ads

Counts search result pages served with advertising. Users may not actually see these ads thanks to e.g. ad-blockers. Learn more in the search analysis documentation.

Data Source: mobile_search_clients_engines_sources_daily

Definition:

{{agg_sum("search_with_ads")}}

organic_search_count

Organic searches

Counts organic searches, which are searches that are not performed through a Firefox SAP and which are not monetizable. Learn more in the search data documentation.

Data Source: mobile_search_clients_engines_sources_daily

Definition:

{{agg_sum("organic")}}

engagement_rate_v1

Focus Android Engagement Rate

The Engagement Rate is calculated as the ratio between DAU and MAU. For each day, we use the single-day DAU number and divide it by the MAU corresponding to the 28-day period ending on that day. For OKR reporting, we then calculate a 28-day moving average of this number. More information is provided on the New Profiles, Retention and Engagement Rate Confluence Page.

Data Source: focus_android_engagement_view

Definition:

SUM(dau) / SUM(mau)

retention_rate_v1

Focus Android Retention Rate

The Retention Rate is calculated as the proportion of clients that are active on the 4th week after the metric date.

Data Source: focus_android_retention_view

Definition:

SUM(retained_week_4) / SUM(active_metric_date)

new_profile_retention_rate_v1

Focus Android New Proflie Retention Rate

The New Profile Retention Rate is calculated as the proportion of new profiles that are active on the 4th week after the metric date. More information is provided on the New Profiles, Retention and Engagement Rate Confluence Page.

Data Source: focus_android_retention_view

Definition:

SUM(retained_week_4_new_profiles) / SUM(new_profiles_metric_date)