New: The Agentic CDP

·Read the analysis

Tool · Data Infrastructure

Google Cloud Storage integrations across CDPs

Directory data as of October 18, 2026

27 of the 44 customer data platforms in the CdpHub directory list an integration with Google Cloud Storage, with 39 listings between them. Of those platforms, 13 both send data to Google Cloud Storage and read from it, 11 only send data to it and 3 only read from it. 1 can run server-side and 38 in the warehouse. 38 of the 39 listings link to their platform's own documentation.

27of 44 CDPs list Google Cloud Storage
39listings across them
13send data to Google Cloud Storage and read from it
#12most listed of 2,243 tools

Which CDPs list Google Cloud Storage

27 of 44
Sends data to Google Cloud Storage Reads from Google Cloud Storage, or uses it as a source Does both

Not listed by 17 CDPs: 6sense, Blueshift, Informatica, Klaviyo, Leadspace, Lexer, Listrak, Microsoft Dynamics 365 Customer Insights, NICE, Optimizely, Oracle, SAP CDP, SAP Engagement Cloud, SAS, Spotler ActivatePro, Teradata and Upland BlueVenn.

How each CDP connects to Google Cloud Storage

27 CDPs · 39 listings
ActionIQ (reads from Google Cloud Storage)1 listing
Google Cloud Storage → ActionIQ

Google Cloud Storage

All ActionIQ integrations →
Adobe Experience Platform (sends data to Google Cloud Storage and reads from it)2 listings
Adobe → Google Cloud Storage

Destination. Exports Real-Time CDP audiences and datasets as data files into Google Cloud Storage buckets on a recurring schedule, configured in the UI or through the API.

Google Cloud Storage → Adobe

Source. Brings Google Cloud Storage files in XDM JSON, XDM Parquet or delimited format into Experience Platform in batches, authenticated with interoperability access keys.

All Adobe Experience Platform integrations →
Amperity (sends data to Google Cloud Storage and reads from it)2 listings
Amperity → Google Cloud Storage

Destination. Sends Parquet, CSV, JSON and other files from Amperity to any Google Cloud Storage bucket, for storage or downstream use.

Google Cloud Storage → Amperity

Source. Pulls files of any supported format from Google Cloud Storage buckets into Amperity using a service account.

All Amperity integrations →
Bloomreach (sends data to Google Cloud Storage and reads from it)1 listing
Bloomreach ⇄ Google Cloud Storage

Connects a Google Cloud Storage bucket to Bloomreach with service-account JSON credentials so data files can be imported from the bucket or exported to it.

All Bloomreach integrations →
BlueConic (sends data to Google Cloud Storage and reads from it)1 listing
BlueConic ⇄ Google Cloud Storage

Pulls CSV files from Google Cloud Storage buckets into BlueConic profiles, groups and timeline events and drops exported profile and event files into a bucket in scheduled batches.

All BlueConic integrations →
Braze (sends data to Google Cloud Storage and reads from it)2 listings
Braze → Google Cloud Storage

Currents. Streams Braze Currents data into a Google Cloud Storage bucket, ready for an ETL job to load it into BigQuery or other systems.

Google Cloud Storage → Braze

Cloud Data Ingestion. Ingests new files from a Google Cloud Storage bucket into Braze as they're finalized, using Pub/Sub notifications, for attributes, events, purchases and catalogs.

All Braze integrations →
CaliberMind (sends data to Google Cloud Storage and reads from it)2 listings
CaliberMind → Google Cloud Storage

Export. Exports CaliberMind tables, such as attribution and engagement scoring, as gzip CSV files to a dedicated Google Cloud Storage bucket each night, overwritten for your ETL to collect.

Google Cloud Storage → CaliberMind

Import. Takes in files your data warehouse exports to a Google Cloud Storage bucket CaliberMind sets up, in Avro, Parquet, CSV or TSV with gzip compression, then stages them as BigQuery tables.

All CaliberMind integrations →
Chord (sends data to Google Cloud Storage and reads from it)2 listings
Chord → Google Cloud Storage

Export. Writes Chord data to a brand's Google Cloud Storage bucket using a Chord service account that holds a custom role able to create, list and delete objects.

Google Cloud Storage → Chord

Import. Gives Chord's Snowflake-based warehouse read access to files in a Google Cloud Storage bucket through a custom role granted to a service account that Chord supplies.

All Chord integrations →
CleverTap (sends data to Google Cloud Storage)1 listing
CleverTap → Google Cloud Storage

Exports CleverTap events or profiles in bulk to a Google Cloud Platform bucket through a service account with Storage Admin rights, on Enterprise, Advanced and Cutting Edge plans.

All CleverTap integrations →
DinMo (sends data to Google Cloud Storage)1 listing
DinMo → Google Cloud Storage

Drops DinMo models or segments into a Google Cloud Storage bucket as CSV, JSON, XML or Parquet, with large snapshot, insert or difference exports split into numbered files of up to 10 million rows.

All DinMo integrations →
Fivetran Activations (sends data to Google Cloud Storage)1 listing
Fivetran Activations → Google Cloud Storage

Writes warehouse data as files into a Google Cloud Storage bucket from Fivetran Activations, after you grant bucket access to a Google identity the platform provides.

All Fivetran Activations integrations →
Hightouch (sends data to Google Cloud Storage and reads from it)2 listings
Hightouch → Google Cloud Storage

Destination. Writes user and product data as CSV files into Google Cloud Storage buckets.

Google Cloud Storage → Hightouch

Source. Reads data files from Google Cloud Storage as a Hightouch source, for syncing to other tools.

All Hightouch integrations →
Insider One (sends data to Google Cloud Storage)1 listing
Insider One → Google Cloud Storage

Exports Insider One event data, with chosen parameters and user attributes, as CSV files to your Google Cloud Storage bucket every 1 to 24 hours, authenticated with HMAC keys.

All Insider One integrations →
Lytics (sends data to Google Cloud Storage and reads from it)1 listing
Lytics ⇄ Google Cloud Storage

Imports activity and profile files from a Google Cloud Storage bucket into Lytics and exports audiences, user fields and raw events to a bucket as CSV files.

All Lytics integrations →
mParticle (sends data to Google Cloud Storage)2 listings
mParticle → Google Cloud Storage

Audiences. Writes mParticle audience membership files to a Google Cloud Storage bucket.

mParticle → Google Cloud Storage

Events. Writes mParticle event batches to a Google Cloud Storage bucket for archiving or processing.

All mParticle integrations →
Odie (reads from Google Cloud Storage)1 listing
Google Cloud Storage → Odie

Connects Totango to a Google Cloud Storage bucket through its S3-compatible interface with HMAC keys, granting a service account object get and list roles.

All Odie integrations →
Ometria (sends data to Google Cloud Storage)1 listing
Ometria → Google Cloud Storage

Writes customized Ometria data exports to a Google Cloud Storage bucket, authenticated with a JSON service account key that can create objects and read the bucket.

All Ometria integrations →
Redpoint Global (sends data to Google Cloud Storage and reads from it)2 listings
Redpoint Global ⇄ Google Cloud Storage

Content provider. Adds a Google Cloud Storage project to Redpoint Interaction as an external content provider, authorized with Google OAuth client credentials and an API key.

Redpoint Global ⇄ Google Cloud Storage

Data Management. Exposes Google Cloud Storage buckets as file systems in Redpoint Data Management, authenticated with a service account key file or application default credentials.

All Redpoint Global integrations →
RudderStack (sends data to Google Cloud Storage)2 listings
RudderStack → Google Cloud Storage

Data lake. Loads RudderStack events into a Google Cloud Storage data lake as structured files that query engines can read.

RudderStack → Google Cloud Storage

Object storage. Stores RudderStack events in a Google Cloud Storage bucket as batched files, for archiving or downstream processing.

All RudderStack integrations →
Salesforce Data 360 (sends data to Google Cloud Storage and reads from it)1 listing
Salesforce ⇄ Google Cloud Storage

Moves data between Google Cloud Storage and Data 360, importing structured and unstructured files from a bucket on a schedule and exporting Data 360 data back.

All Salesforce Data 360 integrations →
Segment (sends data to Google Cloud Storage)1 listing
Segment → Google Cloud Storage

Sends all data from a Segment Engage source to a Google Cloud Storage bucket you own during each sync (beta).

All Segment integrations →
Simon Data (reads from Google Cloud Storage)1 listing
Google Cloud Storage → Simon Data

Loads Parquet, JSON, CSV or TSV files from your Google Cloud Storage bucket into a Managed Simon Data deployment on a schedule, incrementally or as full overwrites, through a Google service account.

All Simon Data integrations →
Snowplow (sends data to Google Cloud Storage)1 listing
Snowplow → Google Cloud Storage

Copies Snowplow events from a Pub/Sub subscription into Google Cloud Storage with a Dataflow job, writing windowed files that can be compressed and partitioned by date or schema.

All Snowplow integrations →
Tealium (sends data to Google Cloud Storage)1 listing
Tealium → Google Cloud Storage

Writes full or custom event, visitor and log data to Google Cloud Storage buckets from AudienceStream or EventStream.

All Tealium integrations →
Treasure AI (sends data to Google Cloud Storage and reads from it)4 listings
Treasure AI → Google Cloud Storage

Export v1. Writes Treasure Data job results to a Google Cloud Storage bucket as CSV or TSV files, signing in with a service account JSON key.

Treasure AI → Google Cloud Storage

Export v2. Exports Treasure Data job results as CSV or TSV files to Google Cloud Storage with the v2 connector, which also accepts Workload Identity Federation instead of a JSON key.

Google Cloud Storage → Treasure AI

Import v1. Imports CSV and TSV files from a Google Cloud Storage bucket into Treasure Data by path prefix or regex, and on scheduled runs picks up only files after the last path read.

Google Cloud Storage → Treasure AI

Import v2. Loads CSV and TSV files from Google Cloud Storage into Treasure Data with the v2 connector, which adds Workload Identity Federation alongside service account keys.

All Treasure AI integrations →
Zeotap (sends data to Google Cloud Storage)1 listing
Zeotap → Google Cloud Storage

Delivers Zeotap audiences to a folder in your own Google Cloud Storage bucket as CSV files, with identifiers alone or with attributes, through a Zeotap or client service account.

All Zeotap integrations →
Zeta Global (sends data to Google Cloud Storage and reads from it)1 listing
Zeta Global ⇄ Google Cloud Storage

Brings files from Google Cloud Storage into Zeta Data Flows and sends cleaned files, audience lists and report builder exports back to buckets, authenticated with service account keys.

All Zeta Global integrations →

Other Data Infrastructure tools

All tools on two or more 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. Each one notes which way data flows and where the integration runs. A platform can list more than one connector for Google Cloud Storage, so listings can outnumber platforms; a platform that both sends data to Google Cloud Storage and reads from it is counted once, as doing both. The rank orders all 2,243 tools in the directory by how many platforms list them; tools listed on the same number of platforms share a rank. Counts are updated as catalogs change; this page reflects the directory as of October 18, 2026. CdpHub is independent and not affiliated with Google Cloud Storage or any platform listed.

Connecting Google Cloud Storage to a CDP?

Vendor-neutral help choosing the CDP that fits how you use Google Cloud Storage, and getting the connection running in your stack.

Talk to CdpHub →

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

C
CdpHub × LiveAvatar
Early Access: CdpHub's AI guide draws from our integration directory but may occasionally provide incomplete or inaccurate information. We're actively improving it — your patience and feedback are appreciated. When you use the mic, your voice is transcribed so Ed can answer.
Ed, CdpHub's AI guide

CdpHub · Powered by Claude + LiveAvatar

Ask Ed