Courier

Datafly Signal delivers events to Courier server-to-server using the Send API. Each delivered Signal event triggers a Courier notification for the recipient, routed across whatever channels your Courier template defines (email, SMS, push, chat, in-app). Signal maps the recipient’s identity into the notification and passes the event properties through as template variables.

Because delivery happens from your own Signal backend, there is no client-side Courier SDK on the page and no browser API key to expose.

Prerequisites

Before configuring Courier in Signal, you need a Courier account, an API key, and a notification template.

Step 1: Create a Courier account

If you don’t already have one, sign up at app.courier.com and complete the onboarding.

Step 2: Create a notification template

1. In the Courier dashboard, go to Designer.
2. Click Create Notification and design the message for the channels you want (email, SMS, push, etc.).
3. Use template variables (e.g. {order_id}, {amount}) where you want event data to appear. These map to the values Signal sends in message.data.
4. Publish the notification and note its template id (the slug you reference in the API).

Step 3: Get your API key

1. Go to Settings > API Keys (app.courier.com/settings/api-keys).
2. Copy a production API key.

Configure in Signal

Configuration Fields

Management UI Setup

API Endpoint

POST https://api.courier.com/send
Authorization: Bearer {api_key}
Content-Type: application/json

A successful request returns HTTP 202 with a requestId you can use to track delivery in the Courier dashboard.

Identity Signals

Courier delivers to a recipient, so identity is about who to notify — not probabilistic ad matching. Signal maps the following into message.to:

How to send recipient data

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

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

Signal forwards these into message.to so Courier knows who to notify and how.

Event Mapping

The Default preset maps these Signal events. Event properties land in message.data, where they become template variables. Unmapped events are dropped.

To customise, edit the integration’s Field Mappings in the Management UI.

Example: Order Completed event

Datafly.js call:

datafly.identify("user-123", { email: "jane.doe@example.com" });
 
datafly.track("Order Completed", {
  order_id: "ORD-001",
  revenue: 129.99,
  currency: "USD",
  products: [
    { product_id: "SKU-A", name: "Widget", price: 49.99, quantity: 2 },
    { product_id: "SKU-B", name: "Gadget", price: 30.01, quantity: 1 }
  ]
});

Courier Send API payload sent by Signal:

{
  "message": {
    "to": {
      "user_id": "user-123",
      "email": "jane.doe@example.com"
    },
    "template": "order_confirmation",
    "data": {
      "order_id": "ORD-001",
      "amount": 129.99,
      "currency": "USD",
      "items": [
        { "product_id": "SKU-A", "name": "Widget", "price": 49.99, "quantity": 2 },
        { "product_id": "SKU-B", "name": "Gadget", "price": 30.01, "quantity": 1 }
      ]
    }
  }
}

In your Courier template, reference these as {order_id}, {amount}, {currency}, and loop over {items}.

Testing Your Integration

Troubleshooting

Rate Limits

Courier rate-limits the API per plan. Signal applies a conservative client-side limit (10 requests/second sustained, burst 20) to stay within typical ceilings; adjust this for your Courier plan if you send at higher volume.