Sailthru (Marigold)

Datafly Signal delivers events to Marigold Engage by Sailthru server-to-server using the Event API. Each event is submitted against a user profile and can trigger Lifecycle Optimizer flows, Smart Strategies, and other behaviour-based messaging inside Sailthru — without a client-side Sailthru tag on your site.

Prerequisites

Before configuring Sailthru in Signal you need a Marigold Engage by Sailthru account and your API credentials.

Configuration

Configure in Signal

1. Go to Integrations > Add Integration > Sailthru (Marigold).
2. Choose the Default preset (page, search, e-commerce funnel, and signup events).
3. Enter your api_key and secret.
4. Select the consent categories that apply (typically marketing).
5. Click Save.

To customise which Signal events map to which Sailthru event names, edit the integration’s Field Mappings in the Management UI. Make sure each Sailthru event name matches a listener (Lifecycle Optimizer flow, Smart Strategy, or trigger) you have set up in the Sailthru platform.

API Endpoint

POST https://api.sailthru.com/event

Every request is sent as application/x-www-form-urlencoded with four parameters:

Request signature

Sailthru does not use a static token. For every request, Signal computes a signature by sorting the values of the other parameters alphabetically, concatenating them, prepending your shared secret, and taking the MD5 hash. Signal handles this for you — you only need to supply the API Key and Shared Secret.

Identity Signals

Sailthru identifies a user profile by the id value, with key telling Sailthru what kind of identifier it is.

How to send user data

Call datafly.identify() when a user logs in, registers, or submits a form so Signal has an email to key events against:

datafly.identify("user-123", {
  email: "jane.doe@example.com"
});

Event Mapping

Default preset

Event properties are delivered as Sailthru vars, which are available in your messaging templates and Lifecycle Optimizer flows. Event vars take priority over same-named profile custom fields.

Example: Purchase event

Datafly.js call:

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 }
  ]
});

Sailthru Event API request sent by Signal (the json form parameter, decoded):

{
  "id": "jane.doe@example.com",
  "key": "email",
  "event": "purchase",
  "vars": {
    "order_id": "ORD-001",
    "revenue": 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 }
    ],
    "marketing_consent": "1"
  }
}

The full request body also carries api_key, format=json, and the computed sig.

Testing

1. In the Management UI, open your Sailthru integration and use the Event Debugger to inspect the request Signal builds for a sample event.
2. Trigger an event on your site (e.g. complete a test purchase with a known email).
3. In the Sailthru platform, open the user’s profile and confirm the event appears under their activity, with the expected vars.
4. If you have wired a Lifecycle Optimizer flow to the event name, confirm the profile enters the flow.

Troubleshooting