Computed attributes are reusable across Blueshift. Once launched, they become available in:

Customer profiles: View a customer's computed attributes in Customer Data → Profiles.
Templates: Reference them using Liquid syntax (e.g., user.computed_attributes.avg_order_value) to personalize messages.
Segments: Filter audiences based on computed values (e.g., customers with average order value > $100).
Reports: Analyze user distribution by computed attributes using audience insights reports.

Computed attribute use cases

Below are example configurations of computed attributes, based on common business goals. Each row highlights how to use fields like Function, Event, Attribute, Condition, and Time window.

Use case	Details
YTD revenue	Function: Sum Event: Purchase Attribute: Revenue Condition: — Time window: This Year (Jan 1 to today) Industry: Retail / Ecommerce
Revenue of last purchase	Function: Last Event: Purchase Attribute: Revenue Condition: — Time window: Within past 365 days Industry: Retail / Ecommerce
Average deposit amount	Function: Average Event: Deposit Attribute: Amount Condition: Status = Success Time window: Within past 365 days Industry: Personal Finance
Last submitted application	Function: Last Event: application_submitted Attribute: timestamp Condition: application_type = Credit Time window: Within past 180 days Industry: Banking / Lending
High-value monthly purchases	Function: Count Event: Purchase Attribute: Revenue Condition: Revenue > 100 Time window: This Month Industry: Retail / Ecommerce

Example walkthrough: Average order value (AOV)

Let’s walk through a real-world scenario of how a computed attribute is configured and used across Blueshift. In this case, we’re calculating a customer's Average Order Value (AOV) using purchase revenue over the past 365 days.

Attribute setup

The AOV attribute uses the Average function on the revenue field from Purchase events. The time window is set to 365 days.

Using AOV in a template

Computed attributes can be used inside campaign templates with Liquid syntax. The general format is:

user.computed_attributes.<computed_attribute_name>

For example, to display or check a customer’s average order value:

{% if user.computed_attributes.avg_order_value > 100 %}

Using AOV in a segment

You can filter users based on their AOV using segment conditions like “AOV is greater than 100.” This allows you to build more targeted campaigns.

Using AOV in a report

Use AOV to group customers and analyze distribution patterns in reports. For example, group users into bins based on their AOV to see how customer trends vary across the base.

FAQs

At what time are the attributes calculated daily? Does account timezone affect the computation start time?

Computed attributes are calculated at 1 AM UTC every day. The computation time is not affected by the customer account’s timezone.

What is the starting date for computation of YTD (year till date) attributes?

The starting date for YTD computations is always 1st January of the current year.

Who can access the extended event schema for computing attributes?

Only customers who have the Profiles and Schemas (ADP) package included in their contract can access the extended event schema for computed attributes. Note that all customers currently have access to the extended schema in the segment builder.

Stop a computed attribute

You can stop a launched computed attribute if it's no longer needed. This helps free up your quota and clean up usage across templates, segments, and campaigns. Learn how.

Ways to Use Computed Attributes Across Blueshift