Sync data from SendGrid to your warehouse destination via RudderStack.
SendGrid is an email delivery and marketing tool that lets you build and deliver personalized experiences through their API and marketing automation flows.
This document guides you in setting up SendGrid as a source in RudderStack. Once configured, RudderStack automatically ingests your SendGrid data and routes it to your specified data warehouse destination.
Go to Sources > New source > Cloud Extract and select SendGrid from the list of sources.
Assign a name to your source and click Next.
Enter the following connection credentials to authenticate your SendGrid account with RudderStack:
SendGrid API key: Enter your SendGrid API key by going to your SendGrid dashboard and navigating to Settings > API Keys.
Start time: Choose the start date from which you want RudderStack to ingest the SendGrid data. RudderStack will not replicate any data before this date.
For more information on the required permissions for the API key, refer to the FAQ section below.
The following settings specify how RudderStack sends the data ingested from SendGrid to the connected warehouse destination:
Table prefix: RudderStack uses this prefix to create a table in your data warehouse and loads all your SendGrid data into it.
Schedule Settings: RudderStack gives you three options to ingest the data from SendGrid:
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 SendGrid data you want to ingest by selecting the required resources:
The below table mentions the syncs and API endpoints supported by these resources from SendGrid to your warehouse destination:
Full Refresh sync
SendGrid API endpoint
For more information on the Full Refresh and Incremental sync modes, refer to the Common Settings guide.
Note the following restrictions for the campaigns, messages, and single_sends resources:
campaigns: SendGrid currently supports two kinds of marketing campaigns - legacy and new marketing campaigns. However, RudderStack only supports the new marketing campaigns.
If your SendGrid account uses legacy marketing campaigns, you might get a 403 Forbidden error while ingesting data from this resource.
messages: To ingest data from this resource, you must have purchased access to the Email Activity Feed API. For more information, refer to the SendGrid API documentation.
single_sends: RudderStack uses the stats API instead of the marketing API to ingest the data from this resource.
SendGrid is now configured as a source. RudderStack will start ingesting data from SendGrid 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.
How do I obtain the SendGrid API key?
To obtain the API key for configuring the SendGrid Cloud Extract source, follow these steps:
Log into your SendGrid dashboard.
Go to Settings > API keys.
Click the Create API key option:
Enter the name of the API key under the API Key Name field. In API Key Permissions, select Restricted Access.
Set the permissions as shown below:
Finally, click Create & View. Use these credentials to configure the source.
Copy the API key and store it securely. SendGrid will not display the API key again once you click Done.
How does RudderStack sync the SendGrid data?
Upon configuring the source, RudderStack first connects to your SendGrid instance and pulls all historical data. Subsequently, RudderStack syncs the SendGrid data based on your specified sync schedule and frequency.
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.