Drip quick info
Drip accepts data in cloud-mode from all source types, and can accept data in device-mode from Analytics.js sources.
When you enable Drip in the Segment web app, your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts 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.
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, Personas 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), Personas sets that value to
When you first create an audience, Personas 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.
Supported Sources and Connection Modes
Before you start, make sure Drip supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.
Segment offers an optional Device-based Connection Mode for Mobile data going to Drip, so that you can use Drip features that collect data directly from the mobile device. To do this, you must package the Segment-Drip mobile SDK with the Segment mobile library.
Segment lets you change these destination settings from the Segment app 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, 8, or 9 character numerical string, like this:
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.
This page was last modified: 20 Oct 2020
Questions? Problems? Need more info? Contact us, and we can help!