Google Sheets Destination

The Google Sheets destination allows you to sync your warehouse data to a Google spreadsheet, and update the spreadsheet automatically as your data changes. This destination automates the workflow of exporting CSVs from your warehouse.

The Google Sheets destination can be connected to Reverse ETL warehouse sources only.

Getting started

Create a spreadsheet

1. Create a new Google spreadsheet in your Google account.
2. Copy the spreadsheet ID from the spreadsheet URL. The spreadsheet ID is the value after d/ and before /edit. For example, if your URL is https://docs.google.com/spreadsheets/d/1ejq5-UVP0SWZezRsdggzFxMqOmaJwZh7NkKPkQfi0Bb/edit#gid=0 the ID is 1ejq5-UVP0SWZezRsdggzFxMqOmaJwZh7NkKPkQfi0Bb. You will need this ID when you configure the destination.

Connect Google Sheets

1. Create and configure your Reverse ETL source.
2. Create a model for the data you plan to sync to Google Sheets.
3. Navigate to the Reverse ETL > Destinations tab and click Add Destination.
4. Select Google Sheets and click Next. Select the source you configured and name the destination.
5. On the Settings tab, authenticate the Google Sheets API using OAuth. Select the email account that owns the spreadsheet you created above. Make sure you enable the See, edit, create, and delete all your Google Sheets spreadsheets permission.
6. On the Mappings tab, click Add Mapping and create a Post Sheet mapping. Within the mapping, configure how warehouse records should map to your Google Sheets spreadsheet.
7. Enable the destination and configured mappings.

Actions v2

Segment’s v2 Action, Post Sheet v2, supports Sync modes, which allow you to select a strategy for updating your data in Google Sheets.

Sync modes

Sync modes allow users to define how Segment updates the data in your destination.

Available sync modes for the Post Sheet v2 Action includes:

• Update: Update a record if a match with the specified identifier is found. Segment does nothing if the row doesn’t exist.
• Upsert: If a record with the specified identifier is found, it is updated. If not, a new row is created.
• Add: Add a new record when the specified identifier doesn’t exist. If it does, the record is skipped.

Available Actions

Build your own Mappings. Combine supported triggers with the following Google Sheets-supported actions:

• Post Sheet

• Post Sheet V2

Post Sheet

Write values to a Google Sheets spreadsheet.

Post Sheet is a Cloud action. The default Trigger is: event = "updated" or event = "new"

Click to show / hide fields

Post Sheet V2

Write values to a Google Sheets spreadsheet.

Post Sheet V2 is a Cloud action. The default Trigger is: event = "updated" or event = "new"

Click to show / hide fields

FAQ

How does Segment know if a row should be added or updated?

The Record Identifier mapping is used to make a distinction between adding a new row or updating an existing row. If two rows have the same Record Identifier, they are considered to be pertaining the same object and will live in the same row. Please ensure Record Identifier is set to a unique field.

How do I define the columns in my spreadsheet?

The Fields mapping controls which fields in your model will be written as columns. Input the desired column name(s) on the right, and select the data variable that will populate the value for that column on the left. Please note, at least one field must be configured to send data to Google Sheets or no columns will be created or synced.

How are columns formatted when synced to my spreadsheet?

When syncing data to Google Sheets, the columns will be arranged alphabetically, based on the names defined in the Fields mapping.

Can I add or remove columns after data has been synced?

Once data has been synced to Google Sheets, any subsequent addition or removal of columns in the RETL Model and/or Mapping may lead to misalignment of existing data, as Segment does not retroactively adjust previously synced data. For updates involving column modifications, Segment recommends starting with a new Sheet to ensure data integrity.