From 9d7b15d98d39829d7ca81c2533c8da1a41958768 Mon Sep 17 00:00:00 2001 From: m-d-bowerman Date: Wed, 25 Sep 2024 12:30:20 -0700 Subject: [PATCH] fix prettier check errors --- .../search/search_revenue_levers/reference.md | 38 +++++++++---------- 1 file changed, 19 insertions(+), 19 deletions(-) diff --git a/src/datasets/search/search_revenue_levers/reference.md b/src/datasets/search/search_revenue_levers/reference.md index 62249be82..bc5343541 100644 --- a/src/datasets/search/search_revenue_levers/reference.md +++ b/src/datasets/search/search_revenue_levers/reference.md @@ -5,33 +5,33 @@ # Introduction The `search_revenue_levers` datasets isolate key components of the search monetization funnel, e.g. revenue levers, to more effectively support search revenue analyses. The suite of `search_revenue_levers` datasets are as follows: -- `search_revenue_levers_daily`: provides daily search metrics at **minimum country granularity* (e.g. SAP by device, partner, channel, and specific country) -- `search_revenue_levers_monthly_detail` **(work in progress, see [Jira](https://mozilla-hub.atlassian.net/browse/RS-1245))**: provides monthly search and revenue metrics at *partner reporting granularity* (e.g. SAP by device, partner, channel, and country as reported by each partner) -- `search_revenue_levers_monthly`: provides monthly search and revenue metrics at *search funnel granularity* (e.g. SAP by device, partner, and US vs Rest of World) +- `search_revenue_levers_daily`: provides daily search metrics at \*_minimum country granularity_ (e.g. SAP by device, partner, channel, and specific country) +- `search_revenue_levers_monthly_detail` **(work in progress, see [Jira](https://mozilla-hub.atlassian.net/browse/RS-1245))**: provides monthly search and revenue metrics at _partner reporting granularity_ (e.g. SAP by device, partner, channel, and country as reported by each partner) +- `search_revenue_levers_monthly`: provides monthly search and revenue metrics at _search funnel granularity_ (e.g. SAP by device, partner, and US vs Rest of World) **[Revenue data access permissions](https://mozilla-hub.atlassian.net/wiki/spaces/DATA/pages/747176558/Search+Revenue+Documentation#Revenue-Data-Access-Policies) of category 2 or higher are required to access `search_revenue_levers_monthly_detail` and `search_revenue_levers_monthly`.** -For most search and revenue analyses, we recommend using `search_revenue_levers_monthly`. By aggregating to the search monetization funnel granularity, this table is used to support the Monthly and Quarterly Business Reviews. Most ad hoc search revenue analyses should align with this internal standard of reporting. +For most search and revenue analyses, we recommend using `search_revenue_levers_monthly`. By aggregating to the search monetization funnel granularity, this table is used to support the Monthly and Quarterly Business Reviews. Most ad hoc search revenue analyses should align with this internal standard of reporting. That being said, there are cases when Mozillians require more granularity for search revenue analyses. By aggregating to the partner reporting granularity, `search_revenue_levers_monthly_detail` is designed to support deep dives into performance by search partner. -The final dataset, `search_revenue_levers_daily`, does not include revenue (because search revenue is reported monthly, not daily). Due to the convenient partner-level aggregation, this table is ingested for search revenue forecasting. However, Mozillians focused on search analyses may prefer the other existing search tables: [`search_aggregates`](https://docs.telemetry.mozilla.org/datasets/search/search_aggregates/reference) (fastest to query!) or [`search_clients_engines_sources_daily`](https://docs.telemetry.mozilla.org/datasets/search/search_clients_engines_sources_daily/reference) (most data possible!). +The final dataset, `search_revenue_levers_daily`, does not include revenue (because search revenue is reported monthly, not daily). Due to the convenient partner-level aggregation, this table is ingested for search revenue forecasting. However, Mozillians focused on search analyses may prefer the other existing search tables: [`search_aggregates`](https://docs.telemetry.mozilla.org/datasets/search/search_aggregates/reference) (fastest to query!) or [`search_clients_engines_sources_daily`](https://docs.telemetry.mozilla.org/datasets/search/search_clients_engines_sources_daily/reference) (most data possible!). ## Contents The differences between the aggregation structures are summarized as follows: -| Column Name | `search_revenue_levers_daily` | `search_revenue_levers_monthly_detail` | `search_revenue_levers_monthly` | -| ----------- | ----------------------------- | -------------------------------------- | -------------------------------- | -| device | `desktop`, `mobile` | `desktop`, `mobile` | `desktop`, `mobile` | -| partner | `Google`, `Bing`, `DuckDuckGo` | `Google`, `Bing`, `DuckDuckGo` | `Google`, `Bing`, `DuckDuckGo` | -| channel | `NULL`, `personal`, `ESR` | `NULL`, `personal`, `ESR` | column does not exist | -| country | `US`, `DE`, `FR`, ... | Google: `US`, `ROW`, Bing: `US`, `DE`, `FR`, ... | All partners: `US`, `ROW` | -| submission_date | minimum aggregation: daily | minimum aggregation: monthly | minimum aggregation: monthly | +| Column Name | `search_revenue_levers_daily` | `search_revenue_levers_monthly_detail` | `search_revenue_levers_monthly` | +| --------------- | ------------------------------ | ------------------------------------------------ | ------------------------------- | +| device | `desktop`, `mobile` | `desktop`, `mobile` | `desktop`, `mobile` | +| partner | `Google`, `Bing`, `DuckDuckGo` | `Google`, `Bing`, `DuckDuckGo` | `Google`, `Bing`, `DuckDuckGo` | +| channel | `NULL`, `personal`, `ESR` | `NULL`, `personal`, `ESR` | column does not exist | +| country | `US`, `DE`, `FR`, ... | Google: `US`, `ROW`, Bing: `US`, `DE`, `FR`, ... | All partners: `US`, `ROW` | +| submission_date | minimum aggregation: daily | minimum aggregation: monthly | minimum aggregation: monthly | There are 14 possible revenue levers measures available: - 3 [daily active users metrics](https://mozilla-hub.atlassian.net/wiki/spaces/DATA/pages/747176558/Search+Revenue+Documentation#Search-DAU): `Eligible Markets DAU`, `Default Engine DAU`, `Search-Engaged DAU` -- 9 [search engagement metrics](https://mozilla.cloud.looker.com/dashboards/314): `SAP`, `Tagged SAP`, `Tagged Follow On`, `Monetizable SAP`, `Search with Ads`, `Ad Click`, `Organic Search`, `Organic Search with Ads`, `Organic Ad Click` +- 9 [search engagement metrics](https://mozilla.cloud.looker.com/dashboards/314): `SAP`, `Tagged SAP`, `Tagged Follow On`, `Monetizable SAP`, `Search with Ads`, `Ad Click`, `Organic Search`, `Organic Search with Ads`, `Organic Ad Click` - 2 revenue metrics (monthly tables only): `Revenue paid to Mozilla`, `Revenue per Ad Click` # Data Reference @@ -46,7 +46,7 @@ There are 14 possible revenue levers measures available: SELECT submission_date, COALESCE(SUM(sap), 0) AS sap -FROM `mozdata.search.search_revenue_levers_daily` +FROM `mozdata.search.search_revenue_levers_daily` WHERE country IN ('DE', 'US') AND device = 'desktop' AND partner = 'Google' AND submission_date >= '2024-01-01' GROUP BY 1 @@ -72,11 +72,11 @@ GROUP BY ## Scheduling - `search_revenue_levers_daily`: This job is -[scheduled on airflow](https://workflow.telemetry.mozilla.org/dags/bqetl_search_dashboard/grid?search=bqetl_search_dashboard) -to run daily. + [scheduled on airflow](https://workflow.telemetry.mozilla.org/dags/bqetl_search_dashboard/grid?search=bqetl_search_dashboard) + to run daily. - `search_revenue_levers_monthly_detail` and `search_revenue_levers_monthly`: These jobs are -[scheduled on airflow](https://workflow.telemetry.mozilla.org/dags/private_bqetl_revenue/grid?search=private_bqetl_revenue) -to run daily. However, the most recent month does not populate until the calendar month is completed. + [scheduled on airflow](https://workflow.telemetry.mozilla.org/dags/private_bqetl_revenue/grid?search=private_bqetl_revenue) + to run daily. However, the most recent month does not populate until the calendar month is completed. ## Schema @@ -136,4 +136,4 @@ root - `search_revenue_levers_daily` is [defined in `bigquery-etl`](https://github.com/mozilla/bigquery-etl/tree/main/sql/moz-fx-data-shared-prod/search_derived/search_revenue_levers_daily_v1). - `search_revenue_levers_monthly_detail` is TBA. -- `search_revenue_levers_monthly` job is [defined in `private-bigquery-etl`](https://github.com/mozilla/private-bigquery-etl/tree/main/sql/moz-fx-data-shared-prod/revenue_derived/search_revenue_levers_monthly_v3). \ No newline at end of file +- `search_revenue_levers_monthly` job is [defined in `private-bigquery-etl`](https://github.com/mozilla/private-bigquery-etl/tree/main/sql/moz-fx-data-shared-prod/revenue_derived/search_revenue_levers_monthly_v3).