Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
So I'm trying to play around with the Google Analytics dataset found in Google BigQuery. Just a little background on this dataset:
When I connect to BigQuery in Power BI and it loads the data, I'm noticing some formatting issues. Check out the screenshot below:
You'll notice that some columns are formatted just fine and it is understandable (i.e. "channelGrouping", "socialEngagementType", "fullVisitorId"). But it looks like the columns "customDimensions" and "hits" are not splitting up into their subsections and is combined into one messy column in a format I don't understand.
When I go to look at the data source on BigQuery, however, it looks fine:
Even though the preview only has one row of data available, you can see that the "hits" column is correctly separated into its respective subsections.
How do I go about formatting the query to look more like this? Here are my ideas:
Any feedback is appreciated. Cheers!
Hi pstrand64,
To use SQL statement when connecting to Google Big Query, you can use ODBC connector instead. For details, you can refer to:
In addtion, ODBC driver only support import mode, so if you are using direct query mode you should using Google Big Query connector.
Regards,
Jimmy Tao
Jimmy,
Thanks for the response, man. So what you're saying is that I can query the data with SQL from Google BigQuery inside Power BI by selecting the option "OBDC connector"?
Sorry if I'm not understanding this or asking the right questions, I'm a little new to SQL and data wrangling (also new to Power BI).
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
71 | |
70 | |
43 | |
31 | |
26 |
User | Count |
---|---|
89 | |
49 | |
44 | |
38 | |
37 |