Data Synchronization Identifiers

An Activation uses identifiers to synchronize data from the Activate Warehouse with objects in the Target CRM application. These are fields or properties that contain detailed metadata for the Target objects. They help identify the data records to be replicated. You can either use a unique identifier, a composite identifier, or a matching identifier.

  • Unique Identifier: A unique identifier is a property similar to a primary key in relational databases. It helps to uniquely identify records in the Target object with which data from the Warehouse is synchronized.

    For example, in the Salesforce object, Account, the field, AccountId is a unique identifier for each record in the object.

  • Composite Identifier: A composite identifier consists of two or more properties, similar to a candidate key in relational databases. It helps to uniquely identify records in the Target object with which data from the Warehouse is synchronized.

    For example, in the Marketo object, Opportunity Role, the fields, externalOpportunityId, leadId, and role together form a composite identifier for each record in the object.

  • Matching Identifier: A matching identifier is a property that helps identify the data to be synchronized in the Target. It can be a unique or a non-unique property. If you select a unique property as a matching identifier, then its behavior is similar to that of a unique identifier. If you select a non-unique property as a matching identifier, all records in the Target object that match the property‚Äôs value are updated.

    For example, in the HubSpot object, contacts, the field, City can hold multiple values, such as San Francisco or Los Angeles. Now, if you select City as a matching identifier, then all the records in the Target object that match any of these values are updated. Therefore, City is a non-unique property.

Note: You cannot change the selected data synchronization identifier once you create the Activation.

Limitations

  • You cannot change the identifier once you create the Activation.

Revision History

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

Date Release Description of Change
Mar-07-2022 1.83 - Added information on composite identifiers.
- Updated the section, Limitations to remove the limitation of single field as an identifier.
Dec-20-2021 NA Updated the content for clarity and additional details.
Oct-25-2021 NA Added the Limitations section.
Oct-04-2021 1.73 New document.
Last updated on 27 Jun 2022

Tell us what went wrong