Skip to content
Book a demoStart free
Connectors

Elastic Email connector

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

Elastic Email connector pricing, tier and credits on kaivo.io

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

Sync your Elastic Email data into BigQuery with Kaivo to measure campaigns, deliverability, and audience growth in one place.

CategorySurveys & Email
AuthenticationAPI key
SetupSelf-service

Getting started with the Elastic Email connector

Section titled “Getting started with the Elastic Email connector”
  1. Sign up for Kaivo and create a workspace.
  2. Connect your Elastic Email 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
API key for accessing Elastic Email. Find it in your account under Settings > API Keys.

|

When you set up the connector, you provide:

Field Description
Scope Type
The scope of templates to fetch. Personal returns templates specific to your account; Global returns templates available to all users.

| | Start Date |

Any data before this date will not be fetched.

|

Tables and columns synced from Elastic Email

Section titled “Tables and columns synced from Elastic Email”

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

campaigns (10 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
name STRING
options__delivery_optimization STRING
options__schedule_for STRING
options__split_options__optimize_for STRING
options__split_options__optimize_period_minutes FLOAT64
options__trigger_count FLOAT64
options__trigger_frequency FLOAT64
status STRING
_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.
from STRING
poolname STRING
reply_to STRING
subject STRING
template_name STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.

Subtable: campaigns__recipients__list_names

Section titled “Subtable: campaigns__recipients__list_names”
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.
contacts (20 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
activity__friendly_error_message STRING
activity__last_ip STRING
activity__last_sent STRING
activity__total_clicked FLOAT64
activity__total_failed FLOAT64
activity__total_opened FLOAT64
activity__total_sent FLOAT64
consent__consent_date STRING
consent__consent_ip STRING
consent__consent_tracking STRING
date_added STRING
date_updated STRING
email STRING
first_name STRING
last_name STRING
source STRING
status STRING
status_change_date STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
events (14 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
channel_name STRING
event_date STRING
event_type STRING
from_email STRING
ip_address STRING
message STRING
message_category STRING
msg_id STRING
pool_name STRING
subject STRING
to STRING
transaction_id STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
files (8 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
content_type STRING
date_added STRING
expiration_date STRING
file_id FLOAT64
file_name STRING
size FLOAT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
inboundroute (9 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
action_parameter STRING
action_type STRING
filter STRING
filter_type STRING
name STRING
public_id STRING
sort_order FLOAT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
lists (6 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
allow_unsubscribe BOOL
date_added STRING
list_name STRING
public_list_id STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
segments (4 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
name STRING
rule STRING
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
statistics (15 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
bounced FLOAT64
clicked FLOAT64
complaints FLOAT64
delivered FLOAT64
email_total FLOAT64
in_progress FLOAT64
inbound FLOAT64
manual_cancel FLOAT64
not_delivered FLOAT64
opened FLOAT64
recipients FLOAT64
sms_total FLOAT64
unsubscribed FLOAT64
_kaivo_extracted_at TIMESTAMP Timestamp that shows when the row was extracted. Auto-generated by Kaivo.
templates (7 columns)
Column Type Description
_kaivo_id STRING Primary key that uniquely identifies the row. Auto-generated by Kaivo.
date_added STRING
name STRING
subject STRING
template_scope STRING
template_type STRING
_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.
value JSON
_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 Elastic Email 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 Elastic Email?

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

It depends on how much history is in your Elastic Email 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 Elastic Email’s schema changes?

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

Use campaigns and statistics to track sends and engagement over time.

Use events to monitor delivered, bounced, and failed messages.

Track lists and segments to see how your audience grows and engages.

Use Elastic Email data in your AI and BI tools

Section titled “Use Elastic Email data in your AI and BI tools”

Once Elastic Email 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 Elastic Email 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 Elastic Email connector pricing and plan details.