Drip (Actions) Destination
Drip is a nurture marketing platform Empowering B2C SMBs to convert long-sales cycle prospects into lifelong buyers with sophisticated and personalized marketing automation.
This destination is maintained by Drip. For any issues with the destination, contact their Support team.
- From your workspace's Destination catalog page search for "Drip (Actions)".
- Select Drip (Actions) and click Add Destination.
- Select an existing Source to connect to Drip (Actions).
- Go to the Drip dashboard
- In the Settings tab, select the User Settings, find and copy the API key at the bottom of the page.
- In a terminal, run
echo <your-api-key>: | base64to encode the API key. - Enter the encoded API Key in the Drip destination settings in Segment.
- Your account ID is a seven digit number that can be found in the address bar of your browser when you are logged into Drip. It is the number after
https://www.getdrip.com/. - Enter the Account ID in the Drip destination settings in Segment.
Account ID for your Drip account. You can find this in your Drip account settings.
API key for your Drip account. You can find this in your Drip account settings.
Drip (Actions) has the following presets
| Preset Name | Trigger | Default Action |
|---|---|---|
| Track event | Event type = "track" | Track Event |
| Identify | Event type = "identify" | Identify |
Build your own Mappings. Combine supported triggers with the following Drip-supported actions:
Mapping limits per destination
Send track() events to Drip
Track Event is a Cloud action. The default Trigger is type = "track"
The name of the action.
The person's email address.
Optional
Additional properties associated with the event.
Identify person in Drip
Identify is a Cloud action. The default Trigger is type = "identify"
Optional
Custom fields to add to a person's profile. Non string values will be stringified.
The person's email address.
Optional
The person's ip address.
Optional
The person's sms number.
Optional
The person's subscription status if newly identified.
Optional
The person's subscription status. Overrides initial_status.
Optional
The timestamp associated with the update to a person's status.
Optional
Comma delimited list of tags to add to a person's profile. e.g. "tag1,tag2".
Optional
The person's timezone.
Optional
When enabled, Segment will send events in batches.
For more information about developing with Drip, check out their documentation.
You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.
For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to false.
When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Real-time to batch destination sync frequency
Real-time audience syncs to Drip (Actions) may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.
Segment lets you change these destination settings from the Segment app without having to touch any code.
Account ID for your Drip account. You can find this in your Drip account settings.
API key for your Drip account. You can find this in your Drip account settings.