Send your event data from RudderStack to Google Sheets.
4 minute read
Google Sheets is a popular spreadsheet program. You can seamlessly create spreadsheets that update and save automatically and are easy to access from your Google Drive.
Find the open source transformer code for this destination in the GitHub repository.
Once you have confirmed that the source platform supports sending events to Google Sheets, follow these steps:
From your RudderStack dashboard, add a source. Then, from the list of destinations, select Google Sheets.
Assign a name to the destination and click Continue.
Service account permissions
To add Google Sheets as a destination in RudderStack, you must first obtain the Google Cloud service account credentials required for the configuration. Follow these steps:
Enter the service account details and click CREATE AND CONTINUE.
Under Grant this service account access to project, select the Editor role:
Click DONE to finish the service account configuration. The service account is now created.
Under the KEYS tab, click ADD KEY > Create new key.
Choose JSON as the key type and click CREATE.
The private key JSON will be downloaded and saved to your computer automatically. Use this JSON to set up your Google Sheets destination in RudderStack.
Before setting up the destination in RudderStack, make sure you enable the Google Sheets API for your project.
Connection settings
To successfully configure Google Sheets as a destination, you will need to configure the following settings:
Credentials: Enter the contents of the credentials JSON obtained in the Service account permissions section above.
Sheet ID: Enter your Google Sheet ID present in the spreadsheet’s URL. For example, if the URL is https://docs.google.com/spreadsheets/d/aBC-123_xYz/edit#gid=920137070, then the sheet ID is 920137070.
Sheet Name: Enter the name of the spreadsheet to which you want to send the data. You can find the sheet name in the bottom left corner of the spreadsheet.
Map Event to Google Sheets: Use this setting to send an event property to a specific sheet’s column.
For mapping the traits or event properties, enter the trait/property name directly, for example, firstName, email, etc. However, it is highly recommended to provide the absolute path to avoid ambiguity when you have the same attribute name in your event’s traits, context.traits, or properties object.
For mapping contextual fields or nested attributes, you must enter the absolute path to the attribute using dot notation. For example, context.app.build, address.zip, etc.
The screen call lets you record whenever your user views their mobile screen, with any additional relevant information about the screen. This call is similar to the page call but is exclusive to your mobile device.
This site uses cookies to improve your experience while you navigate through the website. Out of
these
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
essential
for the working of basic functionalities of the website. We also use third-party cookies that
help
us
analyze and understand how you use this website. These cookies will be stored in your browser
only
with
your
consent. You also have the option to opt-out of these cookies. But opting out of some of these
cookies
may
have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
This site uses cookies to improve your experience. If you want to
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.