New: The Agentic CDP

·Read the analysis

Connect · Data warehouse

Bloomreach to BigQuery

Directory data as of October 23, 2026

Bloomreach's own catalog lists BigQuery, moving data both ways (2 listings). None of the other CDPs in the CdpHub directory lists both a connector that reads from Bloomreach and one that sends data to BigQuery; 8 go the other way, from BigQuery to Bloomreach.

0CDPs can carry Bloomreach data into BigQuery
8CDPs can carry BigQuery data to Bloomreach
2BigQuery listings in Bloomreach's own catalog
30of 44 CDPs list BigQuery

Bloomreach's own BigQuery integrations

2 listings

Bloomreach is one of the CDPs in the directory, and its own catalog lists BigQuery: the two connect directly, with no other platform in between.

Bloomreach → BigQuery

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.

BigQuery → Bloomreach

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.

All Bloomreach integrations →

CDPs that can carry Bloomreach data into BigQuery

0 CDPs

None of the other 43 CDPs in the directory lists both a connector that reads from Bloomreach and one that sends data to BigQuery. Bloomreach's own integration above is the direct route.

The other way: BigQuery to Bloomreach

8 CDPs

Each of these CDPs lists a connector that reads from BigQuery and one that sends data to Bloomreach.

  • Reads from BigQuery

    Amperity ⇄ BigQuery

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

    Sends to Bloomreach

    Amperity → Bloomreach

    Creates and updates customer profiles in Bloomreach Engagement from Amperity queries or segments, matched on a Bloomreach hard ID (in beta).

  • Reads from BigQuery

    BigQuery → Fivetran Activations

    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.

    Sends to Bloomreach

    Fivetran Activations → Bloomreach

    Sends customer attributes and events from Fivetran Activations to Bloomreach, matching customers on registered or cookie IDs, with Bloomreach API keys and a project token.

  • Reads from BigQuery

    BigQuery → Hightouch

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

    BigQuery → Hightouch

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

    Sends to Bloomreach

    Hightouch → Bloomreach

    Uploads customer attributes and custom events from your warehouse to Bloomreach for attribute-based audiences.

  • Reads from BigQuery

    BigQuery → RudderStack

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

    Sends to Bloomreach

    RudderStack → Bloomreach

    Catalog. Syncs product catalog records from your warehouse to Bloomreach catalogs with RudderStack Reverse ETL, for recommendations and personalized content.

    RudderStack → Bloomreach

    Events. Sends RudderStack customers, page views and events to Bloomreach Engagement for personalized campaigns and recommendations.

  • Reads from BigQuery

    BigQuery → Segment

    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).

    BigQuery → Segment

    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.

    Sends to Bloomreach

    Segment → Bloomreach

    Bloomreach Engagement. Sends identify, track, page, group plus alias calls from Segment to Bloomreach Engagement for analytics and email marketing in cloud mode.

  • Reads from BigQuery

    BigQuery → Simon Data

    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.

    Sends to Bloomreach

    Simon Data → Bloomreach

    Syncs Simon Data contact attributes and segment membership to Bloomreach Engagement and triggers its scenarios, using an API key with Tracking, Scenarios and Segmentations permissions.

  • Reads from BigQuery

    BigQuery → Tealium

    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.

    Sends to Bloomreach

    Tealium → Bloomreach

    Client-side tag. Adds Bloomreach's tag through Tealium iQ, with control over the page and event types shared with it.

    Tealium → Bloomreach

    Server-side connector. Updates Bloomreach customer properties, adds events (singly or batched) and triggers transactional emails and SMS from AudienceStream or EventStream.

  • Reads from BigQuery

    BigQuery → Zeotap

    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.

    Sends to Bloomreach

    Zeotap → Bloomreach

    Pushes Zeotap audience segments into Bloomreach Engagement, formerly Exponea, through its API, so Bloomreach can send personalized email, SMS or push campaigns to those users right away.

Get an email when these routes change

CdpHub Pro will alert you when a CDP adds, renames or retires a connector between Bloomreach and BigQuery. Join the waitlist for early access.

Join the Pro waitlist →

Bloomreach and the other warehouses

About these numbers

CdpHub documents each integration from the platform's own catalog, so a listing records what the platform says it supports, not a test of the connector. A route counts a CDP that lists a connector reading from one end and another sending data to the other: a possible path, not a tested one. What travels, how often and in which format depends on each connector and its plan, so follow the documentation links. Bloomreach is a CDP in the directory too, so its own listings for BigQuery come first. Counts are updated as catalogs change; this page reflects the directory as of October 23, 2026. CdpHub is independent and not affiliated with Bloomreach, BigQuery or any platform listed.

Getting Bloomreach data into BigQuery?

Vendor-neutral help choosing the route that fits your stack, and getting the connection running.

We use cookies to enhance your experience. By continuing to visit this site you agree to our use of cookies. Read our cookie policy