This destination is currently in Beta and is only available to a limited number of customers. To request access to the Google Cloud Storage connection, contact your Adobe representative and provide your Organization ID.
Create a live outbound connection to Google Cloud Storage to periodically export data files from Adobe Experience Platform into your own buckets.
Refer to the table below for information about the destination export type and frequency.
|Export type||Profile-based||You are exporting all members of a segment, together with the applicable schema fields, as chosen in the select profile attributes screen of the destination activation workflow.|
|Export frequency||Batch||Batch destinations export files to downstream platforms in increments of three, six, eight, twelve, or twenty-four hours. Read more about batch file-based destinations.|
In order to connect Platform to Google Cloud Storage, you must first enable interoperability for your Google Cloud Storage account. To access the interoperability setting, open Google Cloud Platform and select Settings from the Cloud Storage option in the navigation panel.
The Settings page appears. From here, you can see information regarding your Google project ID and details about your Google Cloud Storage account. To access interoperability settings, select Interoperability from the top header.
The Interoperability page contains information on authentication, access keys, and the default project associated with your service account. To generate a new access key ID and a secret access key for your service account, select Create a Key for a Service Account.
You can use your newly generated access key ID and secret access key to connect your Google Cloud Storage account to Platform.
To connect to this destination, follow the steps described in the destination configuration tutorial. In the destination configuration workflow, fill in the fields listed in the two sections below.
To authenticate to the destination, fill in the required fields and select Connect to destination.
Access key ID: A 61-character, alphanumeric string used to authenticate your Google Cloud Storage account to Platform. For information on how to obtain this value, read the prerequisites section above.
Secret access key: A 40-character, base64-encoded string used to authenticate your Google Cloud Storage account to Platform. For information on how to obtain this value, read the prerequisites section above.
Encryption key: Optionally, you can attach your RSA-formatted public key to add encryption to your exported files. View an example of a correctly formatted encryption key in the image below.
For more information about these values, read the Google Cloud Storage HMAC keys guide. For steps on how to generate your own access key ID and secret access key, refer to the Google Cloud Storage source overview.
To configure details for the destination, fill in the required and optional fields below. An asterisk next to a field in the UI indicates that the field is required.
You can enable alerts to receive notifications on the status of the dataflow to your destination. Select an alert from the list to subscribe to receive notifications on the status of your dataflow. For more information on alerts, see the guide on subscribing to destinations alerts using the UI.
When you are finished providing details for your destination connection, select Next.
See Activate audience data to batch profile export destinations for instructions on activating audience segments to this destination.
In the Mapping step, you can select which attribute and identity fields to export for your profiles. You can also select to change the headers in the exported file to any friendly name that you wish. For more information, view the mapping step in the activate batch destinations UI tutorial.
This destination supports dataset exports. For complete information on how to set up dataset exports, read the export datasets tutorial.
To verify if data has been exported successfully, check your Google Cloud Storage bucket and make sure that the exported files contain the expected profile populations.