Check Request Status

Description

This function is called by other functions that submit a requests to Revenera API. It checks the status code returned and tells the user if there was an error code and exits the function.

Usage

check_status(request_obj)

Value

If status code is not 200, returns a message to console with appropriate error message and stops execution.

Get All Categories and Events for a List of Product Ids

Description

Returns all of the unique categories and events (basic and advanced) for each product id.

Usage

get_categories_and_events(rev_product_ids)

Arguments

Details

It is not recommended that your username be stored directly in your code. There are various methods and packages available that are more secure; this package does not require you to use any one in particular.

Value

Data frame with categories, events and event type by product id.

Examples

## Not run: 
rev_user <- "my_username"
rev_pwd <- "super_secret"
logout(rev_user, rev_pwd)
Sys.sleep(30)
revenera_auth(rev_user, rev_pwd)
product_ids_list <- c("123", "456", "789")
session_id <- revenera_auth(rev_user, rev_pwd)
category_event <- get_categories_and_events(
  product_ids_list
)

## End(Not run)

Get Metadata on Client Ids for a List of Product Ids

Description

Returns metadata (what Revenera calls "properties") for every Client Id installed during user-provided date range for all product Ids in a list.

Usage

get_client_metadata(
  rev_product_ids,
  product_properties_df,
  desired_properties,
  installed_start_date,
  installed_end_date,
  chatty = FALSE
)

Arguments

Details

It is not recommended that your username be stored directly in your code. There are various methods and packages available that are more secure; this package does not require you to use any one in particular.

This API call can only return 200 Client Ids at a time. It will take a long time to execute if you have many Client Ids, as the function will submit requests to the API repeatedly; this may even result in a timeout error from the server. In order to provide data for troubleshooting this function will write a message to the console after each call. It is recommended that you divert the console output to a text file. You can do this in multiple ways, including with the sink function (see example for how to do this).

For the same reason you are encouraged to break your request into smaller chunks using the install dates and/or splitting up your product Ids.

Value

Data frame with selected properties for each Client Id.

Examples

## Not run: 
rev_user <- "my_username"
rev_pwd <- "super_secret"
logout(rev_user, rev_pwd)
Sys.sleep(30)
revenera_auth(rev_user, rev_pwd)
product_ids_list <- c("123", "456", "789")
product_properties <- get_product_properties(product_ids_list)
sink("output_filename.txt") # write out chatty messages to a file
sink(stdout(), type = "message")
client_metadata <- get_client_metadata(
  product_ids_list, product_properties, c("Property1", "Property2"),
  start_date, end_date, chatty = TRUE
)
sink()

## End(Not run)

Get Daily Property Values for All Clients for a List of Product Ids

Description

Returns the list of daily client properties for all the client Ids installed during a user provided date range for all the Product Ids. In order to decrease how much is returned only the first date for a property value is returned. For example, if Property A had value 1 for 3 days, then value 2 for 2 days, then value 1 again on day 6, it will return the day 1 value of 1, day 4 value of 2, and day 6 value of 1.

Usage

get_daily_client_properties(
  rev_product_ids,
  product_properties_df,
  desired_properties,
  installed_start_date,
  installed_end_date,
  daily_start_date,
  daily_end_date,
  chatty = FALSE
)

Arguments

Details

It is not recommended that your username be stored directly in your code. There are various methods and packages available that are more secure; this package does not require you to use any one in particular.

This API call can only return 200 Client Ids at a time. It will take a long time to execute if you have many Client Ids, as the function will submit requests to the API repeatedly; this may even result in a timeout error from the server. In order to provide data for troubleshooting this function will write a message to the console after each call. It is recommended that you divert the console output to a text file. You can do this in multiple ways, including with the sink function (see example for how to do this).

For the same reason you are encouraged to break your request into smaller chunks using the install dates and/or splitting up your product Ids.

Value

Data frame with first date a property value appears until it changed for each Client Id.

Examples

## Not run: 
rev_user <- "my_username"
rev_pwd <- "super_secret"
logout(rev_user, rev_pwd)
Sys.sleep(30)
revenera_auth(rev_user, rev_pwd)
product_ids_list <- c("123", "456", "789")
product_properties <- get_product_properties(product_ids_list)
sink("output_filename.txt") # write out chatty messages to a file
sink(stdout(), type = "message")
daily_client_properties <- get_daily_client_properties(product_ids_list,
  product_properties, c("Property1", "Property2"), 
  installed_start_date = "01-01-2020", installed_end_date = "01-31-2020",
  daily_start_date = "01-01-2020", daily_end_date = "01-31-2020",
  chatty = TRUE
)
sink()

## End(Not run)

Get All Properties for a List of Product Ids

Description

Returns all of the unique properties (standard and custom) for each product id by property category.

Usage

get_product_properties(rev_product_ids)

Arguments

Details

It is not recommended that your username be stored directly in your code. There are various methods and packages available that are more secure; this package does not require you to use any one in particular.

Value

Data frame with properties and property attributes by product id.

Examples

## Not run: 
rev_user <- "my_username"
rev_pwd <- "super_secret"
logout(rev_user, rev_pwd)
Sys.sleep(30)
revenera_auth(rev_user, rev_pwd)
product_ids_list <- c("123", "456", "789")
product_properties <- get_product_properties(product_ids_list)

## End(Not run)

Get Raw Data Files

Description

Retrieves a list of raw data file exports that are available for a list of product IDs and the download URL for each file.

Usage

get_raw_data_files(rev_product_ids, days_back)

Arguments

Details

Raw data files are an add-on service available through Revenera. If these files are available they can be downloaded manually from the user portal, or downloaded via R. This function uses the API to first retrieve the list of files, and then get the download URL for each file.

It is not recommended that your username be stored directly in your code. There are various methods and packages available that are more secure; this package does not require you to use any one in particular.

Value

Data frame with available files and URLs.

Examples

## Not run: 
rev_user <- "my_username"
rev_pwd <- "super_secret"
logout(rev_user, rev_pwd)
Sys.sleep(30)
revenera_auth(rev_user, rev_pwd)
product_ids_list <- c("123", "456", "789")
urls_df <- get_raw_data_files(product_ids_list, days_back = 3)
urls <- urls_df %>% pull(download_url)
file_names <-  urls_df %>%   pull(file_name)
file_list <- dplyr::pull(files_df, var = file_name)
dl_and_write <- function(u, f) {
  download.file(u, mode = "wb", destfile = f)
  upload_blob(cont, src = f, dest = paste0("/zip/", f))
  file.remove(f)
}
purrr::map2(urls, file_names, purrr::possibly(dl_and_write, "Download Error"))

## End(Not run)

Get Users by Product ID, Type, and Various Date Spans

Description

For a given period of time (a day, week, or month) Revenera's API summarizes and returns the number of active users. With this function you can return daily, weekly, or monthly active users for multiple product ids.

Usage

get_users(
  rev_product_ids,
  user_type,
  rev_date_type,
  rev_start_date,
  rev_end_date,
  lost_days = 30,
  lost_reported = "dateLastSeen",
  group_by = "clientId",
  optional_json = ""
)

Arguments

Details

You can specify a start and end date but Revenera does not store an indefinite period of historical data.

It is not recommended that your username be stored directly in your code. There are various methods and packages available that are more secure; this package does not require you to use any one in particular.

The optional_json parameter is available so that other optional arguments can be added to the api request. This will require the user to consult the API documentation. See README for an example.

Value

Data frame with active users for each product id and unique date within the range

Examples

## Not run: 
rev_user <- "my_username"
rev_pwd <- "super_secret"
logout(rev_user, rev_pwd)
Sys.sleep(30)
revenera_auth(rev_user, rev_pwd)
product_ids_list <- c("123", "456", "789")
start_date <- lubridate::floor_date(Sys.Date(), unit = "months") - months(6)
end_date <- Sys.Date() - 1
global_filter <- paste0(
  ",\"globalFilters\":{\"licenseType\":",
  "{\"type\":\"string\",\"value\":\"purchased\"}}"
)
monthly_active_users <- get_users(product_ids_list,
  "active",
  "month",
  start_date,
  end_date,
  optional_json = global_filter
)

## End(Not run)

Remove authorization cookies (logout).

Description

Use this to remove the current authorization before re-authorizing.

Usage

logout(rev_username, rev_password)

Arguments

Details

It is not recommended that these values be stored directly in your code. There are various methods and packages available that are more secure; this package does not require you to use any one in particular.

Value

Nothing (successful logout), or an error message.

Examples

## Not run: 
rev_user <- "my_username"
rev_pwd <- "super_secret"
revenera_auth(rev_user, rev_pwd)
logout(rev_user, rev_pwd)

## End(Not run)

Login and Obtain Revenera API Session Id

Description

An authorizaton cookie must first be established before querying for data. This is done using your Revenera username and password. If there is an active cookie this function will fail. You must 'logout()' first then

Usage

revenera_auth(rev_username, rev_password)

Arguments

Details

It is not recommended that these values be stored directly in your code. There are various methods and packages available that are more secure; this package does not require you to use any one in particular.

Value

Cookie authorization (which you won't see), or an error message.

Examples

## Not run: 
rev_user <- "my_username"
rev_pwd <- "super_secret"
logout(rev_user, rev_pwd)
Sys.sleep(30)
revenera_auth(rev_user, rev_pwd)

## End(Not run)

Stop Function Quietly

Description

Quit a function execution without printing error messages. The idea came from a Stack Overflow answer https://stackoverflow.com/questions/14469522/stop-an-r-program-without-error.

Usage

stop_quietly()

Value

Exits a function.