Omnisend

Ecommerce-focused email and SMS marketing platform with automation workflows, segmentation, and product-aware campaigns.

Datafly Signal delivers events to Omnisend’s Customer Events API server-side, with no client-side pixel. Each event triggers Omnisend custom-event automations (welcome series, abandoned cart, back-in-stock, post-purchase) and is recorded on the contact’s timeline.

Why route Omnisend through Datafly Signal

• Profiles are updated from the server, not the browser. Events reach Omnisend even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
• One consent decision governs every destination. Omnisend is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.

Prerequisites

Complete these steps in Omnisend before configuring Signal.

Configuration

Configure in Signal

Quick Setup

1. Navigate to Integrations in the sidebar.
2. Open the Integration Library tab.
3. Find Omnisend under the Marketing Automation category.
4. Click Install and paste your API key.
5. Click Install Integration to create the integration with the ready-to-use default configuration.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/omnisend/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Omnisend",
    "variant": "default",
    "config": {
      "api_key": "AjWvksZpTG4JZBdc4xxxxxxxx"
    },
    "delivery_mode": "server_side"
  }'

API Endpoint

All events are sent to:

POST https://api.omnisend.com/api/events
Authorization: Omnisend-API-Key {api_key}
Omnisend-Version: 2026-03-15
Content-Type: application/json

Omnisend returns a success status on accepted events. A 400 indicates a malformed body or a missing contact identifier; 401/403 indicate a bad or under-scoped API key.

Identity Signals

Server-side Omnisend recommended events over the Events API (POST /api/events): added product to cart, started checkout, placed order, order refunded and order fulfilled, with lineItems[], totals and eventID/eventTime de-duplication, for cart abandonment, order confirmation and follow-up automations. The contact is keyed by email (plain text, trimmed and lowercased, because Omnisend keys the contact on it) or phone (E.164); events with neither are not sent.

Consent

Omnisend events are sent under the marketing consent category. Omnisend records opt-ins and opt-outs on the contact (contact.optIns / optOuts), which Signal does not set: subscription status is managed by Omnisend’s own forms and preference centre.

Event Mapping

Blueprint 0.4.1, reviewed against the vendor’s documentation on 2026-09-23. Each preset maps the events below; every other event is dropped. Events use the canonical names from the event specs (transaction_id, value, items[], search_term); the legacy order_id, revenue and flat product fields are still read as a fallback.

Retail / E-commerce (ecommerce)

Omnisend recommended events over the Events API (POST /api/events, Omnisend-Version 2026-03-15): added product to cart and started checkout (cart and checkout abandonment), placed order, order refunded and order fulfilled (eventVersion v2), with lineItems[], order totals, the currency upper-cased and eventID/eventTime for de-duplication. Adds a signed up custom event for sign-up automations. Omnisend creates or updates the contact from contact.email (sent in plain text, trimmed and lowercased, because Omnisend keys the contact on it) or contact.phone (E.164); events with neither are not sent. viewed product is only accepted through Omnisend’s JavaScript snippet, so it is not sent server-side.

Default (default)

Omnisend recommended events over the Events API (POST /api/events, Omnisend-Version 2026-03-15): added product to cart and started checkout (cart and checkout abandonment), placed order, order refunded and order fulfilled (eventVersion v2), with lineItems[], order totals, the currency upper-cased and eventID/eventTime for de-duplication. Omnisend creates or updates the contact from contact.email (sent in plain text, trimmed and lowercased, because Omnisend keys the contact on it) or contact.phone (E.164); events with neither are not sent. viewed product is only accepted through Omnisend’s JavaScript snippet, so it is not sent server-side.

An identified purchase (preset ecommerce) is delivered as:

POST https://api.omnisend.com/api/events

{
  "contact": {
    "email": "jane.doe@example.com",
    "firstName": "Jane",
    "lastName": "Doe",
    "phone": "+447700900123"
  },
  "eventID": "3f2b8c1e-9d4a-4e7b-8f6a-2c1d0e9b7a65",
  "eventName": "placed order",
  "eventTime": "2025-09-23T04:00:00Z",
  "eventVersion": "v2",
  "origin": "api",
  "properties": {
    "createdAt": "2025-09-23T04:00:00Z",
    "currency": "GBP",
    "discounts": [
      {
        "code": "SUMMER"
      }
    ],
    "lineItems": [
      {
        "productID": "SKU_1",
        "productPrice": 120,
        "productQuantity": 2,
        "productTitle": "Helmet",
        "productVariantID": "M",
        "productVendor": "Shoei"
      },
      {
        "productID": "SKU_2",
        "productPrice": 199.99,
        "productQuantity": 1,
        "productTitle": "Gloves",
        "productVariantID": "L",
        "productVendor": "Alpinestars"
      }
    ],
    "orderID": "T-1001",
    "shippingPrice": 4.99,
    "totalPrice": 439.99,
    "totalTax": 73.33
  }
}

Testing

1. After installing the integration, trigger a test event from your website or via the Signal event API. Make sure the visitor is identified (has an email or phone).
2. In Omnisend, open Audience > Contacts and search for the test contact by email.
3. Open the contact and check the activity timeline for the delivered event.
4. In Signal, check Live Events to confirm delivery with a success status.

Troubleshooting

See also

• Klaviyo — ecommerce email/SMS alternative
• Mailchimp — email marketing alternative
• Customer.io — event-driven messaging alternative