Customerlabs CDP Documentation

You are here:

Source – Drift

(A ‘Source’ platform is one where data can be brought in from any platform into CustomerLabs CDP)

Drift is the Conversational Marketing platform that combines chat, email, video, and automation to remove the friction from business buying. With Drift, you can start conversations with future customers now, on their terms. 

The CustomerLabs CDP + Drift integration will enable marketers to bring their all customer related data from Drift into Customerlabs CDP in order to enrich existing user profiles, create targeted segments & sync them with other marketing tools to personalize engagement. 

Getting Started

Codelessly connect your Drift account with CustomerLabs CDP by following the steps below. 

  1. Login to CustomerLabs CDP and navigate to Sources
Sources in CustomerLabs CDP
  1. Choose Drift from the list of apps
Drift as a Source in CustomerLabs CDP sources tab
  1. Click on Authenticate Drift 
Drift authentication in CustomerLabs CDP to integrate Drip and CustomerLabs CDP
  1. You will be redirected to your Drift account, login and authorize CustomerLabs CDP to access your Drift customer data
Integrating CustomerLabs CDP with Drift
  1. Post authorization you will be prompted to choose the CustomerLabs CDP account to receive data from Drift (in case of multiple accounts)
  2. Choose the account and click confirm
Drift and CustomerLabs CDP direct integration Confirm button inside CustomerLabs CDP for the drift data to be synced in.
  1. Voila! You will now be able to receive customer data from Drift. You can now setup the workflow by clicking on Next: Workflow set up.
Drift Authentication in CustomerLabs to next move on to workflow setup

Building Workflows in CustomerLabs CDP

Setting up a workflow in CustomerLabs CDP will allow you to receive notifications about changes that happen to your Drift data in real-time. 

Learn more about the events that you will be able to receive from drift. 

The Contact Update Subscriptions webhook is the major event from Drift as it enables staying in sync with updates that occur to Drift contacts (when used in tandem with the contact_identified webhook).

The below workflow can be used to bring Contact data to CustomerLabs CDP when a new contact is created/updated in Drift. 

1. Give a name to your workflow and before proceeding, and create a test contact in Drift to get related data samples. Once your new contact is created, click on Choose sample data

Workflow setup in Customerlabs CDP

2. You will now be able to view relevant event samples in CustomerLabs CDP

3. Click on view details to see more information about incoming samples

Sample data list for the data imported from Drift

4. Select any one sample that suits your requirements & Click Select this sample

Raw sample data to choose to have the complete workflow set up

5. The filter screen acts as a roadblock to stop other non-related event data coming in from Drift & skew existing information. Click on Create filter criteria to give your filter condition – this will allow only contact_updated event from Drift to enter this workflow in the future.

Filter incoming data to have full control of your data from Drip

6. Choose the event type from the dropdown as shown below and click on Next: Event configuration

Button highlighting event configuration after filling in the incoming data details

7. Give a name to your incoming event. The dynamic event mentioned here chooses the event name from the sample. You can also give a custom name or select from a list of predefined events. Here’s a detailed breakdown of the event configuration screen

Custom event or existing pre-defined events inside Customerlabs CDP

8. User Identity mapping lets you identify & combine all user-related events, since an incoming contact has an end User_Id, it can be used to identify users and combine all present and future information from Drift. Choose the field and value as shown below

User identity mapping to identify the user by email.

9. Account Identity mapping lets you combine all user company events, since an incoming company data has a company name we can select an identifier from the drop-down and assign relevant values. In case the account name is not specified in the event, this step can skipped

Account identity mapping for advanced identity graph using the company name, website, useful for B2B companies

10. Once the user & account mapping is done, you can categorically map other incoming attributes into the following buckets. After updating, click Save workflow

Map incoming data attributes into CustomerLabs CDP


Send incoming data to third-party apps to boost marketing effectiveness. Learn more about the destination tools we support.


Need assistance?

Have questions or facing issues? We can help set it up for free. 

Get in touch

Was this article helpful?
0 out Of 5 Stars
5 Stars 0%
4 Stars 0%
3 Stars 0%
2 Stars 0%
1 Stars 0%
How can we improve this article?
How Can We Improve This Article?
Need help?
Table of Contents
CustomerLabs gives freedom, flexibility and wings to digital marketers.
Sign Up

Schedule a 1-1 Demo


Unified data to boost ecommerce growth


Engage your customers across the funnel with a unified martech stack


Increase product metrics with a unified martech stack


Scale your customers quickly with the right data