Forum Discussion
Google Analytics connector missing startdate/enddate parameters
Just to add some details. The issue is that Google Analytics does sampling. The more precise the query, the less accurate it becomes. See this page. Our use of the date dimension for filtering date ranges exacerbates the issue. So while we will likely fix this by using parameters in the future, keep in mind that the problem will always be there to a degree.
Hi Tristan!
Any news on this, my problem besides propper aggregation, is that I get sampled data instead of actual values, and since I'm reporting sales my data is not real.
If I use a date range filter, the original query (confirmed with fiddler) is for the whole range of the DB (going all the way to 2013) and then the filter is applied, so i only get the results from the sampled filter... so no, its not useful.
Any news on this? is it going to be fixed/addressed soon?
The only current way to use the GA connector is to allow it to query back to the beginning of time and then to filter. So sad.
Yes it's sad, because its useless in a lot of scenarios, for you is Users for me is sales (i just cant report them out of sampled data). I guess implementing this shouldnt be that hard!
Hold on. Sampled data is a different matter - not an issue with the connector semantics. If you want unsampled data, you need GA Premium.
not really, if the query is small enough (lets say less than a year) GA won't sample data (in their API) premium or not! If you catch the request with fiddler you can see that PBI is requesting for sampled data! if we could run smaller queries like you ask, i would have what i need. (BTW tableau handles this part just fine... just that im on trial)
Can you share the Fidder request that shows it requesting sampled data?
Or are you saying that because there is no timeframe specified that PBI is requesting the entire timeframe and that is implicitly causing sampling.
so there it is, but i guess this is the response, so as you can see we recieve sample data, since the start date is really far off. The same report using google api but with a date range of 1 year, and i get unsampled data!
Ok, so you are getting sampling because of the implicit date range. So I'll extend my "so sad" to cover that also, as there is currently no way to avoid it.
