EmailOctopus connector
Set up the EmailOctopus connector in Kaivo: authentication, configuration, the 2 BigQuery tables it syncs, and answers to common questions.
EmailOctopus connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your EmailOctopus 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 EmailOctopus connector
Section titled “What is the EmailOctopus connector”Sync your EmailOctopus data into BigQuery with Kaivo to measure campaigns and audience growth in one place.
| Category | Surveys & Email |
|---|---|
| Authentication | API key |
| Setup | Self-service |
Getting started with the EmailOctopus connector
Section titled “Getting started with the EmailOctopus connector”- Sign up for Kaivo and create a workspace.
- Connect your EmailOctopus 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 EmailOctopus
Section titled “Authenticating EmailOctopus”Authenticate with your EmailOctopus API key.
| Field | Description |
|---|---|
| EmailOctopus API key | |
| EmailOctopus API Key. See the docs for information on how to generate this key. |
|
Tables and columns synced from EmailOctopus
Section titled “Tables and columns synced from EmailOctopus”Kaivo syncs 2 tables from EmailOctopus into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
campaigns (10 columns), Details of all campaigns.
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
created_at |
STRING |
When the campaign was created, in ISO 8601 format. |
from__email_address |
STRING |
The email address the campaign was sent from. |
from__name |
STRING |
The name the campaign was sent from. |
id |
STRING |
The identifier of the campaign. |
name |
STRING |
The name of the campaign. |
sent_at |
STRING |
When the campaign was sent, in ISO 8601 format. |
status |
STRING |
The status of the campaign (DRAFT/SENDING/SENT/ERROR). |
subject |
STRING |
The subject of the campaign. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: campaigns__to
Section titled “Subtable: campaigns__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. |
lists (9 columns), Details of all lists.
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
counts__pending |
INT64 |
The number of pending contacts in the list. |
counts__subscribed |
INT64 |
The number of subscribed contacts in the list. |
counts__unsubscribed |
INT64 |
The number of unsubscribed contacts in the list. |
created_at |
STRING |
When the list was created, in ISO 8601 format. |
double_opt_in |
BOOL |
If double opt-in has been enabled on the list. |
id |
STRING |
The identifier of the list. |
name |
STRING |
The name of the list. |
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: lists__fields
Section titled “Subtable: lists__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. |
value |
JSON |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
How the EmailOctopus sync works
Section titled “How the EmailOctopus sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where EmailOctopus 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 EmailOctopus?
Section titled “How long does the initial sync take for EmailOctopus?”It depends on how much history is in your EmailOctopus 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 EmailOctopus’s schema changes?
Section titled “What happens when EmailOctopus’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 EmailOctopus, 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 EmailOctopus 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 EmailOctopus connector in Kaivo and all of its synced data is deleted with it.
Common use cases for EmailOctopus data
Section titled “Common use cases for EmailOctopus data”Campaign performance
Section titled “Campaign performance”Use campaigns to track sends and engagement over time.
List growth
Section titled “List growth”Use lists to monitor how your audience grows.
Marketing context
Section titled “Marketing context”Join EmailOctopus data with your other channels to see email contribution to results.
Use EmailOctopus data in your AI and BI tools
Section titled “Use EmailOctopus data in your AI and BI tools”Once EmailOctopus 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 EmailOctopus 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 EmailOctopus connector pricing and plan details.