Dixa connector
Set up the Dixa connector in Kaivo: authentication, configuration, the 2 BigQuery tables it syncs, and answers to common questions.
Dixa connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your Dixa data into a Google BigQuery warehouse and keeps it up to date automatically. There is no pipeline to build and no infrastructure to run, so you can spend your time analysing your customer support data instead of moving it.
What is the Dixa connector
Section titled “What is the Dixa connector”Sync your Dixa conversations and messages into BigQuery with Kaivo to analyse support volume and response times alongside the rest of your data.
| Category | Customer Service |
|---|---|
| Authentication | API key |
| Setup | Self-service |
Getting started with the Dixa connector
Section titled “Getting started with the Dixa connector”- Sign up for Kaivo and create a workspace.
- Connect your Dixa account.
- Choose which tables to sync.
- Wait for the initial sync to finish.
- Query your data in BigQuery or your favourite AI or BI tool.
Authenticating Dixa
Section titled “Authenticating Dixa”Authenticate with your API Token.
| Field | Description |
|---|---|
| API Token | |
| You can create the API token by following Dixa’s instructions. The name of the token can be for example “kaivo”. |
|
Configuring the Dixa connector
Section titled “Configuring the Dixa connector”When you set up the connector, you provide:
| Field | Description |
|---|---|
| Start date | |
| Any data before this date will not be fetched. |
|
Tables and columns synced from Dixa
Section titled “Tables and columns synced from Dixa”Kaivo syncs 2 tables from Dixa into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
conversation_export (43 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
anonymized_at |
INT64 |
|
assigned_at |
INT64 |
|
assignee_email |
STRING |
|
assignee_id |
STRING |
|
assignee_name |
STRING |
|
assignee_phone_number |
STRING |
|
closed_at |
INT64 |
|
created_at |
INT64 |
|
direction |
STRING |
|
dixa_email_integration_id |
STRING |
|
dixa_email_integration_sender_name |
STRING |
|
facebook_page_id |
STRING |
|
facebook_page_name |
STRING |
|
forwarding_email |
STRING |
|
from_provisioned_phone_number_id |
STRING |
|
from_provisioned_phone_number_name |
STRING |
|
handling_duration |
INT64 |
|
id |
INT64 |
|
initial_channel |
STRING |
|
last_message_created_at |
INT64 |
|
originating_country |
STRING |
|
queue_id |
STRING |
|
queue_name |
STRING |
|
queued_at |
INT64 |
|
rating_message |
STRING |
|
rating_score |
INT64 |
|
requester_email |
STRING |
|
requester_id |
STRING |
|
requester_name |
STRING |
|
requester_phone_number |
STRING |
|
status |
STRING |
|
subject |
STRING |
|
to_provisioned_phone_number_id |
STRING |
|
to_provisioned_phone_number_name |
STRING |
|
total_duration |
INT64 |
|
transfer_time |
INT64 |
|
transferee_name |
STRING |
|
transferee_number |
STRING |
|
updated_at |
INT64 |
|
widget_id |
STRING |
|
widget_name |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: conversation_export__conversation_wrapup_notes
Section titled “Subtable: conversation_export__conversation_wrapup_notes”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: conversation_export__custom_fields
Section titled “Subtable: conversation_export__custom_fields”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
archived |
BOOL |
|
attribute_id |
STRING |
|
data_type |
STRING |
|
identifier |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: conversation_export__custom_fields__value
Section titled “Subtable: conversation_export__custom_fields__value”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: conversation_export__ratings
Section titled “Subtable: conversation_export__ratings”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
rating_cancelled_timestamp |
INT64 |
|
rating_created_timestamp |
INT64 |
|
rating_language |
STRING |
|
rating_message |
STRING |
|
rating_modified_timestamp |
INT64 |
|
rating_offered_timestamp |
INT64 |
|
rating_rated_timestamp |
INT64 |
|
rating_scheduled_for_timestamp |
INT64 |
|
rating_scheduled_timestamp |
INT64 |
|
rating_score |
INT64 |
|
rating_status |
STRING |
|
rating_type |
STRING |
|
rating_unscheduled_timestamp |
INT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: conversation_export__requester_additional_emails
Section titled “Subtable: conversation_export__requester_additional_emails”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: conversation_export__requester_additional_phone_numbers
Section titled “Subtable: conversation_export__requester_additional_phone_numbers”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: conversation_export__tags
Section titled “Subtable: conversation_export__tags”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: conversation_export__tags_info
Section titled “Subtable: conversation_export__tags_info”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
message_export (20 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
author_email |
STRING |
|
author_name |
STRING |
|
chat_input_answer |
STRING |
|
chat_input_question |
STRING |
|
chat_menu_text |
STRING |
|
created_at |
INT64 |
|
csid |
INT64 |
|
direction |
STRING |
|
duration |
INT64 |
|
from |
STRING |
|
from_phone_number |
STRING |
|
id |
STRING |
|
initial_channel |
STRING |
|
is_automated_message |
BOOL |
|
recording_url |
STRING |
|
text |
STRING |
|
to_phone_number |
STRING |
|
voicemail_url |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: message_export__attached_files
Section titled “Subtable: message_export__attached_files”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: message_export__bcc
Section titled “Subtable: message_export__bcc”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: message_export__cc
Section titled “Subtable: message_export__cc”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: message_export__to
Section titled “Subtable: message_export__to”| Column | Type | Description |
|---|---|---|
_kaivo_parent_id |
STRING |
Foreign key referencing _kaivo_id in the parent table. Auto-generated by Kaivo. |
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
value |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the Dixa sync works
Section titled “How the Dixa sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Dixa supports it, each sync pulls only new and changed records so it stays fast; otherwise it refreshes the whole table. Every record keeps its original ID, so you won’t get duplicate rows.
Frequently asked questions
Section titled “Frequently asked questions”How long does the initial sync take for Dixa?
Section titled “How long does the initial sync take for Dixa?”It depends on how much history is in your Dixa account. Most initial syncs finish within minutes, while large accounts can take a few hours. After that, syncs only fetch new and changed records, so they’re much faster.
Can I sync only some tables or columns?
Section titled “Can I sync only some tables or columns?”Yes. You pick which tables to sync when you set up the connection and can change the selection later. Tables you don’t select are never copied to your warehouse.
What happens when Dixa’s schema changes?
Section titled “What happens when Dixa’s schema changes?”New fields are never added automatically. You choose which fields to sync, so data you haven’t selected (sensitive personal data, for example) never lands in your warehouse. When a new field appears, it becomes available for you to add. What happens to removed or renamed fields depends on a table’s sync mode: full-refresh tables always match what’s currently in Dixa, so dropped fields disappear, while incremental tables keep their existing columns and history, so an old field stays and newly added fields fill in over time.
How do I handle GDPR or data deletion requests?
Section titled “How do I handle GDPR or data deletion requests?”Your data lives in your own Kaivo-managed BigQuery warehouse, so the most direct option is to delete or anonymise specific records right in BigQuery. If you delete data in Dixa instead, full-refresh tables drop it on the next sync, while incremental tables keep it, so you would remove the row in BigQuery or ask us to run a full refresh. To remove everything, delete the Dixa connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Dixa data
Section titled “Common use cases for Dixa data”Support volume
Section titled “Support volume”Use conversation_export to track ticket volume by channel and over time.
Response times
Section titled “Response times”Analyse message_export timestamps to measure first response and resolution times.
Agent workload
Section titled “Agent workload”Break conversations down by agent and queue to balance workload.
Support and product together
Section titled “Support and product together”Join Dixa conversations with product or order data in BigQuery to connect support to the customer journey.
Use Dixa data in your AI and BI tools
Section titled “Use Dixa data in your AI and BI tools”Once Dixa data lands in your Kaivo-managed BigQuery warehouse, you can explore it with AI tools or any BI tool that connects to BigQuery. Here’s how the most common destinations work with Dixa data.
Claude
Section titled “Claude”Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →
Power BI
Section titled “Power BI”Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →
Data Studio
Section titled “Data Studio”Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →
Tableau
Section titled “Tableau”The premium analytics standard, with native BigQuery integration. Setup guide →
Google Sheets
Section titled “Google Sheets”Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →
Connect via Power Query’s BigQuery connector. Setup guide →
Metabase
Section titled “Metabase”Open-source BI tool with strong BigQuery support. Setup guide →
See our pricing page for Dixa connector pricing and plan details.