On This Page
Drip is an email marketing automation software designed for ecommerce brands, helping online retailers convert leads into paying customers. Using Drip’s simple, user-friendly visual campaign builder, you can design email campaigns based on specific subscriber behavior to maximize sales and repeat purchases by the subscriber.
You can replicate the data from your Drip account to a Destination database or data warehouse using Hevo Pipelines. Hevo ingests the data objects in Full Load mode. Refer to section, Data Model for the list of supported objects.
Drip authenticates API requests from Hevo to access your account data with HTTP Basic authentication.
The Account ID of the Drip account from which data is to be ingested.
The API token to provide Hevo access to your Drip account data.
Obtaining the Account ID and API Token
Drip authenticates requests from Hevo to access the information about your users and accounts with your account ID and API token.
Obtaining the Account ID
Perform the following steps to obtain your account ID:
Log in to your Drip account.
Copy the account ID from the URL path of the Drip dashboard, and save it in a secure location like any other password. For example, if the URL path is https://www.getdrip.com/123456/dashboard, the account ID is 123456.
Obtaining the API Token
Perform the following steps to retrieve your API token:
Log in to your Drip account.
In the left navigation pane, click Settings, and then click User Settings.
In the User Info page, scroll down to find your API Token.
Copy the API token, and save it in a secure location like any other password. Use this token in Hevo to configure your Drip Source.
Configuring Drip as a Source
Perform the following steps to configure Drip as the Source in your Pipeline:
Click PIPELINES in the Asset Palette.
Click + CREATE in the Pipelines List View.
In the Select Source Type page, select Drip.
In the Configure your Drip Source page, specify the following:
Click TEST & CONTINUE.
Proceed to configuring the data ingestion and setting up the Destination.
|Default Pipeline Frequency||Minimum Pipeline Frequency||Maximum Pipeline Frequency||Custom Frequency Range (Hrs)|
|1 hr||1 hr||24 hrs||1-24|
Note: You must set the custom frequency in hours as an integer value. For example, 1, 2, 3 but not 1.5 or 1.75.
Hevo fetches all the objects in Full Load mode in each run of the Pipeline.
Pagination: An API response for each Drip object fetches one page with up to 100 records, except the response for the Subscribers object, that can contain up to 1000 records per page.
API Rate Limit: The Drip API allows a maximum of 3600 individual requests per hour. Exceeding the API rate limit returns the error message: API rate limit exceeded. Please try again in an hour.
Schema and Primary Keys
Hevo uses the following schema to upload the records in the Destination database:
The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:
|Subscribers (People)||Contains the details of your active and inactive subscribers.|
|Single-Email Campaigns (Broadcasts)||Contains the details of your email-series campaigns. An email series campaign is a set of predetermined emails triggered by certain customer actions to maximize their engagement.|
|Email Series Campaigns (Campaigns)||Contains the details of your email-series campaigns. An email series campaign is a set of predetermined emails triggered by certain customer actions to maximize their engagement.|
|Forms||Contains the details of all the forms in your Drip account. Forms are used to collect personal information about your website visitors such as their name and email address in return for a product, service, or free trial. For example, users can provide their name and email address to sign up for your newsletter.|
|Conversions (Goals)||Contains the details of the conversions recorded for your Drip account.|
Hevo currently does not support deletes. Therefore, any data deleted in the Source may continue to exist in the Destination.
The data is loaded in Full Load mode in each Pipeline run. As a result, you cannot load the historical data alone at any time.
Refer to the following table for the list of key updates made to this page:
|Date||Release||Description of Change|