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.
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
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
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.
Supported Sources and Connection Modes
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.
Your API Token can be found in your User Settings. It should be 20 character alphanumeric string, like:
Your account ID can be found on your Site Setup page under 3rd-Party Integrations. It should be a 7 to 8 character numerical string, like this: