Drip Destination

Segment makes it easy to send your data to Drip (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Drip in the format they understand. Learn more about how to use Drip with Segment.

Our Drip destination code is all open-source on GitHub if you want to check it out: Javascript,(iOS and Android work via the server destination).

Getting Started

When you toggle on Drip in Segment, this is what happens:

  • Our CDN is updated within 5-10 minutes. Then our snippet will start asynchronously loading Drip’s track.js onto your page. This means you should remove Drip’s snippet from your page.
  • Since Drip only records custom events and custom user data, no events or users will appear in Drip until you start using the API outlined below.


When you call identify on analytics.js, we call identify on Drip and pass through all of the user traits that were included on that call. You must pass email as a trait to identify the user to Drip. Note that if you want to do cross-domain tracking, after you’ve enabled it in the Drip UI, you’ll need to pass email as a trait on the identify call on both domains.


When you call track, we’ll send the event to Drip with the event name and all properties that you specified. If you include revenue as a property, it will get passed to Drip as the conversion value of this event.


  • If you are sending custom server side events, you must include an email property of the user that the event belongs to.

  • Only conversions that are attributed to a Drip email delivery will show on the conversions dashboard page.

Sending Data from Drip

Drip supports sending email events to other tools on the Segment platform. These events will be sent as track calls to the other destinations you’ve turned on.


You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property order_completed_last_30days: true, and when this user no longer satisfies we will set that value to false.

When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.

Supported Sources and Connection Modes

📱 Device-based
☁️ Cloud-based

To learn more about about Connection Modes and what dictates which we support, see here.


Segment lets you change these destination settings via your Segment dashboard without having to touch any code.

Account Key

Your account ID can be found on your Site Setup page under 3rd-Party Integrations. It should be a 7, 8, or 9 character numerical string, like this: 83702741.

Campaign ID

Your campaign ID can be found in your Campaigns page. Copy a campaign URL, the campaign ID will be the last segment of that url e.g (https://www.getdrip.com/account_id/campaigns/campaign_id). If you need to set this value dynamically, you can pass integrations.Drip.campaignId as an integration specific option and we will respect that. IMPORTANT: If you put a value in here, we will by default try to subscribe every user to this campaign ID.

API Token

Your API Token can be found in your User Settings. It should be 20 character alphanumeric string, like: bmrdc6hczyn8yss8o8td.

Questions? Need help? Contact us!
Can we improve this doc?
Email us: docs-feedback@segment.com!