Manage data freshness

Balance data updates with report performance.

This article explains how caching works, and how to choose between more frequent data updates and better report performance.

Data freshness vs. report performance

Data freshness refers to how up-to-date the data in a report is. Different types of reports have different requirements or expectations for data freshness. If you are measuring ad performance on your site or app, for example, daily updates might be sufficient. Reports based on social media analytics, on the other hand, may want their data updated multiple times in a day.

Report performance is a measure of how quickly the report loads. Fetching data directly from the underlying data set can be slow, which in turn makes your reports sluggish to load and respond to viewer changes, like applying filters and date ranges. In addition, for some data sources, such as BigQuery, fetching data directly can incur financial costs.

To offset these issues, Data Studio may store some of the data provided by your data sources in a temporary system known as a cache. Retrieving data from a cache can be much faster than fetching it directly from the data set. And it helps reduce the number of queries sent, minimizing costs for paid data access.

How the cache works

Every component in a Data Studio report gets its data from the cache when possible. When a component in your report requests data, the cache remembers the response returned by the underlying platform. If a person viewing the report requests the exact same data (for example, the same dimensions and metrics with the same filter conditions and date range) as a previously received query, then the new request is served by the  cache.

If the request can't be served by the  cache, Data Studio requests the data from the underlying data set.

Cache refresh

The cache automatically refreshes at certain intervals, and you can manually refresh reports that you can edit (see below).

When the cache refreshes, all the old cached data is discarded. New queries generated by the report go directly to the underlying platform and the responses are added to the  cache.

If your report uses a BigQuery data source, please be aware that the usual query costs will apply whenever Data Studio queries the underlying project. This includes queries that bypass the cache, as well as manual and automatic cache refreshes.The cache automatically refreshes at certain intervals, and you can manually refresh reports that you can edit (see below).

Set data freshness for a data source

You can control how often some data source types refresh their cache. For example, a Sheets data source can check for fresh data every 15 minutes (the default), every 4 hours, or every 12 hours. Some data sources only support a single default setting (typically, every 12 hours).

To set the refresh time

  1. Edit the data source.
    1. View access to the data source is not sufficient to change this setting.
    2. In the toolbar at the top, click Data freshness.
    3. Select the desired time option, then click SET DATA FRESHNESS.

Refresh report data manually

You can refresh the cache at any time by viewing or editing the report and clicking Refresh data Refresh.

This refreshes the cache for every data source added to the report.

You must be able to edit the report to refresh the cached data.

How to tell if report data is cached

You can see if data is coming from the cache by viewing the report and looking in the bottom left corner. When all the charts on the current page are being served from the cache, you'll see a lightning bolt icon along with the time and date of the last update cache icon.

Blending and cached data

For a blended data source, the cache will use the setting that satisfies the desired refresh times for all of the data sources included in the blend.

For example, if you blend a Sheets data source having a refresh time of 15 minutes, with a BigQuery data source having a refresh time of 4 hours, the resulting blended data source will have a refresh time of 15 minutes.

Report settings

Was this helpful?
How can we improve it?