Records about people (customers, contacts, leads and subscribers) are supplied as 'contacts' records.
Contacts are organised into 'collections'.
For example you could have a 'customers' collection (customer records from your eCommerce platform) and a 'subscribers' collection (contact records from your ESP). Each record in a collection is uniquely identified by a string ID.
In this case it may be that the same person exists in each list (or even more than once in each collection).
Ometria will attempt to merge these contact records into a single 'profiles' record (based on customer_id and then email address).
This means a single profile record may have several contact records attached.
You can’t write profile records directly as they are automatically clustered by Ometria.
We recommend that you pass contacts from different sources into Ometria with different collections.
This will help to ensure that data on the record is not overridden by missing data from another source.
Contact listings priority
When merging contact records to create a profile, there are sometimes varying parameters on the contact records.
When this happens, Ometria uses the following two rules of priority to determine which value to assign to the profile:
Standard rules of priority
- The Ometria preference centre
- API, App, CSV
- Ometria form
- Importer (e.g. Magento or Shopify)
- Third party sync
- If there are two contact records with the same level of priority then the varying parameters from the most recent contact record is used, i.e. the last record pushed to Ometria or to reach our API endpoint.
- firstname and lastname parameters will always be taken from the same contact record.
Marketing opt-in rules of priority
These rules only apply to a contact's marketing_optin value. The rules below can be overridden by @FORCE_OPTIN.
- Any Ometria controlled source (e.g. Preference centre, Platform, Ometria Form, CSV Upload).
- Any Client controlled source (e.g. API, Magento importer).
- Any third party controlled source (eg. Mailchimp)