BigQuery integrations across CDPs

BigQuery

Brings Google BigQuery table data into Experience Platform for Real-Time CDP Ultimate customers.

Google BigQuery (destination). Gets Amperity data into Google BigQuery by sending Parquet or CSV files to cloud storage first, then loading them for analysis.

Google BigQuery (Amperity Bridge). Shares data both ways between Amperity and Google BigQuery through Amperity Bridge, using BigQuery sharing exchanges rather than file exports.

Loomi BigQuery. Exports Bloomreach events every 6 hours and customer properties daily into a read-only Google BigQuery dataset through Loomi BigQuery, for custom SQL analysis and BI tools.

Import. Imports customers, events, catalogs and vouchers from Google BigQuery tables or SQL queries into Bloomreach with service-account credentials, and runs SQL Reports on BigQuery data in place.

Imports BigQuery tables into BlueConic profiles and timeline events and exports profile and timeline data to BigQuery tables, replacing or partitioning a table on each batch run.

Export. Delivers Blueshift campaign activity to your BigQuery project as a linked dataset from an Analytics Hub listing, updated once a day, a feature your CSM may need to switch on.

Import. Imports customer data, events, catalogs and recommendation feeds from BigQuery into Blueshift over a direct connection authenticated with a service account key.

Google BigQuery. Brings BigQuery data into Braze through a service account, syncing user attributes, events, purchases and catalog items from chosen tables or views.

Ingests warehouse data loaded into a BigQuery dataset CaliberMind creates, or connects directly to your own BigQuery instance, with possible setup fees to map it into CaliberMind.

Writes data from Chord's CDP to a BigQuery dataset in a Google Cloud project, authenticated with a service account key given as JSON, a JSON string or a file path.

Export. Exports CleverTap data to Google BigQuery through Google Cloud Storage on a schedule, for analysis and reporting alongside other business data.

Import. Imports data from Google BigQuery into CleverTap over a connection set up with a project ID, dataset ID and service account JSON key under the partner settings.

Connects a BigQuery project to DinMo through a Google Cloud service account, with DinMo datasets for segments, statistics and predictions and optional daily alerts on unusual billed usage.

Destination. Writes rows into Google BigQuery tables from Fivetran Activations, using an automatically managed service account or a service account key of your own.

Source. Reads BigQuery tables and views for Fivetran Activations syncs through IAM roles for viewing data and running unload jobs, with an optional read-only mode.

Destination. Loads model rows into a BigQuery table by insert or upsert through a Google Cloud service account that can read and write data in the project, with billing turned on.

Iceberg source. Reads Apache Iceberg tables managed in BigQuery as a Hightouch source.

Source. Connects BigQuery to Hightouch as a source, so SQL, dbt or table-based models built there can sync to any destination.

Publishes Informatica MDM SaaS master data to a Google BigQuery staging store and a sample analytical schema, with SQL views for customer, supplier, location and product reporting.

Export. Gets Insider One events, their parameters and chosen user attributes into BigQuery by exporting CSV files to your Google Cloud Storage bucket for your own pipeline to load.

Import. Imports user attributes and events from BigQuery tables or views into Insider One on a recurring schedule, mapping columns and using an update timestamp column for incremental syncs.

Sends Klaviyo profile data, event data or both into BigQuery, and can skip events coming from integrations that BigQuery already receives.

Data warehouse import. Syncs profile and event data from a BigQuery dataset into Klaviyo through a dedicated service account, with a Klaviyo Advanced KDP subscription.

Imports BigQuery tables into Lytics and exports user profiles, events, audience changes and definitions, metrics and system events from Lytics to BigQuery tables.

Audiences. Writes mParticle audience membership to tables in a BigQuery dataset in your Google Cloud project.

Warehouse. Loads incoming mParticle data into a BigQuery dataset so you can query it directly with SQL.

Warehouse Sync. Imports user and event data from a BigQuery dataset into mParticle through a Google Cloud service account with read access, as one-time or scheduled syncs.

Runs read-only SQL queries against BigQuery from Totango's Customer Data Hub, authenticating with an uploaded key for a service account given Viewer and BigQuery Data Viewer roles.

Data Management. Bulk loads Google BigQuery tables from Redpoint Data Management with application default credentials or a service account, mapping its data types to BigQuery types.

Interaction. Sets up the Simba ODBC driver for Google BigQuery in the Redpoint Interaction Docker image, so RPI can reach BigQuery through a configured data source.

Stream. Inserts RudderStack track events into a BigQuery table in near real time through Google's streaming API, rather than in batches.

Warehouse. Loads RudderStack events into BigQuery in scheduled batches, using RudderStack's standard warehouse schema.

Source. Syncs BigQuery tables or SQL models to downstream tools with RudderStack Reverse ETL, on a schedule or on demand.

Google BigQuery. Connects Data 360 and Google BigQuery through Zero Copy, querying BigQuery tables in place and sharing Data 360 data back to BigQuery.

Connects Google BigQuery tables and views to SAP Emarsys through a Relational Data connector, letting SQL segment templates and email tokens use the data in place.

Loads Segment event data into BigQuery on a schedule as a storage destination, ready for SQL analysis.

Data Graph. Gives Segment's Data Graph a BigQuery service account that reads entity tables for Linked Audiences and Linked Events and keeps checkpoints in its own dataset (in active development).

Reverse ETL source. Reads BigQuery tables through a service account so Segment Reverse ETL can sync query results onward, granted either broad predefined roles or a narrower custom role.

Extracts data from Google BigQuery into Simon Data using a project name and service account JSON credentials that hold the Data Viewer, User and Job User roles.

Loads enriched Snowplow events, and failed events if chosen, into BigQuery for analysis, keeping events in one table that adapts to new event types, set up in Console for AWS or GCP pipelines.

Google BigQuery. Appends records (singly or batched), sends full event, visitor and log data and runs custom statements in Google BigQuery from AudienceStream or EventStream.

Google BigQuery (cloud data source). Imports a Google BigQuery table or view into Tealium attributes through a service account holding the Data Viewer and Job User roles, with STRUCT columns flattened through a view.

Export v1. Writes Treasure Data job results into a BigQuery table that matches a predefined schema, in append, replace, replace backup or delete mode, with server-to-server API authentication.

Export v2. Uploads large Treasure Data result sets to BigQuery as Parquet files through BigQuery load jobs, with append, replace, replace backup or truncate modes and JSON key or WIF sign-in.

Open Catalog Access. Exposes Treasure Data's Iceberg tables to BigQuery as a federated dataset through BigQuery Omni, an experimental Open Catalog Access option that is not enabled by default.

Composable Audience Studio. Sets up Composable Audience Studio on BigQuery with a GCP service account key and a zero-copy catalog, so Treasure Data segments are built on BigQuery data without copying it.

Import v1. Imports BigQuery tables or query results into Treasure Data with the original BigQuery connector, whose connections can also serve exports unless they use OAuth.

Import v2. Imports BigQuery tables or query results into Treasure Data with version 2 of the connector, which signs in with a service account JSON key or Workload Identity Federation, not OAuth.

Live Connect zero-copy. Queries BigQuery tables in place from Treasure Data's Trino engine as Live Connect zero-copy federated queries, with no ETL, after the feature is enabled for the account.

Analytics Hub. Shares Zeotap's unified profile store, with profile, consent, ID and campaign data, with your service accounts through a private BigQuery Analytics Hub listing you subscribe to.

Destination. Sends Zeotap segments with any identifiers and attributes into a BigQuery project, dataset and table, with a Google Cloud Storage bucket and folder also set up for the transfer.

Source. Connects Zeotap directly to data held in Google BigQuery and syncs it in as a source for building customer segments, personalized content and ad targeting.

Connects Google BigQuery to Zeta with a service account key so marketers can segment on tables in place with Zero Copy Database Explorer or ingest data through Data Flows.