Unique Identifier is a powerful feature that allows marketers to synchronize their contacts between Maropost for Marketing and their own CRM, using a unique identifier other than email such as; member ID, account ID, customer ID, etc.
Marketers can also synchronize their contacts across different digital channels including email, SMS, and mobile app messaging.
Determining if Unique Identifier is Right For You
Maropost's data model requires that no two contacts can share the same email address nor can they share the same unique identifier. If your business rules have the same constraints, then you can use Unique Identifier.
How to Designate a Unique Identifier
The Unique Identifier (UID) is a custom field that you’ve specially designated as the unique identifier for your contact records.
In the main menu bar, mouse over your username and select 'Account Settings' from the drop down menu.
You’ll see the 'Unique Identifier' section displayed on the page. Click on 'Create' link. When the pop-up modal opens, select the name of the custom field that you are designating as the unique identifier of your contact records.
NOTE: The custom field MUST be defined as a string data type.
Import Rules When Using Unique Identifier
The data model allows for the UID field to be null. The allowance enables contacts to be added to your email list directly from sign-up forms prior to being assigned a member ID (or whatever field you have designated as your UID).
You are responsible to provide the value of the UID for each of your contacts. The most common way is to include the field in your email contact import file. (Email address is still a required field in your import file). Simply map the field in your import file to the custom field that you’ve defined as your Unique Identifier. In the example below, 'member_id' is the custom field that has been designated as the Unique Identifier and 'membership_id' is the column name in the import file.
Since the UID field is allowed to be null, if a record in the import file does not have a value for that field, then the rules for determining a new or existing contact will be based on the record’s email address as per the default process.
If a record in the file has a value for the UID field, then that field value will become the first determinant of whether a contact record exists or not.
If a record in the import file has a unique identifier and there is no record in the Contact database having the same unique identifier, then the next step is to check whether the email address of the record in the import file matches an existing record in the Contacts database. If a matching record is found, and that record does not have a unique identifier, then it will be updated (assuming that you’ve selected the option to update existing records), adding the unique identifier from the import file to that record. This logic flow is the primary way that contact records in the Contacts database are updated with their unique identifiers from the import file. On the other hand, if the matching record in the Contacts database (based on email address) already has an existing unique identifier, then the record from the file is not imported and is rejected as a 'Duplicate' record.
If the unique identifier of the record in the import file matches an existing record in the Contacts database, then the next step is to check whether the email address of the record in the import file matches that same record in the database. If it matches, then that record will be updated per the data in the import file (assuming that you’ve selected the option to update existing records). If the email addresses don’t match, then the final step is to check whether the email address in the import file matches a different record in the Contacts database. If no matching record is found, then the record will be updated along with its email address. However, if the email address does match an existing record in the Contacts database, then the record will not be imported, and rejected as a 'Duplicate' record.
The logic diagram below illustrates these import rules.Click to view larger image
Available Features for Unique Identifier
Once your contacts have their UIDs set in their profile records, you can take advantage of Maropost's advanced features specific to Unique Identifier.
- Link data in your relational tables by the UID instead of the contact’s email address. This option is especially helpful when the data you store in relational tables is associated with your contacts’ member IDs, or customer IDs, and not their email addresses.
- Send emails, text messages and mobile app messages to your contacts all through the same Journey.
- Add personalization from custom fields in your text messages and mobile app messages.
- Create and update contacts via API, referencing them by their UIDs instead of their email addresses.