Version 1.3 of the RSiteCatalyst package to access the Adobe Analytics API is now available on CRAN! Changes include:
- Search via regex functionality in
- Support for Realtime API reports:
- Allow for variable API request timing in
validateflag in JSON request to work correctly
GetAdminConsoleLog(appears to be removed from the API)
Searching via Regex functionality
RSiteCatalyst now supports the search functionality of the API, similar in nature to using the Advanced Filter/Search feature within Reports & Analytics. Here are some examples for the
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 #Top 100 Pages where the pagename starts with "Categories" #Uses searchKW argument queue_ranked_pages_search <- QueueRanked("<reportsuite>", "2013-01-01", "2014-01-28", c("pageviews", "visits"), "page", top = "100", searchKW = "^Categories" ) #Top 100 Pages where the pagename starts with "Categories" OR contains "Home Page" #Uses searchKW and searchType arguments queue_ranked_pages_search_or <- QueueRanked("<reportsuite>", "2013-01-01", "2014-01-28", c("pageviews", "visits"), "page", top = "100", searchKW = c("^Categories", "Home Page"), searchType = "OR" )
QueueTrended function calls work in a similar manner, returning elements broken down by time rather than a single record per element name.
Realtime Reporting API
Accessing the Adobe Analytics Realtime API now has limited support in RSiteCatalyst. Note that this is different than just using the
currentData parameter within the
Queue* functions, as the realtime API methods provide data within a minute of that data being generated on-site. Currently, RSiteCatalyst only supports the most common types of reports:
Overtime (no eVar or prop breakdown) and one-element breakdown.
Because of the extensive new functionality for the
GetRealTimeReport() functions, code examples will be provided as a separate blog post.
Variable request timing for Queue function calls
This feature is to fix the issue of having an API request run so long that RSiteCatalyst gave up on retrieving an answer. Usually, API requests come back in a few seconds, but in selected cases a call could run so long as to exhaust the number of attempts (previously, 10 minutes). You can use the
waitTime arguments to specify how many times you’d like RSiteCatalyst to retrieve the report and the wait time between calls:
1 2 3 4 5 6 7 8 9 10 11 12 #Change timing of function call #Wait 30 seconds between attempts to retrieve the report, try 5 times queue_overtime_visits_pv_day_social_anomaly2 <- QueueOvertime("<reportsuite>", "2013-01-01", "2014-01-28", c("visits", "pageviews"), "day", "Visit_Social", anomalyDetection = "1", currentData = "1", maxTries = 5, waitTime = 30)
If you don’t specify either of these arguments, RSiteCatalyst will default to trying every five seconds to retrieve the report, up to 120 tries.
New Contributor: Willem Paling
I’m pleased to announce that I’ve got a new contributor for RSiteCatalyst, Willem Paling! Willem did a near-complete re-write of the underlying code to access the API, and rather than have multiple packages out in the wild, we’ve decided to merge our works. So look forward to better-written R code and more complete access to the Adobe Analytics API’s in future releases…
If you run into any problems with RSiteCatalyst, please file an issue on GitHub so it can be tracked properly. Note that I’m not an Adobe employee, so I can only provide so much support, as in most cases I can’t validate your settings to ensure you are set up correctly (nor do I have any inside information about how the system works :) )
Edit 2/20/2014: I mistakenly forgot to add the new real-time functions to the R NAMESPACE file, and as such, you won’t be able to use them if you are using version 1.3. Upgrade to 1.3.1 to access the real-time functionality.