Hevo-generated Metadata (Edge)

Last updated on Mar 25, 2026
On This Page

Edge Pipeline is now available for Public Review. You can explore and evaluate its features and share your feedback.

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__ingested_at A timestamp that helps to verify that the ingested Event is more current than what already exists in the Destination.
__hevo_op_type This field indicates the type of change for each record in the Source. It helps determine how the data should be processed in the Destination.

For each record, this field can have one of the following values:

- Insert (I): The record was newly added in the Source.
- Update (U): The record was modified in the Source.
- Delete (D): The record was deleted from the Source.
- Read (R): The record was ingested during the historical load from the Source.
__hevo__source_modified_at A timestamp that indicates when the Event was created, updated, or deleted in the Source.
__hevo__marked_deleted A column that logically represents a deleted Event.
__hevo__loaded_at A timestamp that indicates when data was inserted, updated, or deleted (delete flag updated) in the Destination table.

Revision History

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

Date Release Description of Change
Mar-25-2026 NA Updated the __hevo_op_type description to clarify the type of change for each Souce record.
Was this page helpful?

Tell us what went wrong