Models and Destination Objects
This page is the authoritative reference for models and destination objects in reverse ETL integrations.
Model
- Definition: The model is the dataset that is synced to the destination. It is defined by SQL that runs against your connected warehouse. The query result — columns and rows — is what Matia sends to the destination. Column names and types should align with destination field expectations; use SQL to filter, join, aggregate, or cast as needed.
- Where: Model SQL is set in the integration Configure step (at creation) or in Settings → Model configuration. You can preview the model to see sample rows and edit the SQL at any time. Changing the SQL changes the data set for the next sync.
- Primary key: You must select a primary key in the source (a column from the model result) that uniquely identifies each row. This is used with the destination primary key to match rows for updates and deletes (Mirror, Upsert).
- Field mapping: Model columns are mapped to destination fields. Auto-mapping suggests mappings from semantic naming; you can add or edit mappings manually. See Configure field mapping.
Destination Object
- Definition: The destination object is the entity in the destination that receives the synced rows — e.g. Contact, Company, or a custom object in HubSpot. You select one destination object per integration when configuring the integration.
- Where: Set in the Configure step or in Settings. The list of available objects depends on the destination connector (e.g. HubSpot Contact, Company, custom object).
- Behavior: All rows from the model are mapped to fields on this object. Primary key in the destination must be set so Matia can match records for upsert or delete. Destination API limits and validation rules apply; rejected records show the API response for debugging.
Test
Use Test in Settings to push one random record from the model to the destination. Matia shows which record was sent so you can confirm mapping and destination behavior before running a full sync.
For sync modes and destination support, see Sync modes and destinations. For how records are classified, see How reverse ETL works.