Mistakes to avoid when blending data with Google Data Studio
The goal is this article is to highlight and explain some subtleties of Data Studio Data blending. I hope it will help my readers avoid and understand the most common pitfalls.
Only rows with matching keys are returned.
The first thing to known when blending data is that only rows with a key from the primary data source matching a key from the second data source are passed into the blended data. In the example below, you can see that Superman doesn’t appear in the blended data because he is not listed in the first data source. The direct consequence of this is that the order of data source when blending them is crucial.
Data Source blending order
In the example below, we have the same data source as seen previously but blended in a different order. Superman now appears in the list of the blended data.
- Always count the number of rows returned within your blended data and verify it against your blended data source.
- Always verify your aggregated numbers and calculation from your blended data against your blended data sources.
- Always check for “null” values.
- Make sure that you are blending your data sources in the right order.
- Be a data skeptic
As compared to tools like Tableau or Looker, Google Data Studio is pretty simple. However, for a lot of users, it will be their first confrontation with data manipulations like…
Here is a short article on how to freeze top rows in Google Data Studio with Tables. The fix itself might be quickly outdated but the solution is interesting as…
Transferring Google Data Studio ownership is not as straightforward as it should. Firstly it is essential to understand that transferring ownership of a report is not the same as transferring…