RudderStack lets you send your event data to Drip via the Device mode, i.e. using the native web SDK.

Identify

The identify method pushes the subscriber data to Drip. If the subscriber is not present in your account, RudderStack will create a new record for them. Otherwise, RudderStack updates the user records with the latest information.

A sample identify call is as shown:

Copy
rudderanalytics.identify(
  "6781206",
  {
    email: "sampleUser@testmail.com",
    tags: ["Customer"],
  },
  {
    externalId: [
      {
        type: "dripCampaignId",
        id: "846616660",
      },
    ],
  }
)

The following table lists the properties that RudderStack transforms and maps to Drip's standard properties:

You can subscribe a user to a Email Series Campaign by providing the associated Campaign ID. Doing so will add the subscriber directly to that email series campaign.

If you want to add a subscriber to your account without subscribing them to an email series campaign, use the identify call instead. You can also send some additional properties with the identify call. These are listed in the following table:

Track

When you call the track API, RudderStack sends the event to Drip along with its name and all of the specified properties. If you include revenue as a property, it will get passed to Drip as the conversion value of the event.

A sample track call is as shown:

Copy
rudderanalytics.track("randomProduct", {
  email: "sampleUser@rudderstackdrip.com",
  revenue: 100,
})

The following table lists the properties that RudderStack transforms and maps to Drip's standard properties:

Contact us

For any questions related to any of the sections covered in this guide, feel free to contact us or start a conversation in our Slack community.