nav_title | article_title | alias | description | page_type | tool | search_tag |
---|---|---|---|---|---|---|
Google Cloud Storage |
Google Cloud Storage |
/partners/google_cloud_storage_for_currents/ |
This reference article outlines the partnership between Braze and Google Cloud Storage, a massively scalable object storage for unstructured data. |
partner |
Currents |
Partner |
Google Cloud Storage is massively scalable object storage for unstructured data offered by Google as part of the Cloud Computing product suite.
The Braze and Google Cloud Storage integration allows you to stream Currents data to Google Cloud Storage. You can later use an ETL process (Extract, Transform, Load) to transfer your data to other locations, such as Google BigQuery.
Requirement | Description |
---|---|
Google Cloud Storage account | A Google Cloud Storage account is required to take advantage of this partnership. |
Currents | In order to export data back into Google Cloud Storage, you need to have Braze Currents set up for your account. |
{: .reset-td-br-1 .reset-td-br-2} |
To integrate with Google Cloud Storage, you must set up the appropriate credentials that allow Braze to get information about the storage buckets being written to (storage.buckets.get
) and create objects within that bucket (storage.objects.create
).
This can be done using the following instructions, which will walk you through creating a role and service account that will generate a private key to use in your Currents integration.
Create a new role in your Google Cloud Platform Console by navigating to IAM & admin > Roles > + Create Role.
![][2]
Next, give the role a name, click +Add Permissions and add storage.buckets.get
and storage.objects.create
, and click Create.
Optionally, add storage.objects.delete
permissions to allow Braze to clean up incomplete files. In rare circumstances, Google Cloud may terminate connections early, resulting in Braze writing incomplete files to Google Cloud Storage. Under normal circumstances, Braze will retry and create a new file with the correct data, leaving the old file in Google Cloud Storage.
![][3]
Create a new service account in your Google Cloud Platform Console by navigating to IAM & admin > Service Accounts and selecting Create Service Account.
![][4]
Next, give the service account a name and grant it access to your newly created custom role.
![In the Google Cloud Platform, on the create services page, type the name of your role in the "Select a Role" field.][5]
At the bottom of the page, use the Create Key button to create a JSON private key to use in Braze. After the key is created, it will download onto your machine.
![][6]
In Braze, navigate to Currents > + Create Current > Google Cloud Storage Data Export and provide your integration name and contact email.
Next, upload your JSON private key under GCS JSON Credentials and provide your CGS bucket name and GCS prefix (optional).
{% alert important %} It's important to keep your credentials file up to date; if your connector's credentials expire, the connector will stop sending events. If this persists for more than 48 hours, the connector's events will be dropped, and data will be permanently lost. {% endalert %}
![The Google Cloud Storage Currents page in Braze. On this page exist fields for integration name, contact email, GCS JSON credential, GCS bucket name, and prefix.][7]
Finally, scroll to the bottom of the page and select which message engagement events or customer behavior events you would like to export. When completed, launch your Current.
To set up Google Cloud Storage (GCS) exports, go to Technology Partners > Google Cloud Storage, enter your GCS credentials, and select Make this the default data export destination.
{% alert tip %} Your GCS JSON Credentials are generated by following the steps in the Google Cloud documentation. Make sure to input the entire JSON value that is generated. {% endalert %}
![The Google Cloud Storage page in the Braze dashboard.][8]{: style="max-width:70%;"}
Your corresponding Google Cloud IAM service account must have the following permissions (this can be confirmed by selecting the Test Credentials button on the Google Cloud Storage page in Braze):
storage.objects.create
storage.objects.delete
storage.objects.get
storage.objects.list
The organization and contents of any exported files will be identical across AWS S3, Microsoft Azure, and Google Cloud Storage integrations.
Users that have integrated a cloud data storage solution, and are trying to export APIs, dashboard reports, or CSV reports will experience the following:
- All API exports will not return a download URL in the response body and must be retrieved through data storage.
- All dashboard reports and CSV reports will be sent to the users email for download (no storage permissions required) and backed up on Data Storage.
[2]: {% image_buster /assets/img/gcs1.png %} [3]: {% image_buster /assets/img/gcs2.png %} [4]: {% image_buster /assets/img/gcs3.png %} [5]: {% image_buster /assets/img/gcs4.png %} [6]: {% image_buster /assets/img/gcs5.png %} [7]: {% image_buster /assets/img/gcs6.png %} [8]: {% image_buster /assets/img/gcs7.png %}