What this integration does
Section titled “What this integration does”Google BigQuery lets you export SEINō campaign data to your own BigQuery project and dataset. SEINō handles the write, so your team can query the data in your own warehouse environment.
This is a managed integration. You do not need to build the export yourself, but SEINō does need the target project and dataset before we can connect it.
What data is synced
Section titled “What data is synced”SEINō exports the aggregated email campaign dataset, not a raw event stream. The data is the campaign reporting data SEINō already computes, written into BigQuery for your own analysis and downstream use.
Each sync replaces the destination table with the latest snapshot. BigQuery therefore shows the most recent exported state instead of building an append-only history.
What we need from you
Section titled “What we need from you”To set up the export, SEINō needs:
- your Google Cloud Project ID
- the name of the BigQuery dataset
- write access for
seino-app@seino-ai.iam.gserviceaccount.com
The dataset should already exist and be empty when we connect it.
How often it syncs
Section titled “How often it syncs”SEINō refreshes the export whenever the campaign dataset has newer data. It is not a one-time export.
Because each run replaces the table, the BigQuery dataset stays aligned with the latest SEINō snapshot.
Do we need to do anything manually?
Only the setup inputs. Once the project, dataset, and permissions are in place, SEINō can write the data directly to your BigQuery environment.
Can we keep historical copies in BigQuery?
The export itself writes the latest snapshot. If you want history, copy each run into a separate table before the next refresh.
Who should we contact if the connection is not writing data?
Contact SEINō support. We monitor the sync and can help confirm whether the export is running and whether the target dataset is reachable.