After posting a poll on Twitter, it seems not too many people actually use the extract data function.
I’ll show you the steps to follow to extract the data, as well as how it can impact the speed of your reports.
Using the Extract Data connector
Create a new Data Studio report and choose a new data source. We will choose Extract Data as our data source.
You’ll then be presented with ‘Available Data Sources’ that are available for to extract data from, as shown below.
Once you’ve selected your data source, you will need to choose what Dimensions and Metrics you want. I’ve used a Google Analytics source to demonstrate how to extract data. You can see all the different dimensions and metrics in list of ‘Available Fields’ on the right.
We’ll keep things simple and only choose Date and Default Channel Grouping as our dimensions. For metrics, I’ll just pick Sessions and Users. For the date range I’ll choose the last 30 days.
You can see on the right side how many different dimensions and metrics there are in a normal Google Analytics data source. Note that we are leaving all of them behind and only picking the fields we will be using in our report.
We know have our two dimensions and two metrics that we will use in our dashboard. We can click ‘Save and Extract’ to continue.
You’ll notice that there is an option for it to Auto Update. I’ve set it to repeat Daily, so that the data will stay fresh and updated.
We can make any final changes to the fields in our data source before adding to the report.
Since I only chose to extract data from the last 30 days, if I adjust the date settings it shows no data from more than 30 days prior.
So this is good for a monthly report, but bad if we want to be able to play around and explore the data.
Testing out the Extracted Data vs regular Data
So we want to see if using Extracted Data helped speed up our dashboard. Reports being ‘slow’ can be a common complaint with others view Data Studio reports.
I’ve created created two scorecards, a time series chart and a table (with filtering) showing off the previous month’s data. The filters on the table affected both sets of data.
Below you can see that when I click ‘Organic Search’ on the Extracted Data table, the Extracted data time series and scorecards are filtered quicker than the normal Google Analytics data.
If I click ‘Direct’ on the regular data table, the Extracted data time series, scorecards and table also filter sooner than the regular data.
This gives an idea of what using extracted data can do. Sometimes speed can be an issue with reports, particularly if you are sharing them with colleagues who don’t normally use Data Studio.
For example, if you are sharing a report with your manager or CEO you want the data to be quickly accessible. If they have to wait for charts and tables to load, they could get frustrated. Therefore using Extracted Data could be a way to ensure your report loads correctly and is fast and seamless to sue.
Below is the actual Data Studio report. You can play around and see if you notice differences in speed between the Extracted data and regular data.
Difference in number of Users
You’ll notice the number of Users are different between the Extracted Data and the regular Google Analytics data.
For example, the number of Users in the extracted data is 6820.
The number of number of Users in the regular data is 5804. Almost one thousand fewer Users.
Why is this the case?
According to Bounteous;
“Contrary to popular belief, the Users metric in standard Google Analytics views doesn’t really represent individual users and people. Rather, this number is based on a cookie that is set by the user’s browser. That means if you access the website from a different browser or device, you might be counted as multiple users.”
Therefore the difference in Users numbers is likely due to the time frame specified by the extracted data and the full time frame allowed in the regular Google Analytics data.
I hope you enjoyed this post, and know a bit more about using the Extract Data connector in Google Data Studio.
If you liked this article you might like my other blog posts.
Or you can follow me on Twitter!