Treasure Data CDP Integration

Treasure AI Voice can push your organization's recordings, transcripts, AI-generated summaries, and device inventory directly into your own Treasure Data CDP database. Once the data lands in your CDP, you can join it with the rest of your customer data, build segments, drive journeys, and run analytics over what was actually said in your meetings and calls.

The integration is push-based and on demand: an administrator runs an export from the AI Voice Console, and Treasure AI Voice streams a snapshot of the selected data into the tables you specify. There is no standing pipeline to manage and no data sits in an intermediate location — your API key is used only to authenticate that single run and is never stored or persisted.

Each export writes to four logical tables in your CDP database. The recordings, transcript_segments, and summaries tables reflect the recordings in scope for the run; the devices table always reflects your full device inventory regardless of the selected date range.

Recordings are included regardless of processing status. The status column reflects each recording's state, and transcription_text, summary_text, and the related fields are empty for recordings that have not finished transcribing or summarizing yet.

Every row carries a stable uuid derived from the source record. The same record always maps to the same uuid, so you can identify and remove duplicate rows after re-running an export over an overlapping date range.

Every row also carries a time column (Unix epoch seconds) that Treasure Data CDP uses for native time partitioning, so analysts can efficiently filter by time. The time value is anchored to the most meaningful timestamp for each table — recorded_at for recordings and summaries, the utterance start for segments, and the last heartbeat (falling back to provisioning time) for devices.

The schema is owned by Treasure AI Voice. Columns are appended to your CDP tables on first write — you do not need to pre-declare them.

Before running an export, make sure you have:

• An Enterprise Administrator account on Treasure AI Voice.
• The integration enabled for your organization (see below).
• A Treasure Data CDP API key that holds the IMPORT role and can write to the target database.
• A destination database in your Treasure Data CDP. The export writes to the tables you specify within that database, creating them on first write.

The integration is off by default. To turn it on:

1. Sign in to the AI Voice Console as an Enterprise Administrator.
2. Open the Export page.
3. Select the Treasure Data CDP destination.
4. Click Enable export.

If you do not see the option to enable it, contact your Treasure AI representative.

1. On the Export page, with Treasure Data CDP selected, enter:
   • API Key — your Treasure Data CDP API key (IMPORT role).
   • Database — the destination database name (for example, ai_voice_export).
2. (Optional) Expand Advanced to customize:
   • Recordings table and Transcript segments table names (defaults: recordings, transcript_segments).
   • From / To date range to limit which recordings are exported. The range applies to when each recording was captured, and the To date is inclusive through the end of that day.
3. Click Export.

The AI Voice Console reports progress while it reads your recordings, joins transcript data, and sends the events to Treasure Data CDP. A typical run completes in under a minute.

Each run finishes in one of these states:

Every export run — including its outcome and the row counts — is recorded in the Audit Logs under the TD_CDP_EXPORT event type. The API key is never written to the audit log.

Because each table shares recording_id (recordings.id), you can reconstruct any view of your meeting data in your CDP. For example:

• Join summaries to recordings on recording_id to get summaries alongside the full recording metadata.
• Join transcript_segments to recordings on recording_id, ordered by segment_index, to reconstruct or analyze the conversation utterance by utterance.
• Pivot transcript_segments on speaker_label (or speaker_id) to analyze talk time per participant.
• Join recordings to devices on device_serial_number = serial_number to attribute conversations to devices and assigned users.

WITH ranked AS (
  SELECT *, ROW_NUMBER() OVER (PARTITION BY uuid ORDER BY time DESC) AS rn
  FROM your_table
)
SELECT * FROM ranked WHERE rn = 1