Google Cloud Storage (GCS)

Setting up your Google Cloud Storage bucket destination.

Creating a GCS Destination

You can create a new GCS destination from your DCN by going to the Integrations -> Destinations section in your navigation menu or by using the CLI. (see above tab).

To add your GCS bucket, you will need to enter the name of this destination (this is how your destination will appear in the listing), the GCS bucket URL and your GCS credentials file.

The credentials file or<credentials-path> via the CLI is required and should refer to a GCP service account's credential JSON file, which you can download from IAM. The service account must have at least write permissions to the specified bucket (storage.objects.create).

Finally, if you created the destination using your DCN UI you will be redirected to the destinations listing. If you used the CLI, you will be able to export directly from the at the command line.

Exporting Audiences to GCS Buckets.

To export to your GCS bucket, navigate to the audience you want to export and click "Export in the top right. From there you will be asked to select your preferred GCS export destination from a list of all available destinations.

Here you can select what format to export your audience as, both CSV or TSV formats are supported. In addition to the format, you can choose to export either IDs or ID clusters, as well as which IDs to export and various export options. At the bottom of the export page, you can set the name of the file that will be exported to your GCS bucket.

What Can I Export to GCS?

You can export IDs only or ID clusters. All ID types are supported by this destination type. Exports to this destination also have the following optional settings:

  • Include the header row.

  • Include values prefixed with type indicator.

  • ID type in second column.

  • Export an additional METADATA file

How Will my Export Appear in GCS?

Your export will appear in your GCS bucket with the file name you set during export creation.

If you choose to re-export an audience with the same name, it will overwrite the existing file in your storage bucket. However, if you opt for a filename that does not currently exist, a new file will be created upon export.

Last updated