You can use an GCS (Google Cloud Storage) destination to export query results to a Google Cloud Platform GCS bucket.

Once a destination is created, you need only provide run time variables to push an activation file to a remote resource. Saved destinations are available to all users in your company and can be reused indefinitely. Destinations do not require you to re-enter location information each time data is exported. Destinations are currently only compatible with owned activation datasets.

Authentication

Before starting, you will need the following details:

• Obtain a configuration JSON file: You can find instructions on this page to configure Workload Identity Federation to allow InfoSum to authenticate with GCS without having to use service account keys.
  • Although it's not recommended, you can use a Service Account Key in the same way that we support for imports. You can follow the instructions on the imports page if you wish to authenticate in this way.
• Set access permissions in GCS: The service user needs to have Create and Write access to the Google Cloud Storage bucket they intend to push files to. If files are pushed to a subfolder, they may need to give explicit permission to Create and Write files to that subfolder.
• Bucket Details

Creating a GCS destination 

First, select the Destinations tab under Activate and then click New Destination. 

The form below appears when you select GCS as your destination type and the following fields need to be completed:

1. Destination Type: Select GCS.
2. Name: Identifies the destination
3. Description: A free-text explanation of the destination

Once completed, press Next.

Adding GCS connection details

Use destinations to create a connection between the InfoSum Platform and your GCS bucket.

The above form contains the following fields:

1. Bucket: Specify the GCS bucket name to export to (without any leading GCS identifier, for example "bucket-name" instead of "GCS://bucket-name")
2. Authentication: Select Workload Identity Federation (recommended) or Legacy Service Access Keys.
3. GCS Workload Federation Configuration (JSON). Paste your JSON file obtained from your workload identity federation config screen.
4. Filename: Add the filename you will be exporting to.

Optional: If you wish to edit these fields again during an export you will need to toggle on the switch for “not editable during export”.

Click Submit. The saved destination is stored on the Platform’s Destinations page and can be selected in the Activations tab when pushing an activation file to a remote resource. The destination can be reused and is available to all users in your company.

Activate your Data to your Destination

You can activate results to a Destination using either Segment Builder or the Query Tool. 

1. Navigate to Activations & select your activation

Once you’ve created the activation query, go to the Activation tab under Activate, where you will see each of the activation queries that have been run in your account. Please ensure you are in the correct Collaboration view at the top for the Activation you're looking for. Your latest one will be at the top, but you can search by Activation name or use filters to manage this list.

You will see a modal providing more details on the Activation you have selected, such as the query used and the name of the output column. There are three menu tabs within this box - Details, Stats, and Export History. Once you've pushed the results, the details and status will be viewable under the Export History tab.

2. Select your destination

Click on the Export blue button to configure your export. This will open a pop up asking you to select which Destination it should be sent to. You will be able to see all the Destinations that your company owns or has permission to use. 

3. Configure the export

When you select the correct Destination, the pop up will show additional options, including column mapping if required and optional fields. 

4. Click Export to Destination to initiate the activation.