Drip

Drip is an ecommerce email-marketing automation platform. Datafly Signal delivers your behavioural events to Drip’s REST API server-side, keyed on the subscriber’s email address. Recording an event drives Drip workflows and lead scoring, and automatically creates the subscriber in Drip when the email is new.

Because delivery is server-to-server, you remove Drip’s client-side JavaScript from your site while keeping (and improving) event coverage: events fire from your first-party Signal endpoint, are unaffected by ad blockers and ITP, and carry whatever identity your pipeline has resolved.

Prerequisites

• A Drip account with API access.
• Your Drip Account ID — found in Settings > General Info, and in the dashboard URL (app.getdrip.com/<account_id>/...).
• A Drip API Token — found under Settings > User Settings > API Token.
• A subscriber email on each event you want to deliver. Drip keys events on email; an event without an email (or Drip subscriber ID) is rejected.

Configuration

Configure in Signal

1. In Management UI, go to Integrations and add Drip.
2. Enter your Account ID and API Token.
3. Choose a preset (Retail or B2B / SaaS) or start from the default and map your events.
4. Attach the integration to the pipeline that carries the events you want to deliver.
5. Save. New events flowing through the pipeline are delivered to Drip.

API Endpoint

Signal delivers to Drip’s Record an event endpoint:

POST https://api.getdrip.com/v2/{account_id}/events

Authentication is HTTP Basic, with your API token as the username and an empty password. A successful request returns 204 No Content.

The single-event endpoint accepts up to 3,600 requests per hour. Signal applies a matching per-integration rate limit so a busy pipeline does not trip Drip’s throttle.

Identity Signals

Drip identifies the subscriber by email on the body of each event. Signal maps your resolved contact email to the email field. The email is trimmed and lowercased before sending.

You do not need to create the subscriber first: recording an event with a new email auto-creates the subscriber in Drip as a prospect. To record an event without affecting lead scoring (for example, for known customers), set prospect to false in your event mapping.

Drip’s events endpoint has no per-event consent field — consent and mailability are managed on the Drip subscriber record. Gate delivery with a pipeline-level consent filter if you only want to forward events for consented contacts.

Event Mapping

Signal’s GA4-style event names map to Drip actions. The vendor_event_name becomes Drip’s action, the subscriber email becomes email, and everything else lands in the properties object. Drip’s convention is to store conversion value in cents under properties.value, so revenue mappings multiply by 100.

Example — an Order Completed event from Datafly.js:

datafly.track("Order Completed", {
  order_id: "ORD-1001",
  revenue: 79.99,
  currency: "USD",
  coupon: "SUMMER10"
});

Resulting payload delivered to Drip (revenue 79.99 stored as value: 7999 cents):

{
  "events": [
    {
      "email": "jane@example.com",
      "action": "Order Completed",
      "occurred_at": "2026-06-06T10:15:00Z",
      "properties": {
        "order_id": "ORD-1001",
        "value": 7999,
        "currency": "USD",
        "coupon": "SUMMER10"
      }
    }
  ]
}

Default event map (Retail preset)

The B2B / SaaS preset maps Signed Up, Logged In, Trial Started, and Subscription Started instead. Events not present in your chosen preset are dropped by default.

Testing

1. Send a test event through your pipeline (for example, trigger an Order Completed on a staging site, or replay an event from the Event Debugger).
2. In Signal’s Event Debugger, confirm the Drip delivery returned 204 No Content.
3. In Drip, open the subscriber by email and check Activity — the event should appear as the mapped action with its properties. Batch processing means there can be a short delay before it shows.

Troubleshooting