Skip to content

Firefox ios

metric-hub

Pre-defined metrics for firefox_ios. 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. 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

Firefox iOS DAU

This is the official DAU reporting definition. The logic is defined in bigquery-etl and is automatically cross-checked, actively monitored, and change controlled. Whenever possible, this is the preferred DAU reporting definition to use for Firefox iOS. 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: active_users_aggregates_v1

Definition: 
SUM(dau)

client_level_daily_active_users_v1

Firefox iOS 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 the Mozilla Data Documentation](https://docs.telemetry.mozilla.org/concepts/terminology.html#dau).
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

Firefox iOS 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)

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')}}

ad_click_organic

Organic Ad Click Count

Total number of Organic Ad Click Counts

Data Source: mobile_search_clients_engines_sources_daily

Definition: 
{{agg_sum('ad_click_organic')}}

search_count

SAP searches

Counts the number of searches a user performed through Firefox's Search Access Points. Learn more in the search data documentation.

Data Source: mobile_search_clients_engines_sources_daily

Definition: 
{{agg_sum('search_count')}}

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')}}

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')}}

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

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')}}

spoc_tiles_impressions

Sponsored Tiles Impressions

Number of times Contile Sponsored Tiles are shown.

Data Source: events

Definition: 
COALESCE(COUNTIF(
          event.category = 'top_site'
          AND event.name = 'contile_impression'
      ),0)

spoc_tiles_clicks

Sponsored Tiles Clicks

Number of times user clicked a Contile Sponsored Tile.

Data Source: events

Definition: 
COALESCE(COUNTIF(
          event.category = 'top_site'
          AND event.name = 'contile_click'
      ),0)

spoc_tiles_preference_toggled

Sponsored Tiles Preference Toggled

Number of times Contile Sponsored Tiles setting is flipped.

Data Source: events

Definition: 
COALESCE(SUM(CASE WHEN
          event.category = 'preferences'
          AND event.name = 'changed'
          AND `mozfun.map.get_key`(event.extra, 'preference') = 'sponsoredTiles'
    THEN 1 ELSE 0 END
  ),0)

new_profile_activation

New Profile Activation

A new profile is counted as activated one week after creation if it meets the following conditions: 1) at least 3 days of use during first week 2) at least one search between days 4-7.

Data Source: new_profile_activation

Definition: 
COUNTIF(is_activated)

turn_on_notifications_ctr_onboarding

Turn on Notification Click

This metric looks at proportion of all new profiles that were exposed to the turn on notification card and clicked the action during on-boarding.

Data Source: special_onboarding_events

Definition: 
COALESCE(SUM(turn_on_notifications_flag))

set_to_default_ctr_onboarding

Set to Default Click

This metric looks at proportion of all new profiles that were exposed to the set to default card and clicked the action during on-boarding.

Data Source: special_onboarding_events

Definition: 
COALESCE(SUM(set_to_default_flag))

sign_in_ctr_onboarding

Sign in Click

This metric looks at proportion of all new profiles that were exposed to the sign-in card and clicked the action during on-boarding.

Data Source: special_onboarding_events

Definition: 
COALESCE(SUM(sign_in_flag))

at_least_1_cta_ctr_onboarding

Clicked at least one CTA

This metric looks at proportion of all new profiles that were exposed to onboarding cards and clicked at least one action during on-boarding.

Data Source: special_onboarding_events

Definition: 
COALESCE(SUM(at_least_1_cta))

impressions

Firefox iOS appstore impressions

This is the number of unique impressions of firefox browser in iOS appstore. The etl of the base table is defined in bigquery-etl. This metric needs to be aggregated by first_seen_date (date column from the data recieved from appstore) for daily aggregation. The underlying table have a lag of 7 days. For questions please contact "rbaffourawuah@mozilla.com".

Data Source: appstore_funnel

Definition: 
SUM(impressions)

downloads

Firefox iOS appstore downloads

This is the total number of downloads of firefox browser in iOS appstore. The etl of the base table is defined in bigquery-etl. This metric needs to be aggregated by first_seen_date (date column from the data recieved from appstore) for daily aggregation. The underlying table have a lag of 7 days. For questions please contact "rbaffourawuah@mozilla.com".

Data Source: appstore_funnel

Definition: 
SUM(total_downloads)

funnel_new_profiles

Firefox iOS funnel new profiles

This is the total number of new profiles created on a given date. We only count new profiles that came via release channel and we also filter out app version 107.2 data that was recieved after February 1st. The etl of the base table is defined in bigquery-etl. This metric needs to be aggregated by first_seen_date for daily aggregation. The underlying table have a lag of 28 days, this means the most recent completed first seen date will be 28 days from current date. For questions please contact "rbaffourawuah@mozilla.com".

Data Source: funnel_retention

Definition: 
SUM(new_profiles)

repeat_users

Firefox iOS funnel repeat users

This is the total number of new profiles that visited more than once within their first 28 days. All the filters applied to new profile counts is applied to this calculation. The etl of the base table is defined in bigquery-etl. This metric needs to be aggregated by first_seen_date for daily aggregation. The underlying table have a lag of 28 days, this means the most recent completed first seen date will be 28 days from current date. For questions please contact "rbaffourawuah@mozilla.com".

Data Source: funnel_retention

Definition: 
SUM(repeat_user)

week_4_retained_users

Firefox iOS funnel week 4 retained users

This is the total number of new profiles that returned between between day 22 to day 28 after first seen. All the filters applied to new profile counts is applied to this calculation. The etl of the base table is defined in bigquery-etl. This metric needs to be aggregated by first_seen_date for daily aggregation. The underlying table have a lag of 28 days, this means the most recent completed first seen date will be 28 days from current date. For questions please contact "rbaffourawuah@mozilla.com".

Data Source: funnel_retention

Definition: 
SUM(retained_week_4)