This article will teach you where and how to create a Computed Property. We suggest reading our Introduction to Computed Properties before you get started.
Skip To:
- Step 1: Getting Started
- Step 2: Navigate to Computed Properties
- Step 3: Create
- Step 4: Build
- Step 5: Click SAVE & wait
- Step 6: FIND your computed property in segments
- Step 7: LEVERAGE your computed property in SEGMENTS, CAMPAIGNS, AUTOMATIONS, AND FOR ANALYTICS
- Supported Calculation/Computation Types
- First Party Track Events
Step 1: Getting Started
To prepare to build a Computed Property, you will want to have the following information ready:
-
Computation Type (e.g. Count)
- Click here or scroll to the bottom of this article to see the full list of calculation/computation types supported.
-
Track Event (e.g. Order Completed)
- Click here or scroll to the bottom of this article to see the full list of first-party Track events
- Any GDP-enabled brand can also send in unique Track events or have integration-specific Track events available.
-
Conditions / Properties (e.g. 'Merchant ID' aka Location, Order Source = Olo)
- Conditions are the detailed data points that travel with a Track event
- You'll find available conditions vary by Track event and can be viewed when you click 'View Properties' on a Track event from the Timeline. See example below.
Example:
'View Properties' on an 'Order Completed' Track Event Accessed via a Guest Timeline
You can click into any guest timeline from the Guest Book search at the top of the Dashboard. Once you’re in the timeline, you’ll want to click on ‘View Properties’.
- You can also click into a guest timeline when you’re looking at guests who fall into a Segment .
Note: This is showing the JSON view of the 'View Properties' UI, which you can learn more about here. Conditions are outlined in red that may be of interest when building a Computed Property.
Step 2: Navigate to Computed Properties
Once you're prepared, navigate to the Guest Data section of the side navigation within the Engage Dashboard. There, you'll see Computed Properties.
Step 3: Create
Follow the steps of the builder to begin creating a Computed Property.
-
Name your Computed Property
- Note the name exactly as you type it here will be how the Computed Property appears in the Segment dropdown as a segmentation criteria option. This cannot be edited once created at this time.
-
Select Computation Type
Step 4: Build
Leverage the information you gathered for 'STEP 1: PREPARE' to build your Computed Property
- Select the Track Event for your computation
- Add Conditions
- Select the Date Range for the computation
Step 5: Click SAVE and wait
Once you've completed building your Computed Property you'll click 'SAVE.' The computation will take time to process. Once initially created, a Computed Property can take up to 6-12 hours to fully process all guest records and complete the computation.
Thereafter, the computation will be kept up-to-date on a on-going basis. Please be aware that initial computation time is needed before using a Computed Property within Segments/Automations and wait a suggested 12 hours before first leveraging the Custom Property (e.g. as a Segment Entry/Exit Trigger).
Step 6: Find your Computed Property in Segments
Navigate to Guest Data > Segments > Create Segment and in the segmentation criteria dropdown you'll find your Computed Property in the list of available fields under the category 'COMPUTED PROPERTIES' exactly how you named it when you built it.
Reminder: The Computed Property will show as an available field in the Segment dropdown shortly after it's created in most cases. There could be a delay due to processing time for the computation OR the field may not show up at all if there are no guests yet which meet the computation criteria.
Step 7: Leverage your Computed Property in Segments, Campaigns, Automations, and for Analytics
From here, you will leverage the Computed Property just as you would any other Custom Field/Property when building a Segment — by adding in parameters & operators to get to your desired outcome.
Supported Calculation/Computation Types
|
Count |
The number of events that match a specified interaction (e.g. Count of Orders Completed). |
|
Sum |
The results of a specified property added together, which must be a number (e.g. Sum of “Total” spent on Order Completed events). |
|
Min |
The lowest value for a specified property, which must be a number or timestamp. |
|
Max |
The highest value for a specified property, which must be a number or timestamp. |
|
First Value |
The oldest value for a specified property. |
|
Last Value |
The most recent for a specified property. |
|
First Timestamp |
The oldest occurrence for a specified property. |
|
Last Timestamp |
The most recent occurrence for a specified property. |
|
Average |
The average value of a property, which must be a number. Processing time may be longer for this computation type. |
First Party Track Events
| Automation Started |
| Automation Completed |
| Automation Email Opened |
| Automation Email Delivered |
| Automation Email Clicked |
| Automation Email Failed |
| Automation Exited |
| Email Sent |
| Email Opened |
| Email Delivered |
| Email Clicked |
| Email Failed |
| SMS Sent |
| Party Created |
| Party Updated |
| Party Seated (midnight api) |
| Order Completed |
| Survey Completed |
| Wifi Checkin |
| Segment Entered |
| Segment Exited |