LivePerson to Domo Integration

How Datrise loads LivePerson into Domo

Datrise syncs LivePerson's conversations, agents, skills, messages, surveys, and engagement metrics into Domo as datasets in Domo's cloud store via connector. Flexible or custom fields land in flattened columns for Magic ETL, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses partitioned dataset updates rather than full replaces, so re-runs update only what changed. Domo dataset partitions keyed on load date. Domo stores its own copy of data, so Datrise sends incremental partitions to avoid re-uploading whole datasets.

Ideal for all-in-one cloud BI with built-in ETL.

Endpoints

LivePerson: Messaging-first customer conversations and bots.

Domo: Cloud BI platform combining data integration and executive dashboards.

How LivePerson entities map to Domo

LivePerson entity	Domo object	Notes
conversations	`liveperson_conversations`	id PK · custom fields → flattened columns for Magic ETL
agents	`liveperson_agents`	id PK · linked to liveperson_conversations
skills	`liveperson_skills`	id PK · linked to liveperson_conversations
messages	`liveperson_messages`	id PK · linked to liveperson_conversations

FAQ

How does Datrise handle LivePerson's custom fields in Domo?

Flexible values are stored as flattened columns for Magic ETL, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Domo types.

How does the LivePerson to Domo sync stay up to date?

It runs incrementally — Datrise uses partitioned dataset updates rather than full replaces.

Related pipelines

Early access

Connect LivePerson to Domo the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.