Skip to main content

​
What this is

Google Cloud Storage (GCS) is Google Cloud’s object storage service. Connecting it as a Zeotap CDP destination lets you deliver an audience — its identifiers and any attributes you map — as CSV files into a folder inside a GCS bucket you own. Downstream, those files can drive campaign automation, personalisation, and optimisation in whatever system reads your bucket. This page walks through configuring the destination, choosing between the two send actions, understanding the file names Zeotap writes, verifying delivery, and resolving the configuration errors that block it.
Audiences and Segments refer to the same thing throughout the Zeotap CDP UI — a group of customer profiles that match a set of criteria you define.

​
Prerequisites

Before you begin, gather the following:
  • A Google Cloud Storage account and a bucket you can write to.
  • The bucket name and the folder path inside that bucket where files should land.
  • Authentication: either the Zeotap Service Account (which you whitelist on your bucket) or a client service account JSON file you upload during configuration.
  • If you plan to encrypt files in transit, a PGP public key file. See PGP encryption in destinations.

​
Supported identifiers

This integration accepts MAIDs, hashed email addresses, hashed mobile numbers, and CRM IDs. You can send any number of identifiers and attributes per audience.

​
Available actions and supported features

​
Understand the destination components

You configure three GCS-side details in Zeotap CDP:
  • Bucket — the name of your Google Cloud Storage bucket. You obtain it from your GCS console.
    Bucket name shown in the Google Cloud Storage console
  • Folder — a folder path inside the bucket. GCS does not have real folders; the folder concept is emulated by object key names containing / separators, which replicate a hierarchical arrangement.
    Folder path inside a bucket in the Google Cloud Storage console
  • Account — the identity Zeotap uses to write into your bucket. Choose either the Zeotap Service Account (which you then whitelist on your bucket) or upload a client service account JSON you manage.

​
Configure the destination

1

Open the Destinations application

Log in to the Zeotap CDP App and open the Destinations application.
2

Start a new destination

Click + Create Destination.
Create Destination button in the Destinations application
3

Select Google Cloud Storage

Under All Destinations, search for Google Cloud Storage and select it.
Searching for Google Cloud Storage under All Destinations
4

Fill in the destination fields

On the right-hand side of the destination screen, provide the following values:a. A name for the destination.b. A value for Destination Instance Name — an internal field.c. The Bucket name of your Google Cloud Storage bucket.d. The Folder path inside that bucket where Zeotap CDP should write exported data.
The folder path must:
  • Follow the structure folder_name/sub_folder_name/.
  • Not start with a /.
  • End with a / (both the folder name and any sub-folder name).
e. A Filename Prefix. Enter a text value without spaces, underscores (_), or the symbols # @ $ % & *. The full file name follows the pattern shown in Understand exported file names below.f. Under Account, choose either Zeotap Service Account or Client Service Account Json from the drop-down:
Account drop-down with Zeotap Service Account and Client Service Account Json options
  • Zeotap Service Account — the service account Zeotap will use auto-populates under Service Account to be Whitelisted. Whitelist it on your bucket in Google Cloud before saving so Zeotap CDP can push audiences to your bucket.
    Service Account to be Whitelisted auto-populated for the Zeotap Service Account
  • Client Service Account Json — use + Select File to upload the JSON key for a service account you manage so that Zeotap CDP can push audiences to your bucket.
    Uploading a client service account JSON key using + Select File
g. Under Send Encrypted Data, choose whether to encrypt files using PGP. If you choose Yes, upload the Public Key.
Send Encrypted Data option with PGP public key upload
h. Review every value entered above, then click Next to proceed.
Reviewing the destination values before clicking Next
5

Choose the action and map fields

Under Choose your Action, pick one:
  • Send Identifiers to Google Cloud Storage — sends MAIDs and raw email addresses.
    Send Identifiers to Google Cloud Storage action
  • Send attributes and identifiers to Google Cloud Storage — sends any identifiers and attributes you map.
    Send attributes and identifiers to Google Cloud Storage action
6

Create the destination

Click Create Destination. The destination now appears in the Audiences application and can be linked to an audience.

​
Verify the destination is working

You know the destination is configured correctly when:
  1. After you click Create Destination, it appears in the destination list inside the Audiences application.
  2. After you link an audience to it (see Link an audience to the destination) and the next audience refresh runs, CSV files land in your bucket under the folder path you configured.
  3. The file names follow the naming pattern described below.

​
Understand exported file names

Zeotap CDP writes each activation as one or more CSV files. The name pattern is:
The timestamp is formatted as yyyy-MM-dd, and destinationAudienceId is the ID Zeotap CDP assigns to the audience after it is linked to this destination. Example file name:
Channel ID on the audience matching the destinationAudienceId in the exported file name
The parts of the name are:

​
Multipart uploads

When a file is uploaded in multiple parts, the name pattern is:
Where:
  • partNumber — the index of the part in the multipart upload. Part0 is the first part.
  • channelId — the ID Zeotap CDP assigns to the audience after it is linked to this destination.
  • ${timestamp} — the timestamp in epoch milliseconds.
Channel ID displayed on the audience details in the Audiences application
Worked example — an audience named PublicAbove18 with Channel ID 12345678, Filename Prefix testprefix, and file number 98765, uploaded as the first part of a multipart upload at epoch milliseconds 1625138600:

​
Why this happens

When a Google Cloud Storage destination misbehaves, check the destination configuration and the bucket-side permissions. Match your symptom to a row below and inspect the location listed:

​
When to contact support

Contact Zeotap Support if:
  • You corrected the configuration above, whitelisted the Zeotap Service Account on the bucket, and files still do not arrive after the next audience refresh.
  • Files land in the bucket but their contents do not match the identifiers and attributes you mapped.
  • You see an error on the destination or on the linked audience that does not match any row in the table above.
Include in your request:
  • The destination name and the destinationAudienceId visible on the audience in the Audiences application.
  • The bucket name and folder path you configured.
  • Whether you chose Zeotap Service Account or Client Service Account Json under Account.
  • The timestamp of the last audience refresh you expected files from.
  • A sample file name (if any files arrived) or a screenshot of the destination configuration.

​
FAQ

MAIDs, hashed email addresses, hashed mobile numbers, and CRM IDs. There is no cap on the number of identifiers or attributes you send per audience.
Only if you pick Zeotap Service Account under Account. If you choose Client Service Account Json and upload your own service account key, that account’s own bucket permissions apply instead.
Yes. Set Send Encrypted Data to Yes during configuration and upload a PGP public key. See PGP encryption in destinations for the full setup.
They refer to the same ID — the identifier Zeotap CDP assigns to the audience after you link it to this destination. destinationAudienceId appears in the single-file naming pattern, and channelId appears in the multipart naming pattern.

​
Next steps

Last modified on September 8, 2026