Sync data from Customer.io to your warehouse destination via RudderStack.
Customer.io is a popular marketing platform for sending targeted emails and push and SMS notifications to improve conversions and customer engagement.
This document guides you in setting up Customer.io as a source in RudderStack. Once configured, RudderStack automatically ingests your Customer.io data and routes it to your specified data warehouse destination.
Go to Sources > New source > Cloud Extract and select Customer.io from the list of sources.
Assign a name to your source and click Continue.
To set up Customer.io as a Cloud Extract source, you need to configure the following settings:
App API Key: Enter your Customer.io API key which can be obtained in the Customer.io dashboard by navigating to Settings > Account Settings > API Credentials.
Cutoff Days: Enter the number of days after which RudderStack fetches the updated data.
The following settings specify how RudderStack sends the data ingested from Customer.io to the connected warehouse destination:
Table prefix: RudderStack uses this prefix to create a table in your data warehouse and loads all your Customer.io data into it.
Schedule Settings: RudderStack gives you three options to ingest the data from Customer.io:
Basic: Runs the syncs at the specified time interval.
CRON: Runs the syncs based on the user-defined CRON expression.
Manual: You are required to run the syncs manually.
For more information on the schedule types, refer to the Common Settings guide.
Selecting the data to import
You can choose the Customer.io data you want to ingest by selecting the required resources:
The below table lists the syncs supported by the Customer.io resources to your warehouse destination:
Full Refresh sync
For more information on the Full Refresh and Incremental sync modes, refer to the Common Settings guide.
RudderStack ingests the Customer.io data using the Customer.io Beta API which limits the API requests by 10 requests per second.
Customer.io is now configured as a source. RudderStack will start ingesting data from Customer.io as per your specified schedule and frequency.
You can further connect this source to your data warehouse by clicking on Add Destination:
Use the Use Existing Destination option if you have an already-configured data warehouse destination in RudderStack. To configure a data warehouse destination from scratch, select the Create New Destination button.
Is it possible to have multiple Cloud Extract sources writing to the same schema?
Yes, it is.
RudderStack associates a table prefix for every Cloud Extract source writing to a warehouse schema. This way, multiple Cloud Extract sources can write to the same schema with different table prefixes.
How does RudderStack count the events for Cloud Extract sources?
RudderStack counts the number of records returned by the source APIs when queried during each sync. It considers each record as an event.
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
for the working of basic functionalities of the website. We also use third-party cookies that
analyze and understand how you use this website. These cookies will be stored in your browser
consent. You also have the option to opt-out of these cookies. But opting out of some of these
have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.