Skip to content

Commit

Permalink
Fix prettier check issue
Browse files Browse the repository at this point in the history
  • Loading branch information
alekhyamoz committed Jul 30, 2024
1 parent e1e79ab commit 69989e0
Showing 1 changed file with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -50,8 +50,8 @@ heavily limit the data you read using `submission_date` or `sample_id`.

As of August 1, 2024, the `mobile_search_clients_daily` table has been updated to extract data from the `baseline` ping tables instead of the original `metrics` ping tables. This shift maintains the same search totals with greater confidence in the mobile search engagement dates.

As [noted](https://docs.telemetry.mozilla.org/concepts/analysis_gotchas.html?highlight=submission)#submission-date), the `submission_date` used throughout telemetry is the date Mozilla received that client's engagement, not necessarily the actual date on which that client engaged with Firefox. Mobile `metrics` pings are historically sent later than the actual date of activity: it takes roughly [4 days for Firefox to receive 95% of Fenix `metrics` pings](https://sql.telemetry.mozilla.org/queries/92717) which originate from a given actual date. `Baseline` pings are more frequently sent/ received and serve as the basis of KPI DAU metrics. Therefore, this switch ensures a client's KPI DAU activity can be matched to search activity from that same active day.
As [noted](https://docs.telemetry.mozilla.org/concepts/analysis_gotchas.html?highlight=submission)#submission-date), the `submission_date` used throughout telemetry is the date Mozilla received that client's engagement, not necessarily the actual date on which that client engaged with Firefox. Mobile `metrics` pings are historically sent later than the actual date of activity: it takes roughly [4 days for Firefox to receive 95% of Fenix `metrics` pings](https://sql.telemetry.mozilla.org/queries/92717) which originate from a given actual date. `Baseline` pings are more frequently sent/ received and serve as the basis of KPI DAU metrics. Therefore, this switch ensures a client's KPI DAU activity can be matched to search activity from that same active day.

All data prior to August 1st, 2024, is powered by the `metrics` ping and has been moved to the `mobile_search_clients_daily_historical` table. The new derived table, `mobile_search_clients_daily_v2`, has data from August 1, 2024 and is powered by the `baseline` ping. Downstream views and tables, like `mozdata.search.mobile_search_clients_daily`, pull data from both `mobile_search_clients_daily_v2` and `mobile_search_clients_daily_historical` to ensure comprehensive data coverage. `mozdata.search.mobile_search_clients_daily` remains the client-level source-of-truth for mobile search analyses.
All data prior to August 1st, 2024, is powered by the `metrics` ping and has been moved to the `mobile_search_clients_daily_historical` table. The new derived table, `mobile_search_clients_daily_v2`, has data from August 1, 2024 and is powered by the `baseline` ping. Downstream views and tables, like `mozdata.search.mobile_search_clients_daily`, pull data from both `mobile_search_clients_daily_v2` and `mobile_search_clients_daily_historical` to ensure comprehensive data coverage. `mozdata.search.mobile_search_clients_daily` remains the client-level source-of-truth for mobile search analyses.

[search data documentation]: ../../search.md

0 comments on commit 69989e0

Please sign in to comment.