fetch.by with ga:users and ga:NdayUsers #15
Comments
I should add that I was using |
Please read the docs: https://support.google.com/analytics/answer/2992042. To illustrate the problem try the following: library(RGA)
authorize()
get_ga(id, "8daysAgo", "today", "ga:users")
#> users
#> 1 748
get_ga(id, "8daysAgo", "today", "ga:users", fetch.by = "day")
#> 1 932
#> Warning: The 'ga:users' or 'ga:NdayUsers' total value for several days is not the sum of values for each single day. |
Thanks - I just wanted to be explicitly clear before I started using fetch.by exactly how it was working. In your second |
You're right. But I don't know how to fix it for this metric. With other metrics the |
I don't think there is a way to fix it, so it's right that fetch.by raises a warning. It might help if it was added to the last section of the reporting API vignette? That's where I looked first for clarification. |
Sorry that this is more of a question than an issue.
When using the fetch.by parameter with the
ga:users
orga:NdayUsers
metrics,get_ga()
sometimes returns a warning:I note that in date-ranges.R the function is just explicitly checking for those metrics to display the warning.
So my question is, is the warning displaying because when the query is split by the
fetch.by
parameter, thega:users
value will be higher than if the query was run without thefetch.by
, because that value is actually the sum of several sub-query values?It wasn't explicitly clear to me whether the warning was that the
ga:users
figure would be inaccurate, or if it was just a helpful reminder of how GA is calculating users.The text was updated successfully, but these errors were encountered: