Reltio Beta

Reltio is a cloud-native master data management (MDM) platform.

Features

Setup guide

Follow our step-by-step Reltio setup guide to connect Reltio with your destination using Fivetran connectors.

Sync overview

To capture new records and updates, we incrementally sync the following tables and their child tables:

• ENTITY
• INTERACTION
• MATCH
• RELATION

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

Export limit

To avoid affecting other Reltio workloads, we reschedule the sync if there are more than 10 active export tasks running, outside of the connector sync.

We spawn a maximum of 4 export tasks at a time.

Syncing attributes

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).

Example

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:

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 unmerges

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 to TRUE).
• 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 to FALSE).
• Clear the winner_id column of the unmerged entity.
• Delete the information of the previously merged entity from the ENTITY_MERGE table.

Schema information

This schema applies to all Reltio connectors created on or after June 19, 2024.

Limitations

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.