Sendlane

Datafly Signal delivers events to Sendlane server-to-server using the API v2 Custom Integration endpoint. Events are keyed on the contact email so Sendlane resolves or creates the contact and can trigger email and SMS automations, build segments, and track ecommerce behaviour — without a client-side Sendlane pixel.

Prerequisites

Before configuring Sendlane in Signal you need a Sendlane account with API v2 access and a Custom Integration.

Step 1: Generate an API v2 access token

1. Log in to Sendlane and go to Account > API.
2. Create or copy your API v2 access token. This is sent as a Bearer credential on every request.

Step 2: Create a Custom Integration and copy its token

1. Go to Integrations > Custom Integration in Sendlane.
2. Create a new custom integration (or open an existing one).
3. Copy the Custom Integration Token. This links incoming events to that integration and is required for event tracking.

Configuration

Configuration Fields

Configure in Signal

1. Go to Integrations > Add Integration > Sendlane.
2. Choose a variant:
   • Default — page/active-on-site, identify, and core ecommerce events.
   • Retail — full ecommerce funnel with line items, value, and currency.
3. Enter your api_token and custom_integration_token.
4. Select consent categories (typically marketing).
5. Click Save.

API Endpoint

POST https://api.sendlane.com/v2/custom-integrations/events
Authorization: Bearer {api_token}
Content-Type: application/json

The Sendlane event name lands in the event field, the Custom Integration Token in token, and the contact is identified by email. All other mapped fields are sent at the body root.

Identity Signals

Sendlane is an email-first platform: the contact is resolved by email address, which Signal maps from datafly.identify() traits to the email field on every event. When a contact does not yet exist, Sendlane creates it from the email and any contact traits (first_name, last_name, phone) carried on identify-type events.

How to send user data

Call datafly.identify() when a user registers, logs in, or submits a form:

datafly.identify("user-123", {
  email: "jane.doe@example.com",
  firstName: "Jane",
  lastName: "Doe",
  phone: "+44 7700 900123"
});

Event Mapping

Retail preset

Events not in the mapping are dropped. To customise, edit the integration’s Field Mappings in the Management UI.

Example: Order Completed event

Datafly.js call:

datafly.track("Order Completed", {
  order_id: "1001",
  revenue: 49.99,
  currency: "USD",
  products: [
    { product_id: "12345678", sku: "TS1", product_name: "tshirt #1", quantity: 1, item_price: 19.99, total: 19.99 }
  ]
});

Sendlane payload sent by Signal:

{
  "event": "order_placed",
  "token": "ABCDEFGHIJKLM1234567890",
  "email": "jane.doe@example.com",
  "order_id": "1001",
  "value": 49.99,
  "currency": "USD",
  "line_items": [
    { "product_id": "12345678", "sku": "TS1", "product_name": "tshirt #1", "quantity": 1, "item_price": 19.99, "total": 19.99 }
  ]
}

Testing

Troubleshooting