search_aggregates is designed to power high level search dashboards.
It's quick and easy to query, but the data are coarse.
In particular, this dataset allows you to segment
by a limited number of client characteristics which are relevant to search markets.
However, it is not possible to normalize by client count.
If you need fine-grained data, consider using
which breaks down search counts by client
Each row of
the standard search count aggregations
for each unique combination of the following columns.
Unless otherwise noted, these columns are taken directly from
source- The UI component used to issue a search - e.g.
addon_version- The installed version of the [
NULLmeans the standard Firefox build
NULLexcept for small segments relating to search experimentation
There are three aggregation columns:
Each of these columns represent different types of searches.
For more details, see the search data documentation
Note that, if there were no such searches in a row's segment
(i.e. the count would be 0),
the column value is
search_aggregates is heavily restricted.
You will not be able to access this table without additional permissions.
For more details see the search data documentation.
This job is scheduled on airflow to run daily.
As of 2018-02-13,
the current version of
and has a schema as follows.
The dataset is backfilled through 2016-06-06
root |-- country: string (nullable = true) |-- engine: string (nullable = true) |-- source: string (nullable = true) |-- submission_date: string (nullable = true) |-- app_version: string (nullable = true) |-- distribution_id: string (nullable = true) |-- locale: string (nullable = true) |-- search_cohort: string (nullable = true) |-- addon_version: string (nullable = true) |-- tagged-sap: long (nullable = true) |-- tagged-follow-on: long (nullable = true) |-- sap: long (nullable = true)
search_aggregates job is