Google Sheets
The Google Sheets Destination is configured to push data to a single Google Sheets spreadsheet with multiple Worksheets as streams. To replicate data to multiple spreadsheets, you can create multiple instances of the Google Sheets Destination in your HeroPixelinstance.
Google Sheets imposes rate limits and hard limits on the amount of data it can receive, which results in sync failure. Only use Google Sheets as a destination for small, non-production use cases, as it is not designed for handling large-scale data operations.
Read more about the limitations of using Google Sheets below.
Prerequisites
- Google Account
- Google Spreadsheet URL
Step 1: Set up Google Sheets
Google Account
To create a Google account, visit Google and create a Google Account.
Google Sheets (Google Spreadsheets)
- Once you are logged into your Google account, create a new Google Sheet. Follow this guide to create a new sheet. You may use an existing Google Sheet.
- You will need the link of the Google Sheet you'd like to sync. To get it, click "Share" in the top right corner of the Google Sheets interface, and then click Copy Link in the dialog that pops up.
Step 2: Set up the Google Sheets destination connector in HeroPixel
Authentication to Google Sheets is only available using OAuth for authentication.
- Create a new Google Cloud project.
- Enable the Google Sheets API.
-
Create a new
OAuth client ID. Select
Web application
as the Application type, give it aname
and addhttps://developers.google.com/oauthplayground
as an Authorized redirect URI. -
Add a
Client Secret
(Add secret), and take note of both theClient Secret
andClient ID
. - Go to Google OAuth Playground
-
Click the cog in the top-right corner, select
Use your own OAuth credentials
and enter theOAuth Client ID
andOAuth Client secret
from the previous step. -
In the left sidebar, find and select
Google Sheets API v4
, then choose thehttps://www.googleapis.com/auth/spreadsheets
scope. ClickAuthorize APIs
. -
In step 2, click
Exchange authorization code for tokens
. Take note of theRefresh token
. -
Set up a new destination in HeroPixel select
Google Sheets
and enter theClient ID
,Client Secret
,Refresh Token
andSpreadsheet Link
from the previous steps.
Output schema
Each worksheet in the selected spreadsheet will be the output as a separate source-connector stream.
The output columns are re-ordered in alphabetical order. The output columns should not be reordered manually after the sync, as this could cause future syncs to fail.
All data is coerced to a string
format
in Google Sheets. Any nested lists and objects will
be formatted as a string rather than normal lists
and objects. Further data processing is required if
you require the data for downstream analysis.
HeroPixelonly supports replicating
Grid Sheets
, which means only text is
replicated. Objects like charts or images cannot be
synced. See the
Google Sheets API docs
for more info on all available sheet types.
Rate Limiting & Performance Considerations
The Google API rate limit is 60 requests per 60 seconds per user and 300 requests per 60 seconds per project, which will result in slow sync speeds. HeroPixelbatches requests to the API in order to efficiently pull data and respects these rate limits.
Limitations
Google Sheets imposes hard limits on the amount of data that can be synced. If you attempt to sync more data than is allowed, the sync will fail.
Maximum of 10 Million Cells
A Google Sheets document can contain a maximum of 10 million cells. These can be in a single worksheet or in multiple sheets. If you already have reached the 10 million limit, it will not allow you to add more columns (and vice versa, i.e., if the 10 million cells limit is reached with a certain number of rows, it will not allow more rows).
Maximum of 50,000 characters per cell
There can be at most 50,000 characters per cell. Do not use Google Sheets if you have fields with long text in your source.
Maximum of 18,278 Columns
There can be at most 18,278 columns in Google Sheets in a worksheet.
Maximum of 200 Worksheets in a Spreadsheet
You cannot create more than 200 worksheets within single spreadsheet.
Syncs will fail if any of these limits are reached.
Note:
- The underlying process of record normalization is applied to avoid data corruption during the write process. This handles two scenarios:
- UnderSetting - when record has less keys (columns) than catalog declares
- OverSetting - when record has more keys (columns) than catalog declares
EXAMPLE:
- UnderSetting:
* Catalog:
- has 3 entities:
[ 'id', 'key1', 'key2' ]
^
* Input record:
- missing 1 entity, compare to catalog
{ 'id': 123, 'key2': 'value' }
^
* Result:
- 'key1' has been added to the record, because it was declared in catalog, to keep the data structure.
{'id': 123, 'key1': '', {'key2': 'value'} }
^
- OverSetting:
* Catalog:
- has 3 entities:
[ 'id', 'key1', 'key2', ]
^
* Input record:
- doesn't have entity 'key1'
- has 1 more enitity, compare to catalog 'key3'
{ 'id': 123, ,'key2': 'value', 'key3': 'value' }
^ ^
* Result:
- 'key1' was added, because it expected be the part of the record, to keep the data structure
- 'key3' was dropped, because it was not declared in catalog, to keep the data structure
{ 'id': 123, 'key1': '', 'key2': 'value', }
^ ^
Data type mapping
Integration Type | HeroPixelType |
---|---|
Any Type |
string
|
Features & Supported sync modes
Feature | Supported?(Yes/No) |
---|---|
Ful-Refresh Overwrite | Yes |
Ful-Refresh Append | Yes |
Incremental Append | Yes |
Incremental Append-Deduplicate | Yes |