Connect · Data warehouse
Bloomreach to Snowflake
Directory data as of October 23, 2026
Bloomreach's own catalog lists Snowflake, moving data both ways (1 listing). None of the other CDPs in the CdpHub directory lists both a connector that reads from Bloomreach and one that sends data to Snowflake; 8 go the other way, from Snowflake to Bloomreach.
Bloomreach's own Snowflake integration
1 listingBloomreach is one of the CDPs in the directory, and its own catalog lists Snowflake: the two connect directly, with no other platform in between.
Imports Snowflake customers, events and catalogs into Bloomreach over a key-pair connection with change-tracking syncs, and covers loading Bloomreach exports into Snowflake via Google Cloud Storage.
CDPs that can carry Bloomreach data into Snowflake
0 CDPsNone of the other 43 CDPs in the directory lists both a connector that reads from Bloomreach and one that sends data to Snowflake. Bloomreach's own integration above is the direct route.
The other way: Snowflake to Bloomreach
8 CDPsEach of these CDPs lists a connector that reads from Snowflake and one that sends data to Bloomreach.
Reads from Snowflake
Amperity ⇄ SnowflakeShares data both ways between Amperity and Snowflake through Amperity Bridge, using Snowflake Secure Data Sharing so nothing is copied or exported.
Sends to Bloomreach
Amperity → BloomreachCreates and updates customer profiles in Bloomreach Engagement from Amperity queries or segments, matched on a Bloomreach hard ID (in beta).
Reads from Snowflake
Snowflake → Fivetran ActivationsSource. Reads Snowflake tables and views for Fivetran Activations syncs through a dedicated user, role and compute warehouse, with key-pair sign-in recommended over deprecated passwords.
Sends to Bloomreach
Fivetran Activations → BloomreachSends 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 Snowflake
Snowflake → HightouchIceberg source. Reads Apache Iceberg tables managed in Snowflake as a Hightouch source.
Snowflake → HightouchSource. Connects Snowflake to Hightouch as a source, with models built in SQL, dbt, Looker, Sigma, a table selector or Customer Studio.
Sends to Bloomreach
Hightouch → BloomreachUploads customer attributes and custom events from your warehouse to Bloomreach for attribute-based audiences.
Reads from Snowflake
Snowflake → RudderStackSource. Activates Snowflake tables, SQL models and audiences in downstream tools with RudderStack Reverse ETL.
Sends to Bloomreach
RudderStack → BloomreachCatalog. Syncs product catalog records from your warehouse to Bloomreach catalogs with RudderStack Reverse ETL, for recommendations and personalized content.
RudderStack → BloomreachEvents. Sends RudderStack customers, page views and events to Bloomreach Engagement for personalized campaigns and recommendations.
Reads from Snowflake
Snowflake → SegmentData Graph. Connects Snowflake to Segment's Data Graph through a key-pair user that reads warehouse entities for Linked Audiences and Linked Events, on the Business tier.
Snowflake → SegmentReverse ETL source. Runs Reverse ETL model queries in Snowflake and syncs the results to Segment destinations, with key-pair sign-in only (Segment marks it as in active development).
Sends to Bloomreach
Segment → BloomreachBloomreach Engagement. Sends identify, track, page, group plus alias calls from Segment to Bloomreach Engagement for analytics and email marketing in cloud mode.
Reads from Snowflake
Simon Data ⇄ SnowflakeConnected deployment. Runs Simon Data on your own Snowflake account in a Connected deployment, reading the tables you grant to a dedicated role and building its own schemas, views and tasks in a database you create.
Snowflake → Simon DataInbound share. Brings Snowflake tables into Simon Data through a secure data share you create and grant to Simon's Snowflake account, an optional premium feature arranged with your account manager.
Sends to Bloomreach
Simon Data → BloomreachSyncs 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 Snowflake
Snowflake → TealiumAudience Discovery app. Builds audiences inside Snowflake with Tealium's native Snowflake app, using point-and-click filters or Cortex queries, then loads them into Tealium through a Snowflake data source.
Snowflake → TealiumCloud data source. Polls chosen Snowflake tables or views into Tealium attributes, connecting with a custom role that has USAGE privileges and an RSA key pair generated in or uploaded to Tealium.
Sends to Bloomreach
Tealium → BloomreachClient-side tag. Adds Bloomreach's tag through Tealium iQ, with control over the page and event types shared with it.
Tealium → BloomreachServer-side connector. Updates Bloomreach customer properties, adds events (singly or batched) and triggers transactional emails and SMS from AudienceStream or EventStream.
Reads from Snowflake
Snowflake → ZeotapSource. Loads customer data from Snowflake into Zeotap through a direct connection made in the Sources app, refreshed automatically at the sync frequency you pick.
Sends to Bloomreach
Zeotap → BloomreachPushes 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 Snowflake. Join the waitlist for early access.
Bloomreach and the other warehouses
- Bloomreach to BigQueryDirect
More into Snowflake
- Klaviyo to SnowflakeDirect · 9 CDPs
- HubSpot to Snowflake16 CDPs
- Salesforce to Snowflake19 CDPs
- Shopify to Snowflake21 CDPs
- Mailchimp to Snowflake9 CDPs
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 Snowflake 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, Snowflake or any platform listed.
Getting Bloomreach data into Snowflake?
Vendor-neutral help choosing the route that fits your stack, and getting the connection running.