Google Cloud Storage connector
Adobe Experience Platform provides native connectivity for cloud providers like AWS, Google Cloud Platform, and Azure, allowing you to bring your data from these systems.
Cloud storage sources can bring your own data into Platform without the need to download, format, or upload. Ingested data can be formatted as XDM JSON, XDM parquet, or delimited. Every step of the process is integrated into the Sources workflow. Platform allows you to bring in data from Google Cloud Storage through batches.
IP address allow list
The following IP addresses must be added to an allow list prior to working with source connectors. Failing to add your region-specific IP addresses to your allow list may lead to errors or non-performance when using sources.
East US region
West Europe region
Prerequisite setup for connecting your Google Cloud Storage account
In order to connect to Platform, 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 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 user account. If you have not already established a default project for interoperable access, you can set one up from within the Default project for interoperable access section. If a default project has already been established, the section will show a confirmation that a project has been set as default.
To generate a new access key ID and a secret access key for your user account, select Create a Key .
You can use your newly generated access key ID and secret access key to connect your Google Cloud Storage account to Platform.
Naming constraints for files and directories
The following is a list of constraints you must account for when naming your cloud storage file or directory.
- Directory and file component names cannot exceed 255 characters.
- Directory and file names cannot end with a forward slash ( / ). If provided, it will be automatically removed.
- The following reserved URL characters must be properly escaped: ! * ' ( ) ; : @ & = + $ , / ? % # [ ]
- The following characters are not allowed: " \ / : | < > * ? .
- Illegal URL path characters not allowed. Code points like \uE000 , while valid in NTFS filenames, are not valid Unicode characters. In addition, some ASCII or Unicode characters, like control characters (0x00 to 0x1F, \u0081, etc.), are also not allowed. For rules governing Unicode strings in HTTP/1.1 see RFC 2616, Section 2.2: Basic Rules and RFC 3987 .
- The following file names are not allowed: LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, PRN, AUX, NUL, CON, CLOCK$, dot character (.), and two dot characters (..).
Connect Google Cloud Storage to Platform
The documentation below provides information on how to connect Google Cloud Storage to Platform using APIs or the user interface: