Oveit connector
Set up the Oveit connector in Kaivo: authentication, configuration, the 3 BigQuery tables it syncs, and answers to common questions.
Oveit connector pricing, tier and credits on kaivo.ioKaivo is a fully managed data platform that syncs your Oveit 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 marketing and sales data instead of moving it.
What is the Oveit connector
Section titled “What is the Oveit connector”Sync your Oveit event data into BigQuery with Kaivo to analyse ticket sales, attendee check-ins, and overall event performance over time.
| Category | Marketing & Sales |
|---|---|
| Authentication | Username and password |
| Setup | Self-service |
Getting started with the Oveit connector
Section titled “Getting started with the Oveit connector”- Sign up for Kaivo and create a workspace.
- Connect your Oveit 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 Oveit
Section titled “Authenticating Oveit”Connect with your Oveit login. You provide:
| Field | Description |
|---|---|
| Password | |
| Your Oveit account password. |
|
Configuring the Oveit connector
Section titled “Configuring the Oveit connector”When you set up the connector, you provide:
| Field | Description |
|---|---|
| Your Oveit account email address. |
|
Tables and columns synced from Oveit
Section titled “Tables and columns synced from Oveit”Kaivo syncs 3 tables from Oveit into a dedicated dataset in your BigQuery warehouse. Click any table to see its columns and types.
attendees (10 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
created_at |
STRING |
|
id |
STRING |
|
order_id |
STRING |
|
order_uuid |
STRING |
|
ticket_code |
STRING |
|
ticket_id |
STRING |
|
ticket_type__id |
FLOAT64 |
|
ticket_type__name |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: attendees__checkins
Section titled “Subtable: attendees__checkins”| 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. |
Subtable: attendees__links
Section titled “Subtable: attendees__links”| 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. |
Subtable: attendees__values
Section titled “Subtable: attendees__values”| 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. |
events (10 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
hash |
STRING |
|
id |
FLOAT64 |
|
location |
STRING |
|
name |
STRING |
|
starts_at |
STRING |
|
tickets |
FLOAT64 |
|
tickets_checked_in |
FLOAT64 |
|
tickets_sold |
FLOAT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: events__ticket_types
Section titled “Subtable: events__ticket_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. |
id |
FLOAT64 |
|
name |
STRING |
|
price |
STRING |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: events__ticket_types__addons
Section titled “Subtable: events__ticket_types__addons”| 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. |
tickets (5 columns)
| Column | Type | Description |
|---|---|---|
_kaivo_id |
STRING |
Primary key that uniquely identifies the row. Auto-generated by Kaivo. |
checked_in |
BOOL |
|
code |
STRING |
|
ticket_type_id |
FLOAT64 |
|
_kaivo_extracted_at |
TIMESTAMP |
Timestamp that shows when the row was extracted. Auto-generated by Kaivo. |
Subtable: tickets__checkins
Section titled “Subtable: tickets__checkins”| 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 Oveit sync works
Section titled “How the Oveit sync works”After the first load, Kaivo keeps your BigQuery warehouse up to date for you. Where Oveit 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 Oveit?
Section titled “How long does the initial sync take for Oveit?”It depends on how much history is in your Oveit 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 Oveit’s schema changes?
Section titled “What happens when Oveit’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 Oveit, 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 Oveit 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 Oveit connector in Kaivo and all of its synced data is deleted with it.
Common use cases for Oveit data
Section titled “Common use cases for Oveit data”Ticket sales
Section titled “Ticket sales”Use tickets to track sales by event over time.
Attendance
Section titled “Attendance”Join events with attendees to measure turnout.
Event view
Section titled “Event view”Use events to compare performance across your events.
Use Oveit data in your AI and BI tools
Section titled “Use Oveit data in your AI and BI tools”Once Oveit 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 Oveit 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 Oveit connector pricing and plan details.
Related connectors
Section titled “Related connectors”- Google Ads: Sync Google Ads to BigQuery.
- Custobar: Sync Custobar to BigQuery.
- Google Search Console: Sync Google Search Console to BigQuery.
- HubSpot: Sync HubSpot to BigQuery.
- Adform: Sync Adform to BigQuery.
- Amplitude: Sync Amplitude to BigQuery.