Value types in analyses and filters

This article is a continuation of the Event and attribute operators article.

Once you define a logical operator in an analysis or a filter, you must define a value that will be used with the operator to check if the selected attribute or parameter meets the condition.

You can select the following value types:

• Array
• Dynamic key
• Number
• String
• Synerise objects

Value types

Array

If you want to analyze a parameter or an attribute in the filter or an analysis that is an array, you must use the Array operator. Then the field that appears next to the operator accepts the value of an array.

• If the array contains different data types (numbers, objects, arrays) it must be converted into a string and analyzed as a string.
• If you want to analyze occurrences of more than one string, you can do it in the following way:

  

Example

The example below presents the condition in a metric that calculates the occurrences of an array that contains the potato, steak value in the products parameter in a groceries.bag event.

Dynamic key

A dynamic key is a condition whose value can be changed when the analysis is requested.
You can use a dynamic key to create a dashboard entirely dedicated for the analysis of a given aspect, for example, an item, a customer, a campaign, a brand, a product model, and so on.

How to create a dynamic key?

While preparing any analysis (except for aggregates, expressions, and dashboards):

1. Select the property to test (profile attribute or event parameter)

2. After selecting the property, next to the operator, click the icon until you get two fields: Dynamic key and Value.

   

3. In the Dynamic key field, enter the source of the value for the dynamic key. The property will be compared with this value.
   You can:

   • use predefined dynamic keys.
   • access event parameters in the following way: event.params.PARAMNAME
   • use any name for the key (no special characters, only letters and digits allowed). Such a key is only useful in dashboards, because dashboards allow you to enter a value manually.

4. In the Value field, enter the default value.
   This value is used:

   • In Automation: if the parameter from the Dynamic key field doesn’t exist in the event/profile that is analyzed in the filter.
   • In Dashboards: As the initial value of the dynamic key.
     
     Important: Using a comma (,) in the value of a dynamic key splits the string. Such a value is treated as an array. Escaping the comma isn’t supported.

5. Click Save.
   Results:
   You can use the dynamic key:

   • when you create a dashboard and add this analysis, the Dynamic key button appears on the editing panel. Then, you can specify the value of the dynamic key or use the default one.
   • in analytics such as profile filters in Automation.

Example 1

In the above example:

1. A mobile application adds the newsletterTrigger parameter to events it sends. This parameter is the SKU of an item. This is a custom parameter invented for the purposes of this example
2. The newsletterTrigger parameter changes periodically.
3. A workflow is created to send a newsletter when a customer adds the required product to their cart.
4. A “Profile Filter” node is added to the workflow. In this node:
   1. The product.addToCart event is analyzed.
   2. The value of the sku parameter is tested.
   3. The value to test against is a dynamic key:
      • The value is taken from the event’s newsletterTrigger parameter.
      • If the parameter doesn’t exist, the default value (NONE) is used.
5. If the value of sku in the event is the same as the value of newsletterTrigger, the profile matches the filter.
   Further nodes in the workflow send the newsletter to matching profiles.

Example 2

The example below presents the condition of a metric that calculates the number of times a product was purchased. In this example, the id dynamic key is created and it will be compared with the values sent through the $sku parameter of the product.buy event. At this stage, the default value of the dynamic key is not important in this analysis, so it’s set to .. The result for this metric will be 0, but the metric will be added to the analytical dashboard (figure 10) in which the value of the dynamic key (the SKU of the item) will be defined and produce results.

This metric is added to a dashboard. In the Dynamic key field, you can enter a SKU and the dashboard will show metrics result for events in which the $sku parameter was the same as the SKU you entered.

Number

The numerical value is expected when you select the number operator and/or the event parameter or attribute is sent to Synerise in the form of a number.

Example

The example below presents the condition of a metric that calculates the number of transactions above a specific value. In this example, the More than logical operator is used (the Number type operator) to narrow down the analysis to transactions where the monetary value was more than 100.
Currency is a separate parameter. This example shows events with $totalAmount over 100 regardless of the currency.

String

This type of value allows you to enter a string of characters. It accepts special characters and spaces.

How to select a string value

After you select an operator, it’s the default parameter/attribute value.

Example

The screen below presents the condition of a metric: it calculates the first occurrences of the newsletter.open event (an event which is generated when a profile opens an email) in a mobile channel. The is that the source parameter of the event must include the string mobile.

Synerise objects

As the value of the condition, you can select an element created in Synerise. Then, the value of this element will be treated as the value for the condition.

The range of Synerise objects which you can use as values depends on the property type you select. You can select the following property types (remember that property types can also be Synerise objects):

• event and event parameters
• profile attribute

Event and event parameters as properties

If you select an event as a property, you can specify its occurrence with the objects from the left column and analyze it against objects from the right column:

Profile attributes as properties

When you select any profile attribute as a property (left column of the table), you can select its value in accordance with the values from the right column:

Synerise object reference

Example

The example below presents an aggregate that returns the list of last 100 IDs of transactions from the last 30 days which contain the products visited which were displayed in a defined recommendation campaign. The condition of the aggregate uses an aggregate that returns the SKUs of the clicked items within a particular recommendation campaign.

1. Create an aggregate that returns the last visited recommendations in the defined time range.
2. Create a new aggregate:
   1. Set the size of returned results to 100.
   2. Select the Consider only unique occurrence of the event parameter.
   3. Select the Bought product event.
   4. As the event parameter, select $orderId.
   5. After the $orderId parameter, add $sku parameter that occurs in the results of the aggregate from step 1.