LivePerson

Datafly Signal reports consumer activity to LivePerson Conversational Cloud server-to-server using the Monitoring API. Signal maps your first-party events to LivePerson engagement attributes (SDEs) — purchases, cart status, product views, leads, search, and customer info — so agents and proactive-messaging campaigns see an enriched consumer profile without a client-side LivePerson tag.

Prerequisites

Before configuring LivePerson in Signal, you need a LivePerson Conversational Cloud account and a monitoring App Key.

Step 1: Find your Account ID (Site ID)

1. Sign in to Conversational Cloud.
2. Your account / site ID is the numeric ID shown in the admin URL and under account settings (e.g. 12345678).

Step 2: Create an App Key (AppInstallationId)

The Monitoring API identifies a monitoring app installation by an App Key.

1. In the Conversational Cloud admin, go to Campaigns (or Mobile App management).
2. Create an app and copy its App Key (a UUID such as a1b2c3d4-1234-5678-90ab-cdef12345678). This is the app_installation_id.

Step 3: Resolve your Monitoring Domain

The monitoring host is region-specific and must not be hardcoded. Resolve it with the LivePerson Domain API using the service name smt:

curl "https://api.liveperson.net/api/account/12345678/service/smt/baseURI.json?version=1.0"

The response baseURI (e.g. va.bc-monitoring.liveperson.net) is your monitoring_domain.

Configure in Signal

Configuration Fields

Management UI Setup

API Endpoint

POST https://{monitoring_domain}/api/account/{account_id}/app/{app_installation_id}/report?v=1.0

Each request is a single JSON object carrying the consumer identity, page entry points, and an engagementAttributes array of typed SDE objects.

Identity Signals

LivePerson matches reported activity to a consumer using the identity fields Signal sends on every request.

When a consumer is identified via datafly.identify(), Signal also reports a ctmrinfo (customer info) engagement attribute with the customer ID and status.

Event Mapping

Retail preset

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

Example: Purchase Event

Datafly.js call:

datafly.track("Order Completed", {
  order_id: "DRV1534XC",
  revenue: 11.70,
  currency: "USD"
});

LivePerson Monitoring API payload sent by Signal:

{
  "consumerId": "a1b2c3d4e5f6...",
  "identities": [
    {
      "iss": "Datafly",
      "acr": "0",
      "sub": "a1b2c3d4e5f6..."
    }
  ],
  "entryPoints": [
    "https://example.com/checkout/confirmation"
  ],
  "engagementAttributes": [
    {
      "type": "purchase",
      "total": 11.70,
      "currency": "USD",
      "orderId": "DRV1534XC"
    }
  ]
}

Example: Product Viewed Event

Datafly.js call:

datafly.track("Product Viewed", {
  product_id: "SKU-A",
  product_name: "Widget",
  category: "Hardware",
  price: 49.99
});

LivePerson Monitoring API payload sent by Signal:

{
  "consumerId": "a1b2c3d4e5f6...",
  "entryPoints": ["https://example.com/products/widget"],
  "engagementAttributes": [
    {
      "type": "prodView",
      "products": [
        {
          "product": {
            "name": "Widget",
            "category": "Hardware",
            "sku": "SKU-A",
            "price": 49.99
          }
        }
      ]
    }
  ]
}

Testing Your Integration

1. Trigger an event on your site (e.g. view a product or complete an order).
2. In Signal’s Event Debugger, confirm the LivePerson request was sent and returned 200 OK.
3. In Conversational Cloud, open the consumer’s profile / monitoring view and confirm the engagement attribute (e.g. the purchase or product view) appears.
4. If you run proactive campaigns keyed on engagement attributes, confirm the campaign targeting fires for a test consumer.

Troubleshooting

Notes