Data Dictionary
Start typing to search…

Google Cloud Storage Setup and Configuration

Bucket and Permissions Setup

To sync data from Triple Whale to Google Cloud Storage (GCS), you must create a storage bucket and grant the necessary permissions. This guide walks you through the setup process to ensure a seamless connection.

Step 1: Create a GCS Bucket

  1. Open the Google Cloud Console and navigate to Cloud Storage > Buckets. Click Create.


  2. Enter a Bucket Name (e.g., triplewhale-data), and configure additional settings as needed. Learn more about creating GCS buckets

  3. Click Create to finalize.

Step 2: Grant Permissions to the Service Account

Triple Whale requires specific permissions to write data to your GCS bucket.

  1. Locate and select the bucket created in Step 1.

  2. Navigate to the Permissions tab.

  3. Click Grant Access to add a new permission.

    Granting access to the service account in GCS.

  4. In the New principals field, enter the Triple Whale service account email:[email protected]

  5. Under Role, select both of the following:

    • Storage Object Creator (Allows writing data to the bucket).
    • Storage Object Viewer (Allows reading data from the bucket).

    Assigning the required roles to the service account.

  6. Click Save to apply the changes.

Connecting to Triple Whale

Once your GCS bucket is set up, connect it to Triple Whale:

  1. Go to your Triple Whale Integrations page.

  2. Click Connect on the Google Cloud Storage integration.

    Connecting Google Cloud Storage to Triple Whale.

  3. Enter the bucket name created in Step 1 (e.g., triplewhale-data).

  4. Click the checkbox confirming that you added the Triple Whale service account (Step 2).

  5. Click Save to complete the setup.

Troubleshooting

📘

Common Errors and Fixes

  • "Service account does not exist": Ensure that you entered the correct service account email when granting permissions.
  • "Access Denied": This error indicates insufficient permissions. Go to Cloud Storage > Bucket Permissions and ensure the service account has both Storage Object Creator and Storage Object Viewer roles.
  • "Bucket Not Found": Double-check that the correct bucket name was entered in the integration settings.