From aa6cf64bbd31d2924a6f2bfd34df477c6fbbafb8 Mon Sep 17 00:00:00 2001 From: "doc-correctness[bot]" <342578012+doc-correctness[bot]@users.noreply.github.com> Date: Fri, 20 Nov 2026 13:03:30 +0000 Subject: [PATCH 01/14] concepts/pipeline/artifact_deployment.md: Mention bqetl_artifact_initialize DAG for table initialization Finding-Id: b694f55dbf83450b9ad5318316243a37 Reviewed: no (this PR is the review) Source: https://github.com/mozilla/telemetry-airflow/blob/main/dags/bqetl_artifact_initialize.py --- src/concepts/pipeline/artifact_deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/concepts/pipeline/artifact_deployment.md b/src/concepts/pipeline/artifact_deployment.md index 6a4555280..0c78a76ed 100644 --- a/src/concepts/pipeline/artifact_deployment.md +++ b/src/concepts/pipeline/artifact_deployment.md @@ -22,7 +22,7 @@ The UDF deploy is triggered through the `publish_public_udfs` and `publish_persi ## Table Deployment -Tables get deployed through the [`publish_tables_and_views` Airflow task](https://workflow.telemetry.mozilla.org/tree?dag_id=bqetl_artifact_deployment), which replaced the former separate `publish_new_tables` task. This task will run all SQL generators, generate schemas for each query and will deploy schemas for tables and apply any schema-compatible changes for existing tables. The task will fail if changes that are incompatible with existing schemas (such as removing fields or changing field types) are to be applied. +Tables get deployed through the [`publish_tables_and_views` Airflow task](https://workflow.telemetry.mozilla.org/tree?dag_id=bqetl_artifact_deployment), which replaced the former separate `publish_new_tables` task. This task will run all SQL generators, generate schemas for each query and will deploy schemas for tables and apply any schema-compatible changes for existing tables. The task will fail if changes that are incompatible with existing schemas (such as removing fields or changing field types) are to be applied. New tables are first initialized via a separate `bqetl_artifact_initialize` Airflow DAG, which runs `bqetl query initialize` across `moz-fx-data-shared-prod`, `moz-fx-data-experiments`, `moz-fx-data-marketing-prod`, and `moz-fx-data-bq-people`. ## View Deployment From a9c6b3200902cad0dbf94c2a48e5dab84cc57d31 Mon Sep 17 00:00:00 2001 From: "doc-correctness[bot]" <342578012+doc-correctness[bot]@users.noreply.github.com> Date: Fri, 20 Nov 2026 13:03:31 +0000 Subject: [PATCH 02/14] concepts/pipeline/artifact_deployment.md: Add note on static table deployment Finding-Id: 86a8c6b7625f4f39ad30c51b8a439387 Reviewed: no (this PR is the review) Source: https://docs.telemetry.mozilla.org/datasets/static.html --- src/concepts/pipeline/artifact_deployment.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/concepts/pipeline/artifact_deployment.md b/src/concepts/pipeline/artifact_deployment.md index 0c78a76ed..ed56de620 100644 --- a/src/concepts/pipeline/artifact_deployment.md +++ b/src/concepts/pipeline/artifact_deployment.md @@ -24,6 +24,8 @@ The UDF deploy is triggered through the `publish_public_udfs` and `publish_persi Tables get deployed through the [`publish_tables_and_views` Airflow task](https://workflow.telemetry.mozilla.org/tree?dag_id=bqetl_artifact_deployment), which replaced the former separate `publish_new_tables` task. This task will run all SQL generators, generate schemas for each query and will deploy schemas for tables and apply any schema-compatible changes for existing tables. The task will fail if changes that are incompatible with existing schemas (such as removing fields or changing field types) are to be applied. New tables are first initialized via a separate `bqetl_artifact_initialize` Airflow DAG, which runs `bqetl query initialize` across `moz-fx-data-shared-prod`, `moz-fx-data-experiments`, `moz-fx-data-marketing-prod`, and `moz-fx-data-bq-people`. +Static tables, which are deployed from CSV files rather than generated SQL, are published separately via the `publish_static_tables` task for `moz-fx-data-shared-prod` and `mozdata`. + ## View Deployment View deployment happens together with table deployment in the [`publish_tables_and_views` Airflow task](https://workflow.telemetry.mozilla.org/tree?dag_id=bqetl_artifact_deployment), which replaced the former separate `publish_views` task. This task will run all SQL generators, which ensures that SQL for generated views will be available. Only views with either changes to their SQL definition, schema, metadata or newly created views will be deployed. From 9eec87d9fefa47cd8cd39e0f90cb60c16a02c9ad Mon Sep 17 00:00:00 2001 From: "doc-correctness[bot]" <342578012+doc-correctness[bot]@users.noreply.github.com> Date: Fri, 20 Nov 2026 13:03:33 +0000 Subject: [PATCH 03/14] concepts/pipeline/artifact_deployment.md: List projects covered by table/view deployment Finding-Id: 141bfde35fce447686ea326d94e427c9 Reviewed: no (this PR is the review) Source: https://github.com/mozilla/telemetry-airflow/blob/main/dags/bqetl_artifact_deployment.py Source: https://github.com/mozilla/telemetry-airflow/blob/main/dags/bqetl_artifact_initialize.py --- src/concepts/pipeline/artifact_deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/concepts/pipeline/artifact_deployment.md b/src/concepts/pipeline/artifact_deployment.md index ed56de620..b21c3be9e 100644 --- a/src/concepts/pipeline/artifact_deployment.md +++ b/src/concepts/pipeline/artifact_deployment.md @@ -22,7 +22,7 @@ The UDF deploy is triggered through the `publish_public_udfs` and `publish_persi ## Table Deployment -Tables get deployed through the [`publish_tables_and_views` Airflow task](https://workflow.telemetry.mozilla.org/tree?dag_id=bqetl_artifact_deployment), which replaced the former separate `publish_new_tables` task. This task will run all SQL generators, generate schemas for each query and will deploy schemas for tables and apply any schema-compatible changes for existing tables. The task will fail if changes that are incompatible with existing schemas (such as removing fields or changing field types) are to be applied. New tables are first initialized via a separate `bqetl_artifact_initialize` Airflow DAG, which runs `bqetl query initialize` across `moz-fx-data-shared-prod`, `moz-fx-data-experiments`, `moz-fx-data-marketing-prod`, and `moz-fx-data-bq-people`. +Tables get deployed through the [`publish_tables_and_views` Airflow task](https://workflow.telemetry.mozilla.org/tree?dag_id=bqetl_artifact_deployment), which replaced the former separate `publish_new_tables` task. This task will run all SQL generators, generate schemas for each query and will deploy schemas for tables and apply any schema-compatible changes for existing tables across `moz-fx-data-shared-prod`, `moz-fx-data-experiments`, `moz-fx-data-marketing-prod`, `moz-fx-glam-prod`, and `moz-fx-data-bq-people`. The task will fail if changes that are incompatible with existing schemas (such as removing fields or changing field types) are to be applied. New tables are first initialized via a separate `bqetl_artifact_initialize` Airflow DAG, which runs `bqetl query initialize` across `moz-fx-data-shared-prod`, `moz-fx-data-experiments`, `moz-fx-data-marketing-prod`, and `moz-fx-data-bq-people`. Static tables, which are deployed from CSV files rather than generated SQL, are published separately via the `publish_static_tables` task for `moz-fx-data-shared-prod` and `mozdata`. From 5ff4bc4001f20d55de3fb6e23339833b69362ddc Mon Sep 17 00:00:00 2001 From: "doc-correctness[bot]" <342578012+doc-correctness[bot]@users.noreply.github.com> Date: Fri, 20 Nov 2026 13:03:34 +0000 Subject: [PATCH 04/14] concepts/pipeline/artifact_deployment.md: Document concurrency guard skipping queued runs Finding-Id: 03752767662546179bcae538d7723f4c Reviewed: no (this PR is the review) Source: https://github.com/mozilla/telemetry-airflow/blob/main/dags/bqetl_artifact_deployment.py --- src/concepts/pipeline/artifact_deployment.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/concepts/pipeline/artifact_deployment.md b/src/concepts/pipeline/artifact_deployment.md index b21c3be9e..85309f03d 100644 --- a/src/concepts/pipeline/artifact_deployment.md +++ b/src/concepts/pipeline/artifact_deployment.md @@ -18,7 +18,7 @@ There are two categories of user-defined functions: - UDFs for internal use only: These UDFs are published to the `udf` and `udf_js` datasets in the `moz-fx-data-shared-prod` project and managed via [bigquery-etl](https://github.com/mozilla/bigquery-etl/tree/main/sql/moz-fx-data-shared-prod/udf) - public UDFs that can be used even outside of Mozilla projects: These UDFs are published to the `mozfun` project and managed via [bigquery-etl](https://github.com/mozilla/bigquery-etl/tree/main/sql/mozfun) -The UDF deploy is triggered through the `publish_public_udfs` and `publish_persistent_udfs` Airflow task in the [`bqetl_artifact_deployment`](https://workflow.telemetry.mozilla.org/tree?dag_id=bqetl_artifact_deployment) Airflow DAG. The DAG no longer runs on a nightly schedule; it is triggered by CircleCI on merges to `main` and by Jenkins after schema deploys, and tasks can still be triggered manually by clearing them. +The UDF deploy is triggered through the `publish_public_udfs` and `publish_persistent_udfs` Airflow task in the [`bqetl_artifact_deployment`](https://workflow.telemetry.mozilla.org/tree?dag_id=bqetl_artifact_deployment) Airflow DAG. The DAG no longer runs on a nightly schedule; it is triggered by CircleCI on merges to `main` and by Jenkins after schema deploys, and tasks can still be triggered manually by clearing them. To avoid redundant overlapping runs, the DAG skips a run if another run is already queued, unless the `generate_sql` parameter is set. ## Table Deployment From e3343e13d98e7c0f3ae11482b3461ba3b8ed7f87 Mon Sep 17 00:00:00 2001 From: "doc-correctness[bot]" <342578012+doc-correctness[bot]@users.noreply.github.com> Date: Fri, 20 Nov 2026 13:04:08 +0000 Subject: [PATCH 05/14] concepts/pipeline/event_pipeline.md: Note Firefox Desktop events_daily_v1 is deprecated Finding-Id: 4d1b64b59f544a4386deb95e7c1a6be4 Reviewed: no (this PR is the review) Source: https://github.com/mozilla/bigquery-etl/blob/main/sql/moz-fx-data-shared-prod/telemetry_derived/events_daily_v1/metadata.yaml --- src/concepts/pipeline/event_pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/concepts/pipeline/event_pipeline.md b/src/concepts/pipeline/event_pipeline.md index ba2a1cd5c..331f06b3c 100644 --- a/src/concepts/pipeline/event_pipeline.md +++ b/src/concepts/pipeline/event_pipeline.md @@ -125,7 +125,7 @@ On the pipeline side, the event data is made available in different datasets: its event payload for Firefox versions before 62. - [`events`](../../datasets/batch_view/events/reference.md) contains a row for each event received from main pings and event pings. See [`STMO#52582`](https://sql.telemetry.mozilla.org/queries/52582/source). - For applications that collect events through Glean, each application has a separate `events` dataset. -- [`events_daily`](../../datasets/bigquery/events_daily/reference.md) encodes each client-day's events as a compressed string of Unicode characters, for use with the `mozfun.event_analysis` functions for funnel and event-count analysis. +- [`events_daily`](../../datasets/bigquery/events_daily/reference.md) encodes each client-day's events as a compressed string of Unicode characters, for use with the `mozfun.event_analysis` functions for funnel and event-count analysis. The Firefox Desktop version of this table (`telemetry_derived.events_daily_v1`) is deprecated and no longer actively scheduled (see [bug 1805722](https://bugzilla.mozilla.org/show_bug.cgi?id=1805722)). # Data tooling From c086df8bebd271464411d194795cfe7e46157a93 Mon Sep 17 00:00:00 2001 From: "doc-correctness[bot]" <342578012+doc-correctness[bot]@users.noreply.github.com> Date: Fri, 20 Nov 2026 13:04:09 +0000 Subject: [PATCH 06/14] concepts/pipeline/event_pipeline.md: Clarify events_daily is only generated for some apps Finding-Id: 98dc4a4ea2904165af334e4404357ddc Reviewed: no (this PR is the review) Source: https://github.com/mozilla/bigquery-etl/blob/main/sql_generators/events_daily/templates/events_daily/templating.yaml --- src/concepts/pipeline/event_pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/concepts/pipeline/event_pipeline.md b/src/concepts/pipeline/event_pipeline.md index 331f06b3c..a0982f905 100644 --- a/src/concepts/pipeline/event_pipeline.md +++ b/src/concepts/pipeline/event_pipeline.md @@ -125,7 +125,7 @@ On the pipeline side, the event data is made available in different datasets: its event payload for Firefox versions before 62. - [`events`](../../datasets/batch_view/events/reference.md) contains a row for each event received from main pings and event pings. See [`STMO#52582`](https://sql.telemetry.mozilla.org/queries/52582/source). - For applications that collect events through Glean, each application has a separate `events` dataset. -- [`events_daily`](../../datasets/bigquery/events_daily/reference.md) encodes each client-day's events as a compressed string of Unicode characters, for use with the `mozfun.event_analysis` functions for funnel and event-count analysis. The Firefox Desktop version of this table (`telemetry_derived.events_daily_v1`) is deprecated and no longer actively scheduled (see [bug 1805722](https://bugzilla.mozilla.org/show_bug.cgi?id=1805722)). +- [`events_daily`](../../datasets/bigquery/events_daily/reference.md) (generated for Firefox Desktop, Fenix, and Mozilla VPN; not available for other Glean applications) encodes each client-day's events as a compressed string of Unicode characters, for use with the `mozfun.event_analysis` functions for funnel and event-count analysis. The Firefox Desktop version of this table (`telemetry_derived.events_daily_v1`) is deprecated and no longer actively scheduled (see [bug 1805722](https://bugzilla.mozilla.org/show_bug.cgi?id=1805722)). # Data tooling From 8055e299fa4f9b0c7770b09704e8f451b7b1fd22 Mon Sep 17 00:00:00 2001 From: "doc-correctness[bot]" <342578012+doc-correctness[bot]@users.noreply.github.com> Date: Fri, 20 Nov 2026 13:08:52 +0000 Subject: [PATCH 07/14] cookbooks/publishing_datasets.md: Move scheduling out of labels into its own scheduling block Finding-Id: 9b412b9737ab4290b68226d60823fe06 Reviewed: no (this PR is the review) Source: https://github.com/mozilla/bigquery-etl/blob/main/sql/moz-fx-data-shared-prod/telemetry_derived/ssl_ratios_v1/metadata.yaml --- src/cookbooks/publishing_datasets.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/cookbooks/publishing_datasets.md b/src/cookbooks/publishing_datasets.md index cf3ae60af..114b7b429 100644 --- a/src/cookbooks/publishing_datasets.md +++ b/src/cookbooks/publishing_datasets.md @@ -19,12 +19,13 @@ owners: labels: application: firefox incremental: true # incremental queries add data to existing tables - schedule: daily # scheduled in Airflow to run daily public_json: true public_bigquery: true review_bugs: # Bugzilla bug IDs of data review - 1414839 incremental_export: false # non-incremental JSON export writes all data to a single location +scheduling: + dag_name: bqetl_ssl_ratios ``` The following options define how data is published: From 68a0629a371dffedf7fc205f8451bc5e3fe66602 Mon Sep 17 00:00:00 2001 From: "doc-correctness[bot]" <342578012+doc-correctness[bot]@users.noreply.github.com> Date: Fri, 20 Nov 2026 13:08:53 +0000 Subject: [PATCH 08/14] cookbooks/publishing_datasets.md: Note review_bugs is CI-enforced when publishing is enabled Finding-Id: ad36b9136fd74db1a77301ecc1a8bacc Reviewed: no (this PR is the review) Source: https://github.com/mozilla/bigquery-etl/blob/main/bigquery_etl/metadata/validate_metadata.py --- src/cookbooks/publishing_datasets.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/cookbooks/publishing_datasets.md b/src/cookbooks/publishing_datasets.md index 114b7b429..0ac440ba0 100644 --- a/src/cookbooks/publishing_datasets.md +++ b/src/cookbooks/publishing_datasets.md @@ -42,7 +42,7 @@ The following options define how data is published: - `incremental`: indicates how data gets updated based on the query and Airflow configuration - `true`: data gets incrementally updated - `false`: the entire table data gets updated -- `review_bugs`: list of Bugzilla bug numbers of the data review +- `review_bugs`: list of Bugzilla bug numbers of the data review; required, and enforced by CI validation, whenever `public_bigquery` or `public_json` is set - `legacy`: set to `true` to indicate a dataset that selects only from legacy Telemetry Data will get published when the query is executed in Airflow. Metadata of available public From cc6aca02181b7ab7598bb23446786e200a4d32f0 Mon Sep 17 00:00:00 2001 From: "doc-correctness[bot]" <342578012+doc-correctness[bot]@users.noreply.github.com> Date: Fri, 20 Nov 2026 13:08:55 +0000 Subject: [PATCH 09/14] cookbooks/publishing_datasets.md: Clarify separate deployment paths for public_json vs public_bigquery Finding-Id: 9f7844fa2e0042a583a3c4c4fd4be261 Reviewed: no (this PR is the review) Source: https://github.com/mozilla/bigquery-etl/blob/main/docs/cookbooks/common_workflows.md Source: https://github.com/mozilla/telemetry-airflow/blob/main/dags/bqetl_artifact_deployment.py --- src/cookbooks/publishing_datasets.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/cookbooks/publishing_datasets.md b/src/cookbooks/publishing_datasets.md index 0ac440ba0..c1cba0f6c 100644 --- a/src/cookbooks/publishing_datasets.md +++ b/src/cookbooks/publishing_datasets.md @@ -45,8 +45,9 @@ The following options define how data is published: - `review_bugs`: list of Bugzilla bug numbers of the data review; required, and enforced by CI validation, whenever `public_bigquery` or `public_json` is set - `legacy`: set to `true` to indicate a dataset that selects only from legacy Telemetry -Data will get published when the query is executed in Airflow. Metadata of available public -data on Cloud Storage is updated daily through a separate Airflow task. +Data for `public_json` gets published when the query runs in Airflow, and metadata of available public +data on Cloud Storage is updated daily through a separate Airflow task. Tables flagged `public_bigquery` +are deployed to the `mozilla-public-data` project nightly via the `bqetl_artifact_deployment` Airflow DAG. More information about accessing public data can be found in [Accessing Public Data](../cookbooks/public_data.md). From efca1f4f69d1bcd96179a84e110230bd51cdca65 Mon Sep 17 00:00:00 2001 From: "doc-correctness[bot]" <342578012+doc-correctness[bot]@users.noreply.github.com> Date: Fri, 20 Nov 2026 13:09:06 +0000 Subject: [PATCH 10/14] datasets/active_profiles.md: Add retired/archived notice to Intro section Finding-Id: 968809a7f6254565aa4379d424d696c8 Reviewed: no (this PR is the review) Source: https://docs.telemetry.mozilla.org/ Source: https://github.com/mozilla/bigquery-etl/tree/HEAD/sql/moz-fx-data-shared-prod/telemetry_derived Source: https://github.com/mozilla/telemetry-airflow/tree/HEAD/dags --- src/datasets/active_profiles.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/datasets/active_profiles.md b/src/datasets/active_profiles.md index 663cf5df7..97998cd1e 100644 --- a/src/datasets/active_profiles.md +++ b/src/datasets/active_profiles.md @@ -1,5 +1,7 @@ # Intro +**Note:** This dataset is retired/archived. The pipeline no longer exists in Mozilla's current `bigquery-etl` or `telemetry-airflow` repositories, and the table is no longer generated; this page is kept for historical reference. See [Scheduling](#scheduling) below. + The `active_profiles` dataset gives client-level estimates of whether a profile is still an active user of the browser at a given point in time, as well as probabilistic forecasts of the client's future activity. These quantities are estimated by a model that attempts to infer From d705633c4a0c1179bcdc6146ed212db6e8d721a3 Mon Sep 17 00:00:00 2001 From: "doc-correctness[bot]" <342578012+doc-correctness[bot]@users.noreply.github.com> Date: Fri, 20 Nov 2026 13:09:29 +0000 Subject: [PATCH 11/14] datasets/batch_view/clients_daily/reference.md: Note downstream tasks depending on clients_daily Finding-Id: ea451279a0194ce7a8337da6f4662b99 Reviewed: no (this PR is the review) Source: https://github.com/mozilla/bigquery-etl/blob/main/sql/moz-fx-data-shared-prod/telemetry_derived/clients_daily_v6/metadata.yaml --- src/datasets/batch_view/clients_daily/reference.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/datasets/batch_view/clients_daily/reference.md b/src/datasets/batch_view/clients_daily/reference.md index 64ae45f34..57cbb843c 100644 --- a/src/datasets/batch_view/clients_daily/reference.md +++ b/src/datasets/batch_view/clients_daily/reference.md @@ -55,6 +55,8 @@ This dataset is updated daily via the [telemetry-airflow](https://github.com/mozilla/telemetry-airflow) infrastructure. The job runs as part of the [`main_summary` DAG](https://github.com/mozilla/bigquery-etl/blob/master/dags/bqetl_main_summary.py). +Downstream tasks that depend on this dataset include `jetstream`, `operational_monitoring`, `parquet_export`, and `catalyst`. + ## Schema The data is partitioned by `submission_date`. From 24ffc30f4ed100eafc2363eb7333fb09dadc5401 Mon Sep 17 00:00:00 2001 From: "doc-correctness[bot]" <342578012+doc-correctness[bot]@users.noreply.github.com> Date: Fri, 20 Nov 2026 13:10:05 +0000 Subject: [PATCH 12/14] datasets/bigquery/clients_last_seen/reference.md: Fix field name to match actual view column Finding-Id: 4a7933cfd35b4d04bfb79c31c36ddbcf Reviewed: no (this PR is the review) Source: https://github.com/mozilla/bigquery-etl/blob/main/sql/moz-fx-data-shared-prod/telemetry/clients_last_seen_v2/view.sql --- src/datasets/bigquery/clients_last_seen/reference.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/datasets/bigquery/clients_last_seen/reference.md b/src/datasets/bigquery/clients_last_seen/reference.md index 266952ea0..d60a294e3 100644 --- a/src/datasets/bigquery/clients_last_seen/reference.md +++ b/src/datasets/bigquery/clients_last_seen/reference.md @@ -91,7 +91,7 @@ Please see this [section](../../../concepts/segments.md) for descriptions regard - `days_had_8_active_ticks_bits`: Each bit field represents if a client had at least 8 active ticks on that day. This can be used to approximate the threshold of 1 URI, and is useful for determining activity for clients using Private Browsing Mode where URI counts are not recorded. -- `days_since_visited_8_active_ticks`: Number of days since the client had at least 8 active ticks. +- `days_since_had_8_active_ticks`: Number of days since the client had at least 8 active ticks. ### New Profile Specific From 67fff738f908b661e1184a2f26b55ce77d7ccc15 Mon Sep 17 00:00:00 2001 From: "doc-correctness[bot]" <342578012+doc-correctness[bot]@users.noreply.github.com> Date: Fri, 20 Nov 2026 13:10:06 +0000 Subject: [PATCH 13/14] datasets/bigquery/clients_last_seen/reference.md: Document new days_active_bits/days_since_active fields Finding-Id: 5ec68ac8ced7456891ab84d1535d6c6c Reviewed: no (this PR is the review) Source: https://github.com/mozilla/bigquery-etl/blob/main/sql/moz-fx-data-shared-prod/telemetry/clients_last_seen_v2/view.sql --- src/datasets/bigquery/clients_last_seen/reference.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/datasets/bigquery/clients_last_seen/reference.md b/src/datasets/bigquery/clients_last_seen/reference.md index d60a294e3..fdde66bd6 100644 --- a/src/datasets/bigquery/clients_last_seen/reference.md +++ b/src/datasets/bigquery/clients_last_seen/reference.md @@ -93,6 +93,9 @@ Please see this [section](../../../concepts/segments.md) for descriptions regard Private Browsing Mode where URI counts are not recorded. - `days_since_had_8_active_ticks`: Number of days since the client had at least 8 active ticks. +- `days_active_bits`: Each bit field represents if a client had at least 1 active tick and visited at least 1 URI on that day. +- `days_since_active`: Number of days since the client was active (had at least 1 active tick and visited at least 1 URI). + ### New Profile Specific - `first_seen_date`: Date the client sent their first main ping. From 7c7b508cafa24145497e03183665119caf4b509e Mon Sep 17 00:00:00 2001 From: "doc-correctness[bot]" <342578012+doc-correctness[bot]@users.noreply.github.com> Date: Fri, 20 Nov 2026 13:10:08 +0000 Subject: [PATCH 14/14] datasets/bigquery/clients_last_seen/reference.md: Document new segment field as duplicate of activity_segments_v1 Finding-Id: 396509a6edd640b6b42385966f599f53 Reviewed: no (this PR is the review) Source: https://github.com/mozilla/bigquery-etl/blob/main/sql/moz-fx-data-shared-prod/telemetry/clients_last_seen_v2/view.sql --- src/datasets/bigquery/clients_last_seen/reference.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/datasets/bigquery/clients_last_seen/reference.md b/src/datasets/bigquery/clients_last_seen/reference.md index fdde66bd6..3c9fa8085 100644 --- a/src/datasets/bigquery/clients_last_seen/reference.md +++ b/src/datasets/bigquery/clients_last_seen/reference.md @@ -71,6 +71,7 @@ Please see this [section](../../../concepts/segments.md) for descriptions regard - `is_core_active_v1`: Boolean indicating if the client satisfies conditions of being core active on that day. - `activity_segments_v1`: The activity segment applicable to the client that day. +- `segment`: Duplicate of `activity_segments_v1`, using the same logic. - `is_regular_user_v3`: Boolean indicating if the client satisfies conditions of being a regular user on that day. - `is_new_or_resurrected_v3`: Boolean indicating if the client satisfies conditions of being a regular user on that day. - `is_weekday_regular_v1`: Boolean indicating if the client satisfies conditions of being a weekday regular user on that day.