How is new data from Google Sheets updated in the Destination?

For any update in the Google Sheets Source, Hevo fetches the entire sheet and loads it to the Destination. This is done because the Google Sheets API does not provide information as to which records got updated or inserted. Therefore, Hevo cannot fetch just the new or changed records. The only available information is the last_modified_at timestamp of the sheet, resulting in a timestamp-based offset applicable at the sheet level. If any changes are detected via this offset, then the entire sheet is ingested again.

Further, as Google Sheets does not have the concept of a primary key, Hevo creates the metadata field, __hevo_id, to use as a primary key for de-duplicating the records in the Destination table.

Read more about the Hevo metadata field __hevo_id.


Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Nov-07-2022 NA Created as a new document.
Last updated on 03 Nov 2022

Tell us what went wrong