Reltio Private Previewlink
Reltio is a cloud-native master data management (MDM) platform.
Featureslink
Feature Name | Supported | Notes |
---|---|---|
Capture deletes | check | ENTITY , ENTITY_ANALYTICS_ATTRIBUTE_TYPE , ENTITY_ATTRIBUTE_TYPE , ENTITY_TYPE , INTERACTION_ATTRIBUTE_TYPE , INTERACTION_MEMBER_TYPE , INTERACTION_TYPE , MATCH , MATCH_GROUP , RELATION , RELATION_ATTRIBUTE_TYPE , RELATION_TYPE , and SOURCE tables. |
History mode | ||
Custom data | check | ENTITY , INTERACTION , MATCH , and RELATION tables. |
Data blocking | check | Column level |
Column hashing | check | |
Re-sync | check | Connector level |
API configurable | check | API configuration |
Priority-first sync | check | ENTITY , INTERACTION , MATCH , and RELATION tables. |
Fivetran data models | ||
Private networking |
Setup guidelink
Follow our step-by-step Reltio setup guide to connect Reltio with your destination using Fivetran connectors.
Sync overviewlink
To capture new records and updates, we incrementally sync the following tables and their child tables:
ENTITY
INTERACTION
MATCH
RELATIONSHIP
We also re-import the following tables during every sync:
ENTITY_ANALYTICS_ATTRIBUTE_TYPE
ENTITY_ATTRIBUTE_TYPE
ENTITY_TYPE
INTERACTION_ATTRIBUTE_TYPE
INTERACTION_MEMBER_TYPE
INTERACTION_TYPE
MATCH_GROUP
RELATION_ATTRIBUTE_TYPE
RELATION_TYPE
SOURCE
Syncing attributeslink
We sync the nested sub-attributes as individual rows in the attribute tables (ENTITY_ATTRIBUTE
, ENTITY_ANALYTICS_ATTRIBUTE
, INTERACTION_ATTRIBUTE
, RELATION_ANALYTICS_ATTRIBUTE
, and RELATION_ATTRIBUTE
).
Examplelink
In the following example, Country
and Zip
are two attributes of the Location
type entity. Country
is a simple attribute, whereas Zip
is a nested attribute.
{
"attributes": {
"Country": [
{
"type": "configuration/entityTypes/Location/attributes/Country",
"ov": true,
"value": "United States of America",
},
{
"type": "configuration/entityTypes/Location/attributes/Country",
"ov": false,
"value": "USA",
}
],
"Zip": [
{
"value": {
"PostalCode": [
{
"type": "configuration/entityTypes/Location/attributes/Zip/attributes/PostalCode",
"ov": true,
"value": "12345",
"uri": "entities/fivetran_entity/attributes/Zip/ccc/PostalCode/dddd"
}
],
},
"ov": true,
}
]
}
}
The rows corresponding to these attributes in the ENTITY_ATTRIBUTE
table are as follows:
_fivetran_id | entity_id | parent_attribute | name | value | ov | other columns |
---|---|---|---|---|---|---|
id1 | fivetran_entity | Country | United States of America | TRUE | ... | |
id2 | fivetran_entity | Country | USA | FALSE | ... | |
id3 | fivetran_entity | Zip | TRUE | ... | ||
id4 | fivetran_entity | id3 | Zip.PostalCode | 12345 | TRUE | ... |
NOTE: We do not sync sub-attributes of reference attributes. This is because sub-attributes are denormalised data and are present in the attributes of the referenced entities or relations.
Syncing entity merges and unmergeslink
When an entity is merged in Reltio, we do the following in your destination:
- Soft delete the merged entity in the
ENTITY
table (set the_fivetran_deleted
column toTRUE
). - Update the winner of the merge in the
winner_id
column of the merged entity. - Sync the merge operation details into the
ENTITY_MERGE
table.
When an entity is unmerged in Reltio, we do the following in your destination:
- Mark the unmerged entity as active (set the
_fivetran_deleted
column toFALSE
). - Clear the
winner_id
column of the unmerged entity. - Delete the information of the previously merged entity from the
ENTITY_MERGE
table.
Schema informationlink
This schema applies to all Reltio connectors created on or after June 19, 2024.
To zoom, open the ERD in a new window.This schema applies to all Reltio connectors created before June 19, 2024.
To zoom, open the ERD in a new window.Limitationslink
We perform only incremental syncs for the NOT_MATCH
table because the Activity Log API that we use to sync this table has a limited retention.