How to set up attributes in Meiro Business Explorer

A unique id for the attribute. There should be no whitespace.

As a good practice, the Attribute ID should be human readable and snake casing should be used.

Note: Once the attribute is saved, this field cannot be changed!

A category of the events which contributes to this attribute.

Selectable from Sources created in Setup -> Sources
Note: Once the attribute is saved, this field cannot be changed!

Attribute category. There can be multiple Labels for an attribute.

Example labels: Geographic, Technographic, Demographic, PII

Selectable from Labels created in Setup -> Labels

Single - attribute has only one value, eg. Last Page View, First Name

Mutiple - attribute can have many values, eg. All Emails, All Devices, All UTMs

Note: Once the attribute is saved, this field cannot be changed!

The attribute value's type, eg. Boolean, Datetime, String, Integer

Learn more about basic data types here

Learn more about the compound data type here

Note: Once the attribute is saved, this field cannot be changed!

On - Attribute will be calculated when it has been defined

Off - Attribute is not defined and will not be calculated

Predefined - Attribute is defined based on the events and parameters filled up. Use Predefined attribute if your attribute does not require complex logic

Custom - Write your own custom SQL script for your attribute. Use Custom attribute if your attribute requires a deeper logic.

The data sources required to calculate the attribute.

Selectable from sources created in Setup -> Sources

If empty, all data sources will be used in attribute calculation.

The event types required to calculate the attribute.

Selectable from events created in Setup -> Events

If empty, all event types will be used in attribute calculation.

The event versions required to calculate the attribute.

Selectable from event versions created in Setup -> Events

If empty, all event versions will be used in attribute calculation.

The type of aggregation for the attribute.

Eg. Most frequent, least frequent, maximum, minimum, first, last, sum, average

The value of the event to be calculated.

Should be in SQL syntax

Eg. payload->'price'

Additional conditions that you want to filter out from the attribute

Should be in SQL syntax

Eg. coalesce(payload->'email', '') != ''

event_time >= current_timestamp - interval '30 days'

What happens when I create a new attribute?

New column of attribute will appear in customer_attributes table. 

New entities will have their new attribute calculated.

The attribute value for old entities will remain NULL until recalculated

The change in the attribute is propagated within 5 minutes.

All newly recalculated entities will use the new definition.

Old, already calculated values will stay in place until recalculated.

An entity's attributes are calculated when any of these occur:
1. When the entity is first stitched.

2. When new events are stitched to the entity.

3. Every 7 days, ie. when the entity has no new events in the past 7 days.

By default, an entity's attributes are recalculated once every week.