Hevo-generated Metadata

Last updated on May 30, 2023
On This Page

In the process of ingesting Events from a database Source or a SaaS Source and uploading them to the Destination, Hevo may add metadata columns to the Destination tables. This depends on the options you specify during Pipeline creation for the ingestion and uploading of the data, and on the nature of the Destination system itself. Some of these columns are transient, while some are permanent.

The following table describes the metadata columns that Hevo generates:

Metadata Column Description
__hevo_id A field added to Events in Sources which do not provide any primary key by default to load unique Events to the Destination.
Read __hevo_id.
__hevo_database_name A field used to identify the database from which a particular row in the Destination originated, when data is being loaded from multiple databases.
Read __hevo_database_name.
__hevo_ingested_at A timestamp that helps to verify that the ingested Event is more current than what already exists in the Destination.
This field is not visible in the Schema Mapper.
Read Additions to the Destination Schema.
__hevo_loaded_at A timestamp that indicates when data was inserted, updated, or deleted (delete flag updated) in the Destination table.
This field is not visible in the Schema Mapper.
Read Additions to the Destination Schema.
__hevo__marked_deleted A column that logically represents a deleted Event.
This field is not visible in the Schema Mapper.
Read Additions to the Destination Schema.
__hevo_source_modified_at A timestamp that indicates when the Event was created, updated, or deleted in the Source.
This field is not visible in the Schema Mapper.
Read __hevo_source_modified_at.
is_row_deleted A column that logically represents a deleted Event in a Stripe Source.
This field is visible in the Schema Mapper.
Read Additions to the Destination Schema.
deleted_timestamp A timestamp that indicates when the Event was deleted in a Stripe Source.
This field is visible in the Schema Mapper.
Read Additions to the Destination Schema.


Revision History

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

Date Release Description of Change
Apr-11-2022 NA - Updated the table to include the two metadata columns that Hevo generates to handle deletes in a Stripe Source.
May-05-2021 1.62 Updated the table to include a row for the Hevo-specific metadata column __hevo_source_modified_at.
Was this page helpful?

Tell us what went wrong