Understanding Properties and Matching Policies

The Contacthub customer database properties structure is document-oriented. This means it has a flexible format that can contain different elements, depending on specific information needs, rather than being a flat set of fields, which may just have values or not.

Data types

The following traditional data types are available:

  • String.
  • Number.
  • Boolean.
  • Date.
  • Datetime.
  • Email.
  • URI.
  • IPv4.
  • IPv6.

In addition, you can also create properties with the following data types:

  • Array.
  • Object.
  • Array of deprecated objects.

Predefined properties

Contacthub provides a set of predefined Base properties, which can be enabled or disabled within the UI, as required. You can find a list of Base properties here.

Enabling and disabling Base properties

You can enable or disable Base properties using the UI. See Enabling and disabling Base properties for more details.

If properties are disabled, any changes to their read or write settings are ignored.

Custom properties

In addition to enabling or disabling Base properties, you can also define custom ones, which are known as Extended properties in Contacthub. See Creating Extended properties for more details.

Matching Policies

Matching Policies enable you to define the property fields that should be used to determine whether data apparently belonging to two customers, actually relates to same one. See Configuring Matching Policies for more details.

The defined policy is applied to the View nodes, in combination with the Customer uniqueness setting for the relevant workspace. See Understanding Nodes and Trees and Configuring Workspaces for more details.

JSON files

To assist with integration and help you to configure and customize Contacthub, you can download a copy of the JSON file that defines the schema for all Base or Extended properties. See Enabling and disabling Base properties and Creating Extended properties for more details.



Previous page: Configuration overview | Next page: Enabling and disabling Base properties