Monetate

Datafly Signal delivers events to Monetate (now part of Kibo Personalization) server-to-server using the Engine API. Signal sends visitor context and conversion events — page views, product views, cart contents, and purchases — directly to Monetate’s decision engine so personalization, A/B testing, and recommendations work without a client-side Monetate tag.

Prerequisites

Before configuring Monetate in Signal, you need an active Monetate (Kibo Personalization) account that is provisioned for Engine API server-side integration, plus three values from your account settings.

Step 1: Confirm Engine API access

Some Monetate accounts are configured for the client-side tag only. Ask your Monetate services team to confirm your account is enabled for Engine API server-side ingestion.

Step 2: Find your retailer short name and account ID

1. In the Monetate platform, go to Settings and open the API tab of the integration page.
2. Note the retailer short name — the parent identifier for your account, used in the API endpoint path.
3. Note your account ID — the value after a_ in your channel string (for example, in a_887f2483/p/example.com the account ID is 887f2483).

Step 3: Confirm your channel domain

Confirm the site domain Monetate has configured for this account (for example example.com). Signal builds the channel string as a_{account_id}/p/{domain}.

Configure in Signal

Configuration Fields

Management UI Setup

API Endpoint

POST https://engine.monetate.net/api/engine/v1/decide/{retailer_short_name}
Content-Type: application/json

The Engine API /decide endpoint has no per-request API key or token. Each request is scoped to your account by the retailer_short_name in the URL path and the channel field in the body. Every request carries a single visitor-scoped event in the events array.

Identity Signals

Monetate matches server events to a visitor using its own identifiers. Signal forwards whichever are available; you do not need to hash any of these values.

How to identify a user

Call datafly.identify() when a customer logs in so Signal can populate customerId:

datafly.identify("87654321");

Event Mapping

Retail preset

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

Example: Product Viewed

Datafly.js call:

datafly.track("Product Viewed", {
  product_id: "product72",
  sku: "product72-large-green"
});

Monetate Engine API payload sent by Signal:

{
  "channel": "a_887f2483/p/example.com",
  "monetateId": "2.309132816.1519728587304",
  "deviceId": "a1b2c3d4-e5f6-...",
  "customerId": "87654321",
  "events": [
    {
      "eventType": "monetate:context:ProductDetailView",
      "products": [
        { "productId": "product72", "sku": "product72-large-green" }
      ]
    }
  ]
}

Example: Order Completed

Datafly.js call:

datafly.track("Order Completed", {
  order_id: "123456789",
  currency: "GBP",
  products: [
    { product_id: "product72", sku: "product72color2", quantity: 2, price: "24.00" }
  ]
});

Monetate Engine API payload sent by Signal:

{
  "channel": "a_887f2483/p/example.com",
  "monetateId": "2.309132816.1519728587304",
  "events": [
    {
      "eventType": "monetate:context:Purchase",
      "purchaseId": "123456789",
      "purchaseLines": [
        { "sku": "product72color2", "pid": "product72", "quantity": 2, "currency": "GBP", "value": "24.00" }
      ]
    }
  ]
}

Testing Your Integration

Troubleshooting