RudderStack

RudderStack is an open-source Customer Data Platform (CDP) and Reverse ETL platform, providing data pipelines that allow you to easily collect data from every application, website, and SaaS platform to activate in your warehouse and business tools. RudderStack’s Reverse ETL feature lets you use the customer data residing in your data warehouse and route it to your entire data stack, including analytics, sales, and marketing tools. 

Using RudderStack, you can set up your data warehouse as a source and easily copy data into Blueshift so that your marketing teams can leverage that data to drive action and personalize customer experiences.

Blueshift supports imports from the following types of sources in RudderStack:

• Reverse ETL - import data from a data warehouse.
• Event stream - import data from an event stream

Note: Blueshift does not support importing data from Cloud Extract sources in RudderStack.

Supported Data Warehouses

Using RudderStack you can import data from the following data warehouses into Blueshift:

• Databricks
• Google BigQuery
• AWS Redshift
• Clickhouse

Note: RudderStack supports out of the box connections with many other sources and you can import data from any of these into Blueshift.

Supported Imports

Using RudderStack you can import the following data into Blueshift:

• Customer data
• Event data (Standard events and Custom events)

Prerequisites

Before you can set up integration with Blueshift, you must complete the following steps:

1. You must have a RudderStack account set up.
2. You must set up a source in RudderStack for the data that you want to import into Blueshift. You can set up a source of type Reverse ETL or of type Event Stream.
3. You must ensure that you have access to the API keys (User API key and Event API key) in Blueshift. You can access the API keys from Account Settings > API keys in Blueshift.

Set up integration in RudderStack

To integrate with Blueshift in the RudderStack platform, complete the following steps:

1. Set up Blueshift as the destination.
2. Create a Connection in RudderStack to integrate your data warehouse or event stream with Blueshift.

Set up Blueshift as the destination

To set Blueshift as a destination in RudderStack, complete the following steps:

1. Log in to RudderStack and go to your workspace.
2. Go to Collect > Destinations and click New Destination.
3. In the Cloud Destination section, search for and select Blueshift as the destination.
4. Add a Name for the destination and click Continue.
5. On the Configure tab, add the Event API key and User API key that you copied from Blueshift.
    
    
6. Select the Data Center.
   • Select Standard for the US or Rest of the World.
   • Select EU for the EU region.
7. Click Continue.

Blueshift is now set up as a destination in RudderStack.

Connect with a data warehouse in RudderStack

To send data to Blueshift from a data warehouse, you must first set up the data warehouse as a Reverse ETL source in RudderStack. 

To create a connection with a Reverse ETL source in Rudderstack, complete the following steps:

1. Go to Connections and click the Reverse ETL source that you want to create a connection with.
2. Go to Add Destination and select the Use Existing Destination option.
   If you have not already set up Blueshift as a destination in Rudderstack, you can select the Create New Destination option and set up Blueshift as a destination.
3. Verify or edit the API keys that you added previously and click Continue.
    
    
4. Select the Schema and the Table from which you want to import data.
5. Set the Sync Mode as Upsert.
6. Select the Primary Key for the table.
7. Select the Event Type. 
   • Use the Identify event to import customer data into Blueshift.
   • Use the Track event to import event data into Blueshift.
8. If you select Event Type as Track, add the Event Name. You can also specify the column in the database table that contains the event name by selecting the “lookup event name by column” option.
9. Select the column that is to be used as the customer identifier.
    
    
10. Data is fetched from the table and is mapped to fields in Blueshift.
     
     
    • The field in the JSON trait key column is the field in Blueshift. You can edit the name of the field as required.
    • You can also select the fields that you want to import into Blueshift.
11. Verify the mapping and click Continue.
12. Your connection is completed.
13. Go to the Settings tab for the source and set up a Sync schedule.

Connect with an Event Stream in RudderStack

To send data to Blueshift via an event stream, you must first set up an event streaming source in RudderStack.

To create a connection with an Event Stream source in Rudderstack, complete the following steps:

1. Go to Connections and click the event streaming source that you want to create a connection with.
2. Go to Add Destination and select the Use Existing Destination option. If you have not already set up Blueshift as a destination in Rudderstack, you can select the Create New Destination option and set up Blueshift as a destination.
3. Verify or edit the API keys that you added previously and click Continue.
    

Your connection is now set up. 

Note:

• When you import data from an event stream into Blueshift, some fields from RudderStack are mapped to fields in Blueshift by default. You can also use Transformations in RudderStack to manipulate the event data before sending it to Blueshift.
• If you are importing customer data into Blueshift, it is recommended to limit the identify calls to 50 per second.

Import customer data into Blueshift

Use the Identify call for the event streaming source to create new or update existing customers in Blueshift.

It is recommended to limit the identify calls to 50 per second.

The following table lists the default field mappings between RudderStack and Blueshift. You can also use Transformations in RudderStack to manipulate event data and map additional fields to send to Blueshift.

• You must include the email and customer ID in the payload. 
• You can include attributes other than those listed in the mapping table. Blueshift also supports custom attributes.

Field in RudderStack	Field in Blueshift	Required?
email	email	Required
userId	customer_id	Required
event	event	Optional
phone	phone_number	Optional
firstName	firstname	Optional
lastName	lastname	Optional
gender	gender	Optional

Import event data into Blueshift

Use the Track call for the event streaming source to import user events along with the associated properties in Blueshift.

The following table details the mapping between events in RudderStack and Blueshift:

Event in RudderStack	Event in Blueshift
Product Viewed	view
Product Added	add_to_cart
Order Completed	purchase
Products Searched	search
Checkout Step Viewed	checkout
Product Removed	remove_from_cart
Subscribe Interest	subscribe_interest
Unsubscribe Interest	unsubscribe_interest
Identify	identify

The following table lists the default field mappings between RudderStack and Blueshift. You can also use Transformations in RudderStack to manipulate event data and map additional fields to send to Blueshift.

• You must include the event name and atleast one customer identifier in the payload. 

Field in RudderStack	Field in Blueshift	Required?
event	event	Required
userId	customer_id	Optional
email	email	Optional
context.device.type	device_type	Optional
context.device.token	device_token	Optional
context.device.id	device_id	Optional
context.idfa/context.device.advertisingId	device_idfa	Optional
context.idfv/context.device.id	device_idfv	Optional
context.device.manufacturer	device_manufacturer	Optional
context.os.name	os_name	Optional
context.network.carrier	network_carrier	Optional
context.ip/request_ip	ip	Optional
context.address.latitude/context.location.latitude	latitude	Optional
context.address.longitude/context.location.longitude	longitude	Optional
messageId	event_uuid	Optional
properties.cookie	cookie	Optional