A Calculated Attribute is a read-only value about a single user, providing granular insight into user behavior. These attributes are defined in mParticle and are computed automatically over time by using the raw data stream of events and user information.
Calculated attributes can be defined to track almost anything you want to calculate for an individual user. A calculated attribute is composed of the following elements:
draftstatus indicating that they are no being calculated. Once activated, calculated attributes are in the
activestatus to indicate that they are being calculated and can be used across the mParticle platform and downstream.
Calculated attributes are defined and calculated in the scope of a single workspace, which means they use data available within that workspace only. You may create calculated attributes with the same name in multiple workspaces.
Once a calculated attribute is activated, the backfilling of existing data can take anywhere from 24 hours to several days, depending on the date range selected. When new data arrives it will either be processed immediately or with a delay, see the table Calculation Formats below for more information.
We currently support 13 calculations organized into three groups:
count of times an event has occurred. For example:
Calculate statistics about event attributes:
Calculate the value or timestamp of the first or last observation of a specific event:
last value and
Calculate values based on the unique set of observed values for a specific event:
unique list count,
The following table defines the data types produced by each calculation. All timestamp values are in ISO 8601 format in the UTC timezone. Several calculations produce results with types that depend on the type of the event attribute selected, for example First Value.
Synchronous calculations are evaluated immediately and updated values are included in the outgoing event batch. Asynchronous calculations are evaluated with a delay and updated values are included in the next outgoing event batch.
||N (until observed)|
||N (until observed)|
|List||Unique List||Comma separated list of dynamic values; maximum of 100.||
|List||Unique Values Count||Numeric||
* Setting the date range to ‘within the last’ will produce asynchronous calculations.
Calculated attributes can be setup to calculate over all data seen or over a specific time window. This allows you to limit calculations to a more relevant business window such as “unique list of product purchased in the last 30 days” or “total bookings made over the last year”.
The following date ranges are supported:
During early access, date range is limited to the audience retention period as set at your account level. Contact your success manager for more information.
To create a Calculated Attribute:
Click on the data criteria section to define the data used to run the calculation.
To adjust date range for your calculation, click on Date Range criteria.
A calculated attribute must first be activated in order for mParticle to start calculating its values across your users.
To activate a Calculated Attribute:
When activated, mParticle will start to compute and initialize the initial value for the calculated attribute. This uses both the historical data in mParticle and real-time incoming data.
Depending on the date range, volume of data in your workspace, and complexity of definition, calculations will have varying SLAs before it first becomes available across your customer profiles. Whilst calculating, the UI will display its calculation progress.
mParticle will enrich incoming batches with active calculated attributes for that user. Just like regular user attributes, you can restrict which outputs receive them, using the data filters.
Calculated attributes can be viewed alongside other user attributes in the User Activity view, and are accessible via the Profile API. Values will appear in UAV only once the calculations have completed for the user displayed.
Calculated attributes can be used in the Audience builder by selecting User > Calculated Attributes.
Was this page helpful?