LivePerson integration for Dimension Labs
This brings in each LivePerson messaging conversation as one conversation: what the consumer wrote and what your agents and bots replied, across web, app, SMS and social channels. You run it on your side: a small script pulls from LivePerson's Messaging Interactions API and posts each message to the universal API.
- Platform
- LivePerson Conversational Cloud
- Type
- Chat, messaging and AI agents
- Connects by
- Universal API
- Setup
- 5 steps
- Guide checked
- 2026-10-26, against LivePerson's documentation
Every LivePerson message, in the same shape as everything else.
Each record lands in the Dimension Labs conversation format, so Dimensions, reports and the agent work the same way as for every other source.
messageRecords[].messageData.msg.text text Skip messages whose audience is AGENTS_AND_MANAGERS: those are private messages consumers can't see. Skip messages with no text, such as files.
consumerParticipants[].participantId userId LivePerson's id for the consumer, on every message of the conversation. Fall back to the sessionId.
messageRecords[].sentBy incoming true when sentBy is Consumer. Agents and bots are Agent.
info.conversationId sessionId Prefix it, for example liveperson-e5c58e49-....
info.conversationId conversationId Same value as sessionId.
messageRecords[].timeL dimensionlabs_timestamp Already in milliseconds.
info.source, info.device, info.latestSkillName, info.status, info.mcs, info.csatRate; message dialogId platformJson The skill name lets you group by team or queue.
5 steps. Then it runs on its own.
A small job on your side reads LivePerson through its API and posts each message to the Dimension Labs universal API. The guide gives the steps, the field mapping and the code. Run the job once for history, then every 15 minutes. A live source is enriched automatically every day; history is enriched with a backfill.
Open the full LivePerson guide ›- 01Get API access in LivePerson
- 02Pull new conversations
- 03Map the fields
- 04Send it
- 05Run it
What you need
- A Conversational Cloud user with Administrator permissions, to create an OAuth 2.0 application.
- Your LivePerson account ID (your site ID), and the client_id and client_secret of that application.
- A Dimension Labs API key for a new Universal API source.
[03] What you can ask
Questions teams answer with LivePerson data.
- Where does the bot fail, and what does it cost?
- What do customers say right before they ask for a person?
- Which intents should be automated next?
LivePerson integration questions
Does Dimension Labs integrate with LivePerson?
Yes. A small job on your side reads LivePerson through its API and posts each message to the Dimension Labs universal API. The guide gives the steps, the field mapping and the code. The setup guide was checked against LivePerson's documentation on 2026-10-26.
What LivePerson data does Dimension Labs bring in?
This brings in each LivePerson messaging conversation as one conversation: what the consumer wrote and what your agents and bots replied, across web, app, SMS and social channels. You run it on your side: a small script pulls from LivePerson's Messaging Interactions API and posts each message to the universal API.
What do I need to connect LivePerson?
A Conversational Cloud user with Administrator permissions, to create an OAuth 2.0 application. Your LivePerson account ID (your site ID), and the client_id and client_secret of that application. A Dimension Labs API key for a new Universal API source.
How often does LivePerson data update?
Run the job once for history, then every 15 minutes. A live source is enriched automatically every day; history is enriched with a backfill.
Can I connect a platform that is not LivePerson?
Yes. Any platform with an API connects through the same universal API, and any tool with an export button works as a file upload. The integrations page lists the platforms with a written guide.
Stop reporting. Start understanding.
Start with one file. Ask why a number moved. Plans from $299 a month, no demo and no contract on monthly plans.