Google Cloud Storage

Use GrowthLoop audiences for file exports to Google Cloud Storage.

Connect this destination to export audience membership as CSV files, for use in a bucket you control.

This destination writes to your Google Cloud Storage bucket and is a good fit when you want to:

  • Use a file export rather than a paid-media or messaging API
  • Have a GCS bucket and a service account that can write to it

This maps to GrowthLoop Audiences:

Use it forAudiences
Dropping audience CSVs in a Google Cloud Storage bucket✓

If Google provisioned a public bucket for Ad Manager audience lists, use Google Ad Manager 360 instead.

Prerequisites

Make sure you have:

  • A Google Cloud Storage bucket.
  • A service account with the Editor role on that bucket, and its key saved as a JSON file.

If you already have the JSON key, skip to Set up Google Cloud Storage as a destination.

Create a service account

The service account needs permission to manage the bucket. See Google's service account instructions. Assign the Editor role (one of Google Cloud's Basic Roles).

We recommend creating a new service account for GrowthLoop.

Create a JSON key

JSON keys let GrowthLoop use the service account. Save the file in a secure place. The key is not recoverable. If you lose it, create another. You can have up to 10 keys per service account.

You need administrative privilege over keys for the bucket. If you get a permissions error, ask your Google Cloud administrator to grant key creation access or create the key and send you the JSON.

  1. In Google Cloud, search for your bucket name in the Search bar. If the dropdown says No results, press Enter. The bucket still appears on the next screen.
Google Cloud search bar used to find a Cloud Storage bucket
  1. Select the bucket.
Google Cloud Storage bucket selected
  1. Click Permissions.
Cloud Storage bucket Permissions tab
  1. Find the service account with storage privileges. Service accounts include gserviceaccount in the Principal column. Copy that name.
Bucket permissions list showing a service account principal
  1. Search for Service Accounts and open that page.
Google Cloud search results for Service Accounts
  1. Open the service account that matches the name you copied.
Service account selected from the Service Accounts list
  1. Open Keys. Click Add Key → Create New Key.
Service account Keys tab with Create New Key
  1. Select JSON and click Create. The key file downloads to your computer.
Create private key dialog with JSON selected

Set up Google Cloud Storage as a destination

  1. In GrowthLoop, click the Destinations tab on the left sidebar.
  2. Click New Destination in the upper right corner.
  3. Search for GCS under Buckets and click Add GCS.
Select Destination modal showing Add GCS under Buckets
  1. Enter the required information, then click Create.
Google Cloud Storage destination setup form
FieldDescription
Destination NameName this destination in GrowthLoop. Use a name so your team recognizes its purpose, like "Google Cloud Storage Exports".
Sync FrequencySet the default export frequency (for example, hourly or daily). You can override this setting for individual exports.
BucketThe name of your Google Cloud Storage bucket.
CredentialsThe entire contents of your service account JSON key file.
Columns to ExportDataset columns to include by default. Use the column names from your warehouse. If you leave this blank, GrowthLoop exports all columns.

GrowthLoop validates the connection. Google Cloud Storage then appears in your list of connected destinations.

Google Cloud Storage destination listed after a successful connection

Export to Google Cloud Storage

From within GrowthLoop, export from an audience. See Export an audience if you need more information on these steps.

After building or selecting an audience, click Export, then search for your GCS destination.

Configure the export

Google Cloud Storage export settings with export type and personalization fields
SettingAudience export
Export TypeExport All Records writes every audience member on each run. Export Updates (Deltas) writes only members added since the last export.
Personalization FieldsExtra columns for this export. By default, GrowthLoop sends the destination Columns to Export. You can also map custom attributes from the audience.

Export behavior

This is what GrowthLoop writes when you export an audience.

BehaviorWhat happens
What GrowthLoop writesCSV files in a folder for that audience in your GCS bucket. Direction is GrowthLoop → Google Cloud Storage.
When it runsGrowthLoop sends the export as a batch on the next successful run. An export that starts Now runs within about 15 minutes.
DeliveryA folder unique to the audience. That folder contains an individual CSV file for each audience member.
Export All RecordsEach run writes a file for every current audience member.
Export Updates (Deltas)Each run writes files only for new audience members.
Columns to ExportIf you set this on the destination, GrowthLoop limits the files to those columns unless you add personalization fields.

Confirm the export was successful

When the run finishes, confirm you can use the data in Google Cloud Storage.

  • Audience export: Open your Google Cloud Storage bucket, find the folder for that audience, and look up the CSV files inside.
Google Cloud Storage folder containing audience CSV files

In GrowthLoop, review counts on the audience Exports tab. See Export an audience for more information.

Congrats on successfully exporting to Google Cloud Storage!

Troubleshooting

These are the issues we see most often. You can always email us at [email protected] for help.

ProblemCauseResolution
Connection fails to validateThe JSON key is incomplete, or the service account cannot write to the bucketPaste the entire JSON key. Confirm the service account has the Editor role on the bucket
You cannot create a JSON keyYour user cannot manage keysAsk a Google Cloud administrator to grant key access or create the key for you
Expected columns are missingColumns to Export or Personalization Fields omit those columnsAdd the columns on the destination or on the export
The files are missing in GCSYou are looking at the bucket rootOpen the folder unique to the audience

What’s Next

Export an audience after you connect a destination

Did this page help you?