Skip to content
Book a demoStart free
Connectors

Churnkey connector

Set up the Churnkey connector in Kaivo: authentication, configuration, the 2 BigQuery tables it syncs, and answers to common questions.

Churnkey connector pricing, tier and credits on kaivo.io

Kaivo is a fully managed data platform that syncs your Churnkey 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.

Sync your Churnkey retention data into BigQuery with Kaivo to analyse cancellation sessions and save outcomes.

CategoryCustomer Service
AuthenticationAPI key
SetupSelf-service

Getting started with the Churnkey connector

Section titled “Getting started with the Churnkey connector”
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Churnkey account.
  3. Choose which tables to sync.
  4. Wait for the initial sync to finish.
  5. Query your data in BigQuery or your favourite AI or BI tool.

Authenticate with your API Key.

Field Description
API Key
Your Churnkey Data API key (not the Cancel Flow key), found under Settings → Account → Data API Keys.

|

When you set up the connector, you provide:

Field Description
App ID
Your Churnkey App ID, shown alongside the Data API key under Settings → Account → Data API Keys.

|

Kaivo syncs 2 tables from Churnkey into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.

session-aggregation (3 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
count FLOAT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
sessions (104 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
v FLOAT64
_id STRING
org STRING
lang STRING
mode STRING
region__click_to_cancel BOOL
region__matched_region STRING
region__matched_region_code STRING
region__strict_ftc_compliance BOOL
aborted BOOL
canceled BOOL
customer__id STRING
customer__email STRING
customer__paused BOOL
customer__plan_id STRING
customer__created STRING
customer__currency STRING
customer__discount__id STRING
customer__discount__start STRING
customer__discount__coupon__id STRING
customer__discount__coupon__coupon_type STRING
customer__discount__coupon__coupon_amount FLOAT64
customer__discount__coupon__coupon_duration FLOAT64
customer__pause_end STRING
customer__plan_price FLOAT64
customer__item_quantity FLOAT64
customer__subscription_id STRING
customer__billing_interval STRING
customer__subscription_start STRING
customer__billing_interval_count FLOAT64
customer__subscription_period_end STRING
customer__subscription_period_start STRING
customer__latest_discount_expiration STRING
feedback STRING
provider STRING
save_type STRING
survey_id STRING
created_at STRING
recording STRING
updated_at STRING
blueprint_id STRING
managed_flow BOOL
accepted_offer__guid STRING
accepted_offer__coupon_id STRING
accepted_offer__offer_type STRING
accepted_offer__coupon_type STRING
accepted_offer__coupon_amount FLOAT64
accepted_offer__pause_duration FLOAT64
accepted_offer__pause_interval STRING
accepted_offer__coupon_duration FLOAT64
survey_choice_id STRING
sentiment_scores__reason_a__ease FLOAT64
sentiment_scores__reason_a__need FLOAT64
sentiment_scores__reason_a__budget FLOAT64
sentiment_scores__reason_a__refund FLOAT64
sentiment_scores__reason_a__feature FLOAT64
sentiment_scores__reason_a__technical FLOAT64
sentiment_scores__reason_b__ease FLOAT64
sentiment_scores__reason_b__need FLOAT64
sentiment_scores__reason_b__budget FLOAT64
sentiment_scores__reason_b__refund FLOAT64
sentiment_scores__reason_b__feature FLOAT64
sentiment_scores__reason_b__technical FLOAT64
sentiment_scores__emotion_a__angry FLOAT64
sentiment_scores__emotion_a__confused FLOAT64
sentiment_scores__emotion_a__grateful FLOAT64
sentiment_scores__emotion_a__practical FLOAT64
sentiment_scores__emotion_b__angry FLOAT64
sentiment_scores__emotion_b__confused FLOAT64
sentiment_scores__emotion_b__grateful FLOAT64
sentiment_scores__emotion_b__practical FLOAT64
sentiment_scores__product_a__negative FLOAT64
sentiment_scores__product_a__positive FLOAT64
sentiment_scores__product_b__negative FLOAT64
sentiment_scores__product_b__recommend FLOAT64
sentiment_scores__product_c__poor FLOAT64
sentiment_scores__product_c__great FLOAT64
sentiment_scores__product_d__hate FLOAT64
sentiment_scores__product_d__like FLOAT64
sentiment_scores__product_d__love FLOAT64
sentiment_scores__product_d__dislike FLOAT64
sentiment_scores__reactivate_a__negative FLOAT64
sentiment_scores__reactivate_a__reactivate FLOAT64
sentiment_scores__reactivate_b__negative FLOAT64
sentiment_scores__reactivate_b__reactivate FLOAT64
sentiment_scores__subjective_a__emotional FLOAT64
sentiment_scores__subjective_a__reasonable FLOAT64
feedback_analysis__question STRING
feedback_analysis__response STRING
feedback_analysis__session_id STRING
feedback_analysis__timestamp STRING
feedback_analysis__feedback_analyzer_version STRING
followup_question STRING
followup_response STRING
recording_end_time STRING
survey_choice_value STRING
used_click_to_cancel BOOL
recording_start_time STRING
click_to_cancel_enabled BOOL
pause_cooldown_applied BOOL
discount_cooldown_applied BOOL
strict_ftc_compliance_enabled BOOL
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
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.
end STRING
guid STRING
start STRING
duration FLOAT64
step_type STRING
num_choices FLOAT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
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.
guid STRING
accepted BOOL
offer_type STRING
accepted_at STRING
declined_at STRING
pause_config__pause_interval STRING
pause_config__max_pause_length FLOAT64
presented_at STRING
survey_offer BOOL
discount_config__coupon_id STRING
discount_config__custom_amount FLOAT64
discount_config__custom_duration STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: sessions__feedback_analysis__feedback_types

Section titled “Subtable: sessions__feedback_analysis__feedback_types”
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
category STRING
explanation STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Churnkey 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.

How long does the initial sync take for Churnkey?

Section titled “How long does the initial sync take for Churnkey?”

It depends on how much history is in your Churnkey 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.

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 Churnkey’s schema changes?

Section titled “What happens when Churnkey’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 Churnkey, 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 Churnkey 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 Churnkey connector in Kaivo and all of its synced data is deleted with it.

Use sessions to track how many cancellations are saved over time.

Use session-aggregation to find the most common reasons customers leave.

Join Churnkey data with your billing data to connect saves to revenue retained.

Once Churnkey 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 Churnkey data.

Use Kaivo’s MCP server to give Claude secure, workspace-scoped access to your data. Setup guide →

Microsoft’s BI tool with a native BigQuery connector. Supports direct query and scheduled refresh. Setup guide →

Free Google BI tool with native BigQuery support. One-click connection to your Kaivo warehouse; great for SMB teams on Google Workspace. Setup guide →

The premium analytics standard, with native BigQuery integration. Setup guide →

Use Connected Sheets to query BigQuery directly from a spreadsheet, with no SQL. Setup guide →

Connect via Power Query’s BigQuery connector. Setup guide →

Open-source BI tool with strong BigQuery support. Setup guide →

See our pricing page for Churnkey connector pricing and plan details.

  • HubSpot: Sync HubSpot to BigQuery.
  • Dixa: Sync Dixa to BigQuery.
  • Freshservice: Sync Freshservice to BigQuery.
  • Genesys: Sync Genesys to BigQuery.
  • Gorgias: Sync Gorgias to BigQuery.
  • giosg: Sync giosg to BigQuery.