Drift connector
Set up the Drift connector in Kaivo: authentication, configuration, the 5 BigQuery tables it syncs, and answers to common questions.
Drift connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your Drift 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 CRM data instead of moving it.
What is the Drift connector
Section titled “What is the Drift connector”Sync your Drift conversation data into BigQuery with Kaivo to analyse chat volume, contacts, and engagement.
| Category | CRM, Customer Service |
|---|---|
| Authentication | API key |
| Setup | Self-service |
Getting started with the Drift connector
Section titled “Getting started with the Drift connector”- Sign up for Kaivo and create a workspace.
- Connect your Drift 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 Drift
Section titled “Authenticating Drift”Authenticate with your Access Token.
| Field | Description |
|---|---|
| Access Token | |
| Your Drift Access Token. You can generate one from the Drift developer settings. |
|
Configuring the Drift connector
Section titled “Configuring the Drift connector”When you set up the connector, you provide:
| Field | Description |
|---|---|
| Email address used to filter the contacts stream. Leave blank to retrieve all contacts. |
|
Tables and columns synced from Drift
Section titled “Tables and columns synced from Drift”Kaivo syncs 5 tables from Drift into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
accounts (10 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
account_id |
STRING |
The unique identifier for the account |
create_date_time |
INT64 |
The date and time when the account was created |
deleted |
BOOL |
Indicates if the account has been deleted |
domain |
STRING |
The domain associated with the account |
name |
STRING |
The name of the account |
owner_id |
INT64 |
The unique identifier of the account owner |
targeted |
BOOL |
Indicates if the account is a targeted account |
update_date_time |
INT64 |
The date and time when the account was last updated |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: accounts__custom_properties
Section titled “Subtable: accounts__custom_properties”| 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. |
type |
STRING |
The type of the custom property |
label |
STRING |
The label for a custom property |
name |
STRING |
The name of the custom property |
value |
JSON |
The value of the custom property |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
contacts (10 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
attributes__email |
STRING |
Email address of the contact |
attributes__events |
JSON |
Events related to the contact |
attributes__name |
STRING |
Name of the contact |
attributes__phone |
STRING |
Phone number of the contact |
attributes__social_profiles |
JSON |
Social media profiles of the contact |
created_at |
INT64 |
Timestamp of when the contact was created |
id |
INT64 |
Unique identifier for the contact |
name |
STRING |
Name of the contact |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: contacts__attributes__tags
Section titled “Subtable: contacts__attributes__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 |
Tag name |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
conversations (9 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
contact_id |
INT64 |
The unique identifier of the contact associated with the conversation. |
created_at |
INT64 |
The timestamp when the conversation was created. |
id |
INT64 |
The unique identifier of the conversation. |
inbox_id |
INT64 |
The unique identifier of the inbox where the conversation belongs. |
related_playbook_id |
STRING |
The unique identifier of the playbook related to the conversation, if any. |
status |
STRING |
The status of the conversation (e.g., open, closed, in progress). |
updated_at |
INT64 |
The timestamp when the conversation was last updated. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: conversations__conversation_tags
Section titled “Subtable: conversations__conversation_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. |
color |
STRING |
HEX value |
name |
STRING |
The name of the tag associated with the conversation. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: conversations__participants
Section titled “Subtable: conversations__participants”| 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 |
INT64 |
Details of the participants in the conversation. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
messages (13 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
type |
STRING |
Type of message (e.g., text, image, file). |
author__type |
STRING |
Type of the author (e.g., user, bot). |
author__bot |
BOOL |
Boolean flag indicating if the author is a bot. |
author__id |
INT64 |
Unique identifier of the author. |
body |
STRING |
The main content/body of the message. |
context__ip |
STRING |
IP address associated with the message. |
context__user_agent |
STRING |
User agent information of the client device. |
conversation_id |
INT64 |
Unique identifier of the conversation associated with the message. |
created_at |
INT64 |
Timestamp indicating when the message was created. |
id |
INT64 |
Unique identifier of the message. |
org_id |
INT64 |
Unique identifier of the organization associated with the message. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: messages__buttons
Section titled “Subtable: messages__buttons”| 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. |
type |
STRING |
Type of button (e.g., call to action, link). |
label |
STRING |
Text label displayed on the button. |
reaction__type |
STRING |
Type of reaction triggered (e.g., message, action). |
reaction__message |
STRING |
Message triggered by clicking the button. |
style |
STRING |
Visual style of the button (e.g., primary, secondary). |
value |
STRING |
Value associated with the button (e.g., URL, action name). |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
users (17 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
alias |
STRING |
User’s alias used for identification. |
availability |
STRING |
User’s availability status. |
avatar_url |
STRING |
URL for the user’s avatar image. |
bot |
BOOL |
Flag indicating if the user is a bot. |
created_at |
INT64 |
Timestamp when the user was created. |
email |
STRING |
User’s email address. |
id |
INT64 |
Unique identifier for the user. |
locale |
STRING |
User’s preferred language and region settings. |
name |
STRING |
User’s full name. |
org_id |
INT64 |
Identifier for the organization the user belongs to. |
phone |
STRING |
User’s phone number. |
role |
STRING |
User’s role or permission level. |
time_zone |
STRING |
User’s preferred time zone. |
updated_at |
INT64 |
Timestamp when the user was last updated. |
verified |
BOOL |
Flag indicating if the user’s account is verified. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the Drift sync works
Section titled “How the Drift sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Drift 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 Drift?
Section titled “How long does the initial sync take for Drift?”It depends on how much history is in your Drift 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 Drift’s schema changes?
Section titled “What happens when Drift’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 Drift, 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 Drift 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 Drift connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Drift data
Section titled “Common use cases for Drift data”Conversation volume
Section titled “Conversation volume”Use conversations and messages to track chat volume and response activity over time.
Contact view
Section titled “Contact view”Join contacts with conversations to see who engages and how often.
Account context
Section titled “Account context”Use accounts to connect chat activity to your customers and pipeline.
Use Drift data in your AI and BI tools
Section titled “Use Drift data in your AI and BI tools”Once Drift 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 Drift 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 Drift connector pricing and plan details.