Forum Discussion
Problem with Google Analytics data
Hi all, I connected GA to the desktop version of Power BI, but the data (in days, users, and channel) in BI doesn't match with GA reports. After reading a lot of post, I was filter between dates in Power Query and achieve the data match in both systems, but the problem is the maximun range of date is 2 month, I need years. Somebody knows a workaround better than this to retrieve data of the GA api? or if the Power Bi team it´s working in fix this issue?
- Thanks @v-eachen-msft , By the way, I find a brief job to fix this problem, in the advanced editor you must add this code: #"samplingLevel" = HIGHER_PRECISION in each GA table,meanwhile vote in this post https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/39361177-data-credential-issues-i... with the same problem
13 Replies
Hi andrescaso ,
You could vote for this similar idea.
You could also come up a new idea about that and add your comments there to improve Power BI and make this feature coming sooner.https://ideas.powerbi.com/forums/265200-power-bi-ideas
Thanks v-eachen-msft
I found and vote in this post https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/39361177-data-credential-issues-inconsistency-in-data-whe with the same problem
- Thanks @v-eachen-msft , By the way, I find a brief job to fix this problem, in the advanced editor you must add this code: #"samplingLevel" = HIGHER_PRECISION in each GA table,meanwhile vote in this post https://ideas.powerbi.com/forums/265200-power-bi-ideas/suggestions/39361177-data-credential-issues-i... with the same problem
Try to filter your table in power query by dates, at some point your data in power bi is the same than google analytics
Regards
You'd think so, but it's not. I think the blame rests with Google, but I don't know what to do about it.
In the very first step the data is already wrong because Google tries to send all data without filters, and if there are more rows than the return limit it just truncates the rest, and the data is never correct in PowerBI.
