Delighted connector
Set up the Delighted connector in Kaivo: authentication, configuration, the 4 BigQuery tables it syncs, and answers to common questions.
Delighted connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your Delighted 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 survey and email data instead of moving it.
What is the Delighted connector
Section titled “What is the Delighted connector”Sync your Delighted survey data into BigQuery with Kaivo to analyse customer feedback and NPS trends alongside the rest of your data.
| Category | Surveys & Email, Customer Service |
|---|---|
| Authentication | API key |
| Setup | Self-service |
Getting started with the Delighted connector
Section titled “Getting started with the Delighted connector”- Sign up for Kaivo and create a workspace.
- Connect your Delighted 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 Delighted
Section titled “Authenticating Delighted”Authenticate with your Delighted API Key.
| Field | Description |
|---|---|
| Delighted API Key | |
| Your Delighted API key. |
|
Configuring the Delighted connector
Section titled “Configuring the Delighted 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 Delighted
Section titled “Tables and columns synced from Delighted”Kaivo syncs 4 tables from Delighted into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
bounces (6 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
bounced_at |
INT64 |
The timestamp when the email bounced. |
email |
STRING |
The email address that experienced the bounce. |
name |
STRING |
The name associated with the bounced email, if available. |
person_id |
STRING |
The unique identifier of the person related to the bounced email. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
people (10 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
created_at |
INT64 |
Date and time when the person was created in the system |
email |
STRING |
Email address of the person |
id |
STRING |
Unique identifier for the person record |
last_responded_at |
INT64 |
Date and time when the person last responded to a survey |
last_sent_at |
INT64 |
Date and time when the last survey was sent to the person |
name |
STRING |
Full name of the person |
next_survey_scheduled_at |
INT64 |
Date and time when the next survey is scheduled to be sent to the person |
phone_number |
STRING |
Phone number of the person |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
survey_responses (14 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
comment |
STRING |
Additional comments provided in the survey response |
created_at |
INT64 |
Timestamp of when the survey response was created |
id |
STRING |
Unique identifier for the survey response |
permalink |
STRING |
Permanent link to access the survey response |
person |
STRING |
Information about the person who responded to the survey |
person_properties__delighted_browser |
STRING |
Browser used by the person |
person_properties__delighted_device_type |
STRING |
Type of device used by the person |
person_properties__delighted_operating_system |
STRING |
Operating system of the device used by the person |
person_properties__delighted_source |
STRING |
Source from where the survey was accessed |
score |
INT64 |
Score associated with the survey response |
survey_type |
STRING |
Type of survey conducted |
updated_at |
INT64 |
Timestamp of when the survey response was last updated |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: survey_responses__additional_answers
Section titled “Subtable: survey_responses__additional_answers”| 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. |
id |
STRING |
Unique identifier for the additional answer |
question__type |
STRING |
Type of question (free response, scale, select many, select one) |
question__id |
STRING |
Unique identifier for the question |
question__text |
STRING |
Text of the question |
value__free_response |
STRING |
Free response answer |
value__scale |
INT64 |
Scale response value |
value__select_one__id |
STRING |
Unique identifier for the choice |
value__select_one__text |
STRING |
Text of the choice |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: survey_responses__additional_answers__value__select_many
Section titled “Subtable: survey_responses__additional_answers__value__select_many”| 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. |
id |
STRING |
Unique identifier for the choice |
text |
STRING |
Text of the choice |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: survey_responses__notes
Section titled “Subtable: survey_responses__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 |
JSON |
Individual note for the survey response |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: survey_responses__tags
Section titled “Subtable: survey_responses__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 |
JSON |
Individual tag for the survey response |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
unsubscribes (6 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
email |
STRING |
The email address of the subscriber who unsubscribed. |
name |
STRING |
The name of the subscriber who unsubscribed, if available. |
person_id |
STRING |
An identifier for the subscriber in the system. |
unsubscribed_at |
INT64 |
The date and time when the subscriber unsubscribed. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the Delighted sync works
Section titled “How the Delighted sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Delighted 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 Delighted?
Section titled “How long does the initial sync take for Delighted?”It depends on how much history is in your Delighted 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 Delighted’s schema changes?
Section titled “What happens when Delighted’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 Delighted, 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 Delighted 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 Delighted connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Delighted data
Section titled “Common use cases for Delighted data”NPS trends
Section titled “NPS trends”Use survey_responses to track score trends over time and by segment.
Feedback analysis
Section titled “Feedback analysis”Join responses with people to connect feedback to specific customers and cohorts.
Deliverability
Section titled “Deliverability”Bring bounces and unsubscribes into BigQuery to monitor survey reach.
Closing the loop
Section titled “Closing the loop”Combine survey_responses with your support and product data to act on feedback.
Use Delighted data in your AI and BI tools
Section titled “Use Delighted data in your AI and BI tools”Once Delighted 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 Delighted 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 Delighted connector pricing and plan details.