Synchronize Insight Data collections
Insight data is made up of collections of of structured data related to your customers’ purchasing histories, browsing habits, or product reviews.
Overview
In this destination service, DinMo will export records and update attributes for collections of data associated to your contacts. A collection can take a predefined structure, or custom collections can be created for more bespoke use cases.
To begin setup, you will need to go through these three steps:
Creating a Dotdigital destination. Refer to the corresponding section for more info.
Creating a segment or model composed of all the insight data records and attributes that will be inserted and updated in Dotdigital. Refer to this step-by-step tutorial to learn how to build segments without SQL in DinMo.
Activating the segment / model to the Dotdigital destination to start sending data.
Each time the activation is running:
All new insight data records will be added as part of the collection and attached to the relevant contact or account
All attribute values that have changed for a particular insight data record since the last activation will be updated in Dotdigital.
Custom (new) attributes not present in Dotdigital will be created upon the first synchronization and regularly updated afterward.
Note:
Insight data records will not be deleted from Dotdigital. If a record drops out of the segment / model you are using, the record will simply stop being updated.
Any Insight Data record shared in this activation MUST have an associated contact (and matching identifier) that already exists in Dotdigital.
Destination setup
To start exporting Insight data records, you are first required to create a Dotdigital destination with the corresponding destination service.
When selecting 'Synchronize Insight Data Records', you must choose a collection for the Insight data records to be associated to. Here you can choose:
Use existing collection
Create a new collection
It is not recommended to have more than one activation managing a single collection, therefore it is likely you will choose create new collection here.
Next you must choose the collection scope; whether the collection will be at the contact level or account level.
For new collections, you then have two options for collection types:
using one of the predefined collection types from the list, all containing a naming convention and predefined structure
or creating a custom collection which allows you to create a custom defined schema.
Note: the collections that you have access to can vary depending on the account type. Documentation can be found here for collection types.
Activation configuration
Once the destination has been setup, and your DinMo model or segment created, you can configure an activation to start sending data to Dotdigital right away.
Matching Identifier
Here you are asked to choose the matching identifier, which is the field used to match the Insight data records in your data warehouse to an existing contact in Dotdigital, and takes one of the following:
Contact ID (internal Dotdigital ID created upon creation of a contact in Dotdigital)
Email address
Phone number
Note: it is recommended that a consistent identifier is used across all Dotdigital activations within DinMo. If Contact ID exists in your data warehouse, this should be the identifier you chose.
Fields mapping
In the Fields mapping section, you are asked to specify the fields you would like to include as part of the Insight data collection activation. This should include all the attributes associated to your insight data record, which can be used in Dotdigital as part of the Insight data feature.
The following mappings are mandatory:
Record Key - this refers to the unique identifier associated to each of the individual Insight data records (such as a transaction ID, or other "child" ID).
Matching Identifier - this is the mapping for the matching identifier selected above, to allow Dotdigital to match each of the insight data records to a contact or account.
After this, you can add as many mappings as you like to include all necessary attributes associated to the insight data records.
Any new attributes that do not exist in Dotdigital can be added as new attributes to the schema in the next section. Note: any new attribute names must be lowercase, and only contain alphanumeric characters, hyphens, or underscores.
Any existing attributes that are removed from the mappings will also be removed from the Insight data records during the sync. Therefore, please ensure there are no dependencies on certain attributes before removing a mapping from an active sync.
Scheduling
In this section, specify how often the list should be updated in Dotdigital. Every time the list is updated:
Any new Insight data record having entered your DinMo model or segment since the last update will be added, if and only if this user is already an existing Dotdigital contact
Any new mapping added to the Insight data record activation, or any updated value for existing attributes, will be updated during the next activation run
Warnings
In this section, specify if you want to receive warnings for your Dotdigital activation.
Last updated