Sub Rivers

Introduction

Sub Rivers provide a mechanism to embed smaller and more specialized processes within a larger and more comprehensive process. The sub-processes that are integrated into the main River can either adopt the configurations and settings of the main river, or they can have their own unique and distinct parameters and specifications. This allows for greater flexibility and customization in the data processing pipeline, and enables more efficient and effective handling of complex data flows.

Use Case

An agency uses Rivery to manage Facebook Ads data for multiple customers. Instead of duplicating the entire River configuration for each customer, the agency creates a Sub River for each customer, allowing them to tailor the data pulled specifically for that customer while maintaining common definitions across all Sub Rivers, providing scalability and reducing the need for duplication.

Working with Sub Rivers

To activate Sub Rivers, make sure to select the 'Custom Report' option in the Source tab, then select a Target. Next, navigate to the Settings tab and switch the 'Enable Sub Rivers' option to the true.

Currently supported for the following Sources:

• Shopify
• Klaviyo
• Stripe
• Google Ads
• Google Ad Manager
• Google Analytics
• YouTube Reporting
• Bing Ads
• Facebook Social
• Facebook Ads
• Jira
• Twitter Ads
• Linkedin Social
• LinkedIn Ads
• Mavenlink
• Snapchat Marketing
• Taboola
• Instagram Social
• Active Campaigns
• Hubspot
• REST (via Actions)
• TikTok

Currently supported for the following Targets:

• Snowflake
• Google BigQuery
• Azure Synapse
• Amazon Redshift
• Databricks SQL
• Azure Blob Storage

Once Sub Rivers enabled, this will result in the appearance of a "Sub Rivers" tab within the River.
To create the first Sub River, click on New Sub River, which will generate a Sub River named Sub River 1, but the name can be changed as desired.

When you choose the Source Connection option from the available parameters list, it will add that particular parameter to the list of Sub Rivers.This means that each Sub River will now have the ability to have a separate Rivery source connection while pulling data. This provides greater flexibility and control in terms of the data being retrieved, as you can specify a different source connection for each Sub River.

Each parameter has the option to specify a different value or adopt the value already established in the main River. This provides you the choice of setting a specific value only for the current parameter in question or staying consistent with the main River.

In addition, Sub Rivers can each have their own schedule (or inherit from the main River). Click the clock icon to the right of the parameter dropdown to set schedules at the Sub River-level.

Limitation

• Deployment of a River with Sub Rivers between Environments is not possible.
• Versioning of Sub Rivers is not available.
• Copying a River with Sub Rivers will not duplicate the Sub Rivers, only the primary configuration.