# Drip (Actions) Destination ## Destination Info * Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls. * Refer to it as **Drip (Actions)** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object) * This integration is **partner owned.** Please reach out to the partner's support for any issues. * This destination is **Beta.** [Drip](https://www.getdrip.com) 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](mailto:support@drip.com). ## Getting started 1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog) search for "Drip (Actions)". 2. Select Drip (Actions) and click **Add Destination**. 3. Select an existing Source to connect to Drip (Actions). 4. Go to the [Drip dashboard](https://www.getdrip.com/dashboard) 5. In the Settings tab, select the User Settings, find and copy the **API key** at the bottom of the page. 6. In a terminal, run `echo : | base64` to encode the API key. 7. Enter the encoded **API Key** in the Drip destination settings in Segment. 8. 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/`. 9. Enter the **Account ID** in the Drip destination settings in Segment. ## Destination Settings | Field | Description | Required | Type | | ---------- | ---------------------------------------------------------------------------------- | -------- | -------- | | Account ID | Account ID for your Drip account. You can find this in your Drip account settings. | Yes | string | | API Key | API key for your Drip account. You can find this in your Drip account settings. | Yes | password | ## Available Presets Drip (Actions) has the following presets | Preset Name | Trigger | Default Action | | ----------- | ----------------------- | -------------- | | Track event | Event type = "track" | Track Event | | Identify | Event type = "identify" | Identify | ## Available Actions Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Drip-supported actions: > \[!NOTE] > > Individual destination instances have support a maximum of 50 mappings. * [Track Event](#track-event-33) * [Identify](#identify-10) ### Track Event Send track() events to Drip Track Event is a **Cloud** action. The default Trigger is `type = "track"` | Field | Description | Required | Type | | ------------- | ------------------------------------------------ | -------- | ------ | | Action | The name of the action. | Yes | STRING | | Email Address | The person's email address. | Yes | STRING | | Properties | Additional properties associated with the event. | No | OBJECT | ### Identify Identify person in Drip Identify is a **Cloud** action. The default Trigger is `type = "identify"` | Field | Description | Required | Type | | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------- | -------- | -------- | | Custom fields | Custom fields to add to a person's profile. Non string values will be stringified. | No | OBJECT | | Email Address | The person's email address. | Yes | STRING | | IP Address | The person's ip address. | No | STRING | | SMS Number | The person's sms number. | No | STRING | | Initial Status | The person's subscription status if newly identified. | No | STRING | | Status | The person's subscription status. Overrides initial\_status. | No | STRING | | Status Updated At | The timestamp associated with the update to a person's status. | No | DATETIME | | Tags | Comma delimited list of tags to add to a person's profile. e.g. "tag1,tag2". | No | STRING | | Timezone | The person's timezone. | No | STRING | | Batch Size | Maximum number of events to include in each batch. Actual batch sizes may be lower. Max size must be between 1 and 1000 inclusive. | No | INTEGER | | Enable Batching? | When enabled, Segment will send events in batches. | No | BOOLEAN | For more information about developing with Drip, check out their [documentation](https://developer.drip.com/). ## Engage You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo). For user-property destinations, an [identify](/docs/segment/connections/spec/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. > \[!NOTE] > > 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. ## Settings Segment lets you change these destination settings from the Segment app without having to touch any code. | Field | Description | Required | Type | | ---------- | ---------------------------------------------------------------------------------- | -------- | -------- | | Account ID | Account ID for your Drip account. You can find this in your Drip account settings. | Yes | string | | API Key | API key for your Drip account. You can find this in your Drip account settings. | Yes | password |