Who can use this feature?
- All roles with access level "high"
- Available on all plans
A Google Cloud Storage (GCS) integration allows you to bring in additional data into Catalyst to enrich your account, opportunity, contact, and additional objects. The most common use case for GCS is to import KPIs via CSV that are not already part of your Salesforce instance.
Connect your GCS account
Connect your GCS and Catalyst accounts using an application service key (service account). Catalyst encrypts authorization credentials with AES-256 at multiple levels (with option to enable SSH).
- In your Google Cloud account, create a service account key using one of the methods described here. Be sure to include the following permissions when granting access to the service account:
-
storage.buckets.list
-
storage.buckets.get
-
- After setting up a service account with access to the GCS bucket holding your data, generate a service account key in the form of a JSON text file.
- In Catalyst, navigate to Settings > Integrations.
- Locate Google Cloud Storage from the list of inactive integrations, click + Add.
- Enter the application service key (JSON).
- Click Connect.
Once connected, add your data source (see below).
Although it is optional, we recommend adding Catalyst IP addresses to your allowlist: 3.95.50.240 | 34.206.178.38 | 34.192.22.163
Add a GCS data source in Catalyst
Once connected, you can add a CSV file from GCS as a Catalyst data source.
- The CSV file(s) should contain a column for each KPI you want to track, along with the Salesforce ID for each record.
- You should have one CSV file for each object you have data for: accounts.csv, opportunities.csv, and contacts.csv. You don't need to provide all three files. For example, if you only have KPIs for one or two of those objects, the integration can ignore the others.
- Save the CSV file(s) at the root of the bucket. Whenever you upload new data, overwrite the old CSV file(s).
- From within the Google Cloud Storage integration in Catalyst (see above), click + Add Source.
- Enter the details for the data source (see below).
- Click Save.
You can now add a new Catalyst data warehouse field that syncs to the field in your GCS data source.
Data Warehouse integrations update every 6 hours, 4 times a day. You can map Catalyst fields immediately after adding a data source, but fields will not populate with data until after the next sync.
Data source details
- Source nickname: Unique name to identify the source in Catalyst.
- Catalyst object: Choose the object you're mapping to in Catalyst.
-
Data path: Map the data path you're connecting Catalyst to in your GCS warehouse:
- Enter the bucket name
- Enter the CSV name. If the CSV is in a folder, enter
[folder name]/[csv name]
-
Matching strategy: Choose the identifier to use to match your data to your records:
- Salesforce Field ID: Highly recommended. It's best to use an 18-digit SFDC ID when setting up your tables; however, both 15 and 18-digit IDs work.
- Select a field: Choose any supported field that exists in Catalyst for the selected object (e.g., text, number, Boolean, ISO 8601 formatted dates)
- Matching column name: Choose the column in your table that is your identifier.
-
Table structure: Specify how your table is structured (unique or multiple rows).
-
Current snapshot of Salesforce Object ID: Choose this option if the table you're using already has a unique row per Salesforce Object ID record.
-
Latest entry per Salesforce Object ID using timestamp: Choose this option if the table you're using contains multiple rows for a single unique Salesforce Object ID record. Select a timestamp field from the drop-down to indicate the most recently updated record for each Salesforce Object ID; allows Catalyst to reflect the most accurate value at the end of each day.
Performing this operation in your data warehouse could have cost implications, depending on your pricing structure.
-
Current snapshot of Salesforce Object ID: Choose this option if the table you're using already has a unique row per Salesforce Object ID record.