RudderStack provides an infrastructure to track, capture, transform, and route your customer event data to your preferred destinations. However, this data can be quite raw in nature - comprising mainly of customer interactions with your website, mobile apps, or other digital assets.
While the customer event data is important to reconstruct your customers' behavior, there is scope to further enrich customer profiles by processing the other customer-related data residing in every company's main data infrastructure - the Data Warehouse.
With RudderStack's Warehouse Actions feature, you can leverage the already processed customer data residing in your data warehouse and route this enriched information to your desired destinations.
To configure your data warehouse as a source on the RudderStack dashboard, follow these steps:
Log into your RudderStack dashboard.
Navigate to Sources, present in the left panel of the dashboard.
Choose your preferred data warehouse which you want to configure as a source, as shown. Then, click on Next.
Assign a name to your source. Then, click on the Create credentials from scratch button, if you are configuring your data warehouse in the RudderStack dashboard for the first time.
Next, enter the connection credentials to configure your data warehouse connection with RudderStack, as shown:
Next, enter the data warehouse schema and the table name. RudderStack will collect the data from this table.
If the table is valid, you can then preview a snippet of the data, as shown:
You can also filter, select and edit the column names of the table to be included as the data source, as shown:
Once you've selected all the the required table columns, click on Next.
RudderStack also allows you to specify the data update frequency and set a data synchronization time as per your requirement.
That's it! Your data warehouse is now configured and added as a RudderStack source.
Now you can connect this source to any RudderStack destination of your choice. RudderStack will collect the enriched customer data from the specified table columns in your warehouse source and send it to the destination for your activation use-cases.
Currently all events from the RudderStack warehouse actions are