CustomerLabs + Drip Integration

Drip is an ecommerce CRM (ECRM) designed for building personal and profitable customer relationships at scale. Integrating CustomerLabs with Drip enables behavioral event data and unified user traits collected by CustomerLabs to be forwarded directly into Drip, powering targeted messaging, automation workflows, and customer segmentation.

Authentication requires two credentials from Drip: an Account ID and an API Token.

Prerequisites

• An active CustomerLabs account
• An active Drip account with access to Settings

Retrieving Drip Credentials

Account ID

Log in to your Drip account and navigate to Settings → Account → Account ID.

Copy the Account ID — this value will be required during destination configuration in CustomerLabs.

API Token

In Drip, navigate to Profile → User Settings → API Token and copy the API Token.

Caution

The API Token grants programmatic access to your Drip account. Do not expose it in client-side code or share it publicly.

Configuring the Drip Destination in CustomerLabs

Select the Destination

Log in to your CustomerLabs account and navigate to Destinations from the home screen. Search for Drip and select it from the list.

Enter the Account ID

1. In the pop-up screen, click Enable, then open Configuration Settings.

   

2. Paste the Account ID copied from Drip into the designated field.

   

Enter the API Token

1. In Configuration Settings, locate the Integrate with Drip via REST API section.

2. Paste the API Token into the designated field.

3. Click Save Changes.

   

Configuring the Event Workflow

The Event Workflow controls which tracked events are forwarded to Drip and how they are processed before transmission.

Open the Event Workflow

From the Drip destination screen, click Setup Event Workflow. The workflow displays the events previously configured in CustomerLabs, each with server-side and client-side callback options.

Server-Side and Client-Side Callbacks

Each event supports two callback modes:

Callback Type	Description
Server-side	Modifies and forwards event data from the CustomerLabs server to Drip. Suitable for reliable, unblockable delivery.
Client-side	Collects user event data from the browser via the CustomerLabs Action Recorder before forwarding. Suitable for real-time browser interactions.

Use the On/Off toggle on each event to enable or disable forwarding for that event. Click Save Changes after configuring the toggles.

Configuring Trigger Paths

Trigger paths define the URL conditions under which tracking for a given event fires.

Define URL Rules

From the Drip destination screen, click Setup Trigger Path on the relevant event row. Then:

1. Enter the URL or URL pattern for the page on which the event should fire.

   

2. Use the Fire / Don’t Fire toggle to set whether the event should trigger or be suppressed on the specified path.

3. Click Save Changes.

   

Note

Multiple trigger paths can be configured per event to build precise URL-based firing rules — for example, firing only on product or checkout pages while suppressing on informational pages.

The Drip destination is now active. CustomerLabs will forward the enabled events to Drip based on the configured trigger paths, where they will be available for ecommerce workflows, behavioral segmentation, and automated messaging.

Quick Reference

Setting	Value
Auth Type	Account ID + API Token
Account ID Location	Drip → Settings → Account → Account ID
API Token Location	Drip → Settings → User → API Token
Where to Enter	CustomerLabs → Destinations → Drip → Configuration Settings