Introduction


The Ometria platform is based around contacts, products and orders. This page provides an overview of the concepts of the data and how we link your contacts into profiles and attach your products to your customers orders. This page also provides details over how we extend each of the key data points and how the extra data can be used in the platform.

Ometria Summary Integration Architecture

The key concepts of Customers, Orders & Products are connected via Javascript and API. The contacts can also be updated via the subscription and preference centre forms. Contacts are merged by Ometria to create customer profiles which can then be sent campaigns and reported against.

The Ometria model combines the the data into some key tables shown below. Note the diagram is provided is not a full data schema for Ometria, but provides the concepts for Customers, Orders and products and how they are linked to each other and to lists and activities.

Ometria Contact Model

The Ometria contact model takes the different contact sources provided (such as Online, Store) and combines these into a single profile. The contact source is a collection and you can have as many different collections as you require and they do not need to be pre-determined.


For a contact, the contact ID, email and collection act as a unique key. You should ensure the contact ID is unique for a collection.


The customer ID is optional and should only be used where you have one persistent key across all of your data sources that uniquely identifies an individual customer.

The contact and profile can be extended using Custom fields. The fields can be of the following types,

  • String fields (any characters (UTF-8  so includes accents and other character symbols))
  • Integer fields  (only whole numbers, e.g. 1, 2, 3, 4, 500, -344)
  • Decimal fields  (any numbers, e.g. 5, 5.6, 553.3433, -454.34343)
  • Date fields (e.g. date and time, 2018-01-05 15:03:04)

There is a limit of 100 custom fields per type, however, the maximum size of the combined custom properties associated with any record must be <1kb (1000 characters) when formatted as JSON, e.g. including keys and values.

Custom fields can be used in both Segmentation and as merge fields email content.

Ometria Order Model

The order model connects your orders to customers and provides properties specific to the order or the line item. Variant options passed in an order will automatically create a new variant product, which means that you do not need to pre-determine variants when sending Products to Ometria.


Order ID in the Order object is unique and must be unique across all of your order sources, such on online and offline stores.


The Order model can be extended by using order properties, order attributes and line item properties. These values are used in different ways within the platform shown below;

TypeMerge Tags In Email ContentSegmentationRecommendations
Order PropertiesYesNoNo
Line Item PropertiesYesNoNo

Ometria Product Model

The Ometria product model provides for both parent and variant products. Listings provides for different country (or website) variations of the products to be listed. Listings are used to provide different currencies for the products.


The Product model can be extended by using product properties and products attributes. These values are used in different ways within the platform shown below;

TypeMerge Tags In Email ContentSegmentationRecommendations
Product PropertiesYesNoNo
Product AttributesNoYesYes