Synchronize Customer Profile Attributes

Overview

In this destination service, DinMo will update attributes for existing customer profiles in Talon.One, creating or mapping fields as specified.

To do so, you will need to go through these three steps:

• Creating a Talon.One destination. Refer to the corresponding section for more info.

• Creating a user segment composed of all the users that need to be updated. Refer to this step-by-step tutorial to learn how to build segments without SQL in DinMo.

• Activating the segment to the Talon.One destination to start sending data.

Each time the activation will be running:

• If you ticked the insert mode option, all new users in the model will be inserted as a user in Talon.One (UPSERT)

• All attributes values that have changed since the last activation will be updated in Talon.One

Note that if you chose not to insert new users, only users of the model who have an external id linked to an existing Talon.One user will be updated (UPDATE).

Destination Setup

To start synchronizing contacts, you are first required to create a Talon.One destination with the corresponding destination service.

Activation configuration

Once the destination has been setup, and your DinMo segment created, you can create an activation to start sending data to Talon.One right away. All people in the segment will be updated with their most up-to-date attributes.

Fields mapping

In the Fields mapping section, you are asked to specify the field contained in your DinMo segment that Talon.One will use to link each segment's records to a Talon.One contact (Custom Profile ID).

You can also map other standard attributes in Talon.One, that you've already created there.

Custom Attributes

In this section, any field you select will be exported as a new custom attribute in Talon.One. The associated field will have the same name in Talon.One and DinMo.

These values of the attributes selected here will then be updated at each activation.

Scheduling

In this section, specify how often the users should be updated in Talon.One. Every time the activation runs:

• All attributes values that have changed since the last activation will be updated in Talon.One

• ⚠️ If a is no longer in the segment, the attributes are no longer updated.