-
-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Splitting data into multiple rows when using anti_sample=true #49
Comments
Thanks - may I ask how many rows are in the tables you are fetching? Also the results of |
The table has 6 vs 3 rows (deviceCategory). See sessionInfo() below:
|
Weird, ok thanks, will take a look. |
Hi @martijnvv , I can't replicate this with the below code: > dateStart <- Sys.Date() - 30
> dateYesterday <- Sys.Date() - 1
> cf <- dim_filter("source","EXACT","google",not = FALSE)
> fc <- filter_clause_ga4(list(cf))
> gaDataFunnel_dev1 <- google_analytics_4(viewId,
+ date_range = c(dateStart, dateYesterday),
+ dimensions=c("deviceCategory", "source"),
+ metrics = c("uniquePageviews"),
+ order = order_type("deviceCategory", "ASCENDING"),
+ dim_filters = fc,
+ anti_sample = TRUE)
anti_sample set to TRUE. Mitigating sampling via multiple API calls.
Finding how much sampling in data request...
Auto-refreshing stale OAuth token.
Downloaded [3] rows from a total of [3].
No sampling found, returning call
Downloaded [3] rows from a total of [3]. Could you perhaps also report the message feedback when you set And also install the version of |
Hi @MarkEdmondson1234 , I first updated to version 0.3.0.9000, that made no difference...
|
@martijnvv The latest Github version now includes a |
@MarkEdmondson1234 Consider that bug squashed. I haven't run any queries with averaged values or percentages, only absolutes. Thanks! |
I run the following code with or without anti_sample:
The code with anti_sample=true returns the same values separated into two rows:
Without anti_sample=true, the table is no longer split into multiple rows:
This seems to occur only in the past few days. It didn't happen before.
I'm running version 0.3.0 of the package
The text was updated successfully, but these errors were encountered: