Send your event data from RudderStack to Google Sheets.
Google Sheets is a popular spreadsheet program that is bundled as a part of the free, cloud-based office suite offered by Google. With Google Sheets you can seamlessly create spreadsheets that update and save automatically and are easy to access from your Google Drive.
RudderStack allows you to configure Google Sheets as a destination and send your event data to it directly.
Find the open source transformer code for this destination in the GitHub repository.
Getting started
To enable sending data to Google Sheets, you will first need to add it as a destination to the source from which you are sending your event data. Once the destination is enabled, events from RudderStack will start flowing to Google Sheets.
Connection Mode
Web
Mobile
Server
Device mode
-
-
-
Cloud mode
Supported
Supported
Supported
To learn more about the difference between cloud mode and device mode in RudderStack, refer to the RudderStack Connection Modes guide.
Once you have confirmed that the platform supports sending events to Google Sheets, perform the steps below:
From your RudderStack dashboard, add the source. From the list of destinations, select Google Sheets.
Assign a name to the destination and click Next. You should then see the following screen:
Google Sheets Connection Settings
Obtaining the Credentials
Before you add Google Sheets as a destination in RudderStack, follow these steps to get the Google Cloud Service Account credentials required for the configuration:
Create a service account in from your Google Cloud Console account, as shown below:
A JSON file with the required credentials will be generated against this service account:
Once you have completed the connection, make sure you have enabled Google-Sheets-API in the project of your service account.
Then, enter the following details under Connection Settings in the RudderStack dashboard.
Credentials: Paste the downloaded JSON in the Credentials field in the RudderStack dashboard.
Sheet ID: Add the Google Sheet ID to which you want to send your event data. You will also need to assign Editor privileges to the email address of the service account for that specific Google Sheet.
Sheet Name: Add the Sheet Name to which you want to send your data. You can find the sheet name at the bottom left corner the spreadsheet as shown below:
The Sheet Name is case-sensitive and has to be exactly as seen in Google Sheets.
Next, enter the Event Properties corresponding to Column Name under the Map Event to Google Sheets section.
NOTE: For mapping attributes from traits or properties,
you can directly enter the attribute name (for e.g. productName,
firstName, or address.city) and map it to desired Column. For other
contextual attributes, you will need to enter the absolute path to the
attribute using dot notation. (for e.g. context.app.build)
If you have Nested Attributes inside properties or traits, please use the dot notation for mapping to respective Column (For e.g.: address.zip, address.city..)
For mapping attributes from event properties or traits/context.traits, RudderStack also supports absolute mapping. For example: adding context.traits.firstName will map the same value as adding firstName.
NOTE: We advise you to map with absolute path as it resolves
the ambiguity when you have same attribute name in traits, context.traits
or properties.
Finally, click Next to complete the configuration.
Google Sheets should now be added and enabled as a destination in RudderStack.
Page
The page call contains information related to the page, such as the URL of the web page visited by the user.
A sample page payload is as shown in the snippet below:
The screen method allows you to record whenever a user sees the mobile screen along with any associated optional properties. This call is similar to the page call but is exclusive to your mobile device.
A sample screen call looks like the following code snippet:
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.