Integration

Zembula + LivePerson

LivePerson stores a summary text that an agent writes for a conversation, and Zembula can read that summary. Zembula can find a conversation by its conversation ID, or all conversations of one person by consumer ID.

It's our business to grow yours

Book a demo

What Zembula can read from LivePerson

Zembula can read messaging conversations from LivePerson and use them in an email image. Each conversation comes with its metadata, its messages and its survey scores. Zembula can also read the summary text that an agent wrote for the conversation. The engagement attributes that LivePerson captures during a conversation add purchase and lead details to the picture.

Zembula can look up one conversation by its conversation ID. To read every conversation of one person, Zembula can use the consumer ID. Two limits shape what you can plan. A search covers a span of three months at most.

The history service also runs up to one minute behind. LivePerson meant it for reporting, not for real-time decisions. 0 application or a Conversational Cloud user login. LivePerson also supports webhooks, so Zembula can receive event notifications from it.

Zembula needs the conversation ID or the consumer ID of each person in the image URL. Your team supplies the access, and your team stores that ID for each person in your email service provider.

DataDetailLooked up by
ConversationA messaging conversation with its metadata, messages and survey scores.conversation ID; also consumer ID
Conversations by consumerAll conversations of one person.consumer ID
Engagement attributesPurchase and lead attributes captured during a conversation.conversation ID
Conversation summaryThe summary text that an agent wrote for a conversation.conversation ID

How the data arrives

  • API: Zembula can read conversations, summaries and engagement attributes from the LivePerson messaging history service.
  • Webhook: LivePerson can send event notifications to Zembula through webhooks.

What you need

  • An API key or a data export from LivePerson. Zembula sets up the connection for you.
  • A Conversational Cloud user login, or an app key or OAuth 2.0 application for machine-to-machine access.
  • The conversation ID or consumer ID of each person, which your team stores in your email service provider.

Limits to plan for

LimitWhat it means
A search time range of more than three months is rejected.Each read covers a span of three months at most.
The history API has an inherent delay of up to 1 minute. It is for reporting, not real-time decisions.A conversation that just ended can take up to a minute to appear.

Ideas for email

  • Send a recap email that shows the agent’s conversation summary.
  • Follow up on a conversation with a low survey score, using the Conversation row.
  • Pick offer content from the purchase or lead attributes of a conversation.

Last checked: 19 November 2026.

Performance marketing dials, inside email. For the first time.

See how we do it by booking a demo.