LivePerson

Reports consumer engagement attributes (SDEs) to LivePerson Conversational Cloud through the Monitoring API report method, so agents and proactive campaigns see first-party context.

Why route LivePerson through Datafly Signal

• Profiles are updated from the server, not the browser. Events reach LivePerson 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. LivePerson is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.

Prerequisites

Configuration

Signal setup

1. Navigate to Integrations in the sidebar and open the Integration Library tab.
2. Find LivePerson, click Install and fill in the fields above.
3. Pick the preset for your use, then review the mappings in the blueprint editor.

API endpoint

PUT https://{monitoring_domain}/api/account/{account_id}/app/{app_installation_id}/report?v=1.0&obh=true

Example request:

{"identities": [{"iss": "Datafly", "acr": "0", "sub": "df_anon_..."}],
 "entryPoints": ["https://www.example.co.uk/checkout"],
 "engagementAttributes": [{"type": "purchase", "total": 279.98, "currency": "GBP", "orderId": "ORD-1001",
   "cart": {"numItems": 3, "products": [{"product": {"name": "Parka Jacket", "category": "Jackets", "sku": "SKU-1", "price": 129.99}, "quantity": 2}]}}]}

The presets turn on the strict output contract: only the fields the blueprint maps are sent.

Event mapping

Retail preset (ecommerce)

Reports the retail funnel to LivePerson as engagement attributes for agents and proactive campaigns: product views (prodView), cart views (cart), purchases (purchase, with the cart), leads (lead), search (searchInfo) and customer info (ctmrinfo) on identify; add to cart is mapped but disabled (Signal has no cart-total event). Unauthenticated consumer identity (identities: sub = the Signal anonymous ID, a random ID as LivePerson recommends, acr 0) and the page URL as the entry point. No email, phone or name is sent.

Default preset (default)

Leads (lead), search (searchInfo), purchases (purchase) and customer info (ctmrinfo) as LivePerson engagement attributes. Unauthenticated consumer identity (identities: sub = the Signal anonymous ID, a random ID as LivePerson recommends, acr 0) and the page URL as the entry point. No email, phone or name is sent.

Identity and personal data

The consumer is identified by an unauthenticated identity whose sub is the Signal anonymous ID (a random ID, as LivePerson recommends; never an email or name) and acr 0. obh=true tells LivePerson the request is made on the visitor’s behalf, so it does not geo-locate from Datafly’s server. ctmrinfo carries the Signal user ID as customerId on identify; an identify with no user ID and no customer_status or customer_type trait is not sent. No email, phone or name is sent.

Consent

Map LivePerson to the consent category you use for personalisation or support tooling.

Known limitations

• The report method requires an engagement attribute, so page views are not sent.
• LivePerson’s vid and sid are issued by LivePerson to its own web tag; Signal does not hold them, so server events are not joined to a live web session.
• Engagement attributes are unauthenticated by design; do not use them for business transactions that need strong authentication.

Troubleshooting