With the Custom Schema Creation feature, you can build customized collections without any coding involved. The intuitive drag-and-drop editor allows you to design hierarchical data structures. Intempt platform uses JSON to define the schema and data types, allowing for convenient schema evolution.

How to create Collections

Under the Sources object, locate and click on the desired created source. After, a detailed view of the source will be visible, with Overview, Schema, Data Import, and Attribute mapping tabs.


Click the Schema tab. After clicking the tab a window will open from where users can see the created Schemas and create new ones.


Adding a Collection

Click the Add collection button and a pop-up window will appear where you can state the name of the collection. After naming the collection, it will be displayed on the page.


Editing Collection name

To edit the Collection name users need to navigate to the Three dots icon. From the dropdown, select the Edit collection name option and provide a descriptive name for the Collection.


Deleting a Collection

To delete a Collection users need to navigate to the Three dots icon. From the dropdown, select the Delete collection option. Users need to confirm the deletion of the Collection by inputting the name of the Collection.


Adding a field

To add a field to the Collection users need to navigate to the Plus icon. From the dropdown, select the Add field option. From the appeared side window users can:

  • Name the field
  • Assign object type
  • Assign field properties


Adding a nested field

NOTE: prior to adding a nested field, users first need to have a record-type field created in the Collection

From the record-type field under the Three dots dropdown icon select the Add field option. From the appeared side window configure your nested field.


The nested field can be accessed from the record-type field by clicking on the arrow to expand the nested fields.


Field object types

You can assign a field with one of the following object types:

  • boolean - is true or false values
  • string - text input
  • int - (Integer) for numeric values
  • long - holds signed integers ranging in value from -9,223,372,036,854,775,808 through 9,223,372,036,854,775,807 (9.2...E+18)
  • float - for numeric values with decimals
  • double - for a variable that holds very large (or small) numbers. It can contain up to 15 digits in total, including those before and after the decimal point
  • record - a collection of multiple attributes


Key identifiers

To build valid dependencies between the collections, primary and foreign keys need to be assigned to the required fields. To add a key, tick the checkbox in the field configuration.


After ticking the required checkboxes, FK (foreign key), key icon (primary key) initials will appear in the field row icon field.


Differences between primary and foreign keys:

  • Primary Key – must be assigned to any field that is always unique within a created collection. This is necessary for giving each entry a unique identifier.
  • Foreign Key - is a field in a collection that refers to the primary key in another collection. The foreign key links collections and allows to use of related collections in the Event editor.

Foreign keys

If you select a Foreign key option, you will also need to choose the respective foreign collection and foreign fields that refer to the primary key.


Profile identifier

It is a Primary key showing that the field belongs to a profile collection. It is used to identify profile collections that create or merge user profiles.


Account identifier

Select fields that will be used as account identifiers - these data objects should have information about the user (e.g., age, location, gender and etc.). If selected, these collection fields will be available to be used in the segment editor - to filter users by their attributes.


User identifier

To identify anonymous cross-channel users, you need to select which collection objects will allow you to identify and merge anonymous users into unified master profiles. To do that, you need to choose a collection field that is a common identifier across different sources. Usually, this field is email, but it can also be a phone, loyalty ID number, etc.


Product identifier

Product identifiers are used to mark which fields are used to describe product-related data, such as price, type of the product, size, etc.