Search documentation...


Google Cloud Storage

Transfer data at scale from your warehouse to Google Cloud Storage


To get started, select your Google Cloud credential (service account). If you need to create a cloud credential, consult our documentation.

Then, you will need to enter GCP Project ID and GCS Bucket Name. The "GCS Bucket Name" should just be the name of the bucket, not a URL.


Sync Modes

  • All - All Mode creates a CSV file with all the rows in the query results, every time the sync is run.
  • Insert - Insert mode creates a CSV file with the rows that were added since the last sync.

File Name

The file name field will allow you to specify the prefix and the name of the file that you want to use for your results. In the screenshot below, we've specified that we want the file to be called results.csv, with a custom prefix.

You can also timestamp variables in the file name, surrounding each with {}. We currently support these timestamp variables: YYYY, MM, DD, HH, mm. All dates and times will be UTC.

For example: upload/{YYYY}-{MM}-{DD}-{HH}-{mm}-result.csv.

You can also set a File Name Timestamp Offset. By default, the date/time used to generate the file name (above) is the date/time that the sync takes place; you can enter a number of seconds to offset this (offset can be positive or negative).

Ex. To set the date in the file name to 24 hours before the sync takes place, input -86400. The default offset is 0.

Columns to Sync

For this destination, we give you the ability to export all columns as they are represented in your model.

If you need remap the fields that you're exporting, maybe because you don't want to alter your model, you can manually map fields. Only the fields that you map will be exported in this instance. In this example, we're exporting Customer ID, Email, Name, and Price. These fields are mapped to new fields in the CSV as customer_id, email, and name, and price, respectively. All other columns from your results are ignored.

CSV Header

We provide you the option to include a CSV header with your exported results.

Other Considerations

If a file at that path already exists at the time of a sync, Hightouch will overwrite it. To keep different versions of the same results file, you can enable versioning in your bucket, or your application can copy the data to another location.

This destination will not respect any sorting that you have in your model. It will export results file sorted by ID.

    Need help?

    Our team is relentlessly focused on your success. We're ready to jump on a call to help unblock you.

    • Connection issues with your data warehouse?
    • Confusing API responses from destination systems?
    • Unsupported destination objects or modes?
    • Help with complex SQL queries?

    Feature Requests?

    If you see something that's missing from our app, let us know and we'll work with you to build it!

    We want to hear your suggestions for new sources, destinations, and other features that would help you activate your data.

On this page

SetupSyncingSync ModesFile NameColumns to SyncCSV HeaderOther Considerations

Was this page helpful?