Field configuration

The fields returned by a dataset exist for use in segmentation, campaign content, or both. It is important to know a field’s intended use to configure it accordingly.

All fields require a data type for the Simon model. The following types are supported: boolean, currency, float, integer, positive integer, big integer, string (< 255 characters), text (255 characters), date, rate, and set. When choosing a data type, consider the different operators that apply (e.g. ‘greater than’ for integers, ‘contains’ for strings). In some cases how the field is saved in your database will differ from how it is saved in Simon. For example, while an order ID may be an integer in your database, it may make more sense to save it as a string in Simon since arithmetic operators will not be used.

If the field will be used for segmentation, select the Condition button. Condition ensures the field appears for use in the segment builder, and without this button activated the field cannot be used for segmentation. If selected, the field must have a display name for display in the builder. Once used as a condition in segmentation, a field is always a condition. This ensures existing segments that rely on the field are not disrupted.

If the field is to be used as content, select the Content button. Content ensures the field is available for use in custom context during flow creation. No further validations are needed, and, like a condition, a content field stays a content field for its lifetime.

Note on implied null values:

In some cases null values are unavoidable. However it is often the case that a null value implies useful information. For example, a contact without any purchases may return null as their total purchased amount, but it can be implied that their total purchased amount is $0. Simon Data supports implied values that have different defaults based on data types:

These implied values can be overridden on a per-field basis. To do so, please contact your account manager.