蜜豆视频

Build your first rule build-query

The main steps to build rules for your Orchestrated campaigns are as follows:

  1. Add conditions - Create custom conditions to filter your query by building your own condition with attributes from the database and advanced expressions.
  2. Combine conditions - Arrange the conditions in the canvas using groups and logical operators.
  3. Check and validate the rule - Check the resulting data of your rule before saving it.

Add a condition conditions

To add conditions in your query, follow these steps:

  1. Access the rule builder from a Build audience activity.

  2. Click the Add condition button to create a first condition for your query.

    You can also start your query using a predefined filter. To do so, click the Select or save filter button and choose Select predefined filter.

    image showing the rule builder

  3. Identify the attribute from the dabatase to use as criteria for your condition. The 鈥渋鈥 icon next to an attribute provides information on the table where it is store and its data type.

    image showing the selection of an attribute

    note note
    NOTE
    The Edit expression button allows you to use the expression editor to manually define an expression using fields from the database and helper functions. Learn how to edit expressions
  4. Click the image showing the More actions button button next to an attribute to access these addititional options:

    accordion
    Distribution of values

    Analyze the distribution of values for a given attribute within the table. This feature is helpful for understanding the available values, their counts, and percentages. It also helps avoid issues such as inconsistent capitalization or spelling when building queries or creating expressions.

    For attributes with a large number of values, the tool displays only the first twenty. In such cases, a Partial load notification appears to indicate this limitation. You can apply advanced filters to refine the displayed results and focus on specific values or subsets of data.

    image showing the Distribution of values interface

    accordion
    Add to favorites

    Adding attributes to your favorites menu provides quick access to your most frequency used attributes. You can add up to 20 attributes to favorites. Favorite and recent attributes are associated with each user within an organization, ensuring accessibility across different machines and providing a seamless experience across devices.

    To access attributes you have favorited, use the Favorites and recents menu. Favorite attributes appear first, followed by recently used ones, making it easy to locate the required attributes. To remove an attribute from favorites, select the star icon again.

    image showing the favorites interface

  5. Click Confirm to add the selected attribute to your condition.

  6. A properties pane displays, where you can configure the desired value for the attribute.

    image showing the rule builder with a condition added

  7. Select the Operator to apply from the drop-down list. Various operators are available for use. Operators available in the drop-down list depend on the attribute鈥檚 data type.

    accordion
    List of available operators
    table 0-row-3 1-row-3 2-row-3 3-row-3 4-row-3 5-row-3 6-row-3 7-row-3 8-row-3 9-row-3 10-row-3 11-row-3 12-row-3 13-row-3 14-row-3 15-row-3 16-row-3
    Operator Purpose Example
    Equal to Returns a result identical to the data entered in the second Value column. Last name (@lastName) equal to 鈥楯ones鈥 will return only recipients whose last name is Jones.
    Not equal to Returns all values not identical to the value entered. Language (@language) not equal to 鈥楨nglish鈥.
    Greater than Returns a value greater than the value entered. Age (@age) greater than 50 will return all values greater than 鈥50鈥, such as 鈥51鈥, 鈥52鈥.
    Less than Returns a value smaller than the value entered. Creation date (@created) before 鈥楧aysAgo(100)鈥 will return all recipients created less than 100 days ago.
    Greater than or equal to Returns all values equal to or greater than the value entered. Age (@age) greater than or equal to 鈥30鈥 will return all recipients aged 30 or more.
    Less than or equal to Returns all values equal to or lower than the value entered. Age (@age) less than or equal to 鈥60鈥 will return all recipients aged 60 or less.
    Included in Returns results included in the values indicated. These values must be separated by a comma. Birth date (@birthDate) is included in 鈥12/10/1979,12/10/1984鈥 will return the recipients born between these dates.
    Not in Works like the Is included in operator. Here, recipients are excluded based on the values entered. Birth date (@birthDate) is not included in 鈥12/10/1979,12/10/1984鈥. Recipients born within these dates will not be returned.
    Is empty Returns results matching an empty value in the second Value column. Mobile (@mobilePhone) is empty returns all recipients who do not have a mobile number.
    Is not empty Works in reverse to the Is empty operator. It is not necessary to enter data in the second Value column. Email (@email) is not empty.
    Starts with Returns results starting with the value entered. Account # (@account) starts with 鈥32010鈥.
    Does not start with Returns results not starting with the value entered. Account # (@account) does not start with 鈥20鈥.
    Contains Returns results containing at least the value entered. Email domain (@domain) contains 鈥榤ail鈥 will return all domain names that contain 鈥榤ail鈥, such as 鈥榞mail.com鈥.
    Does not contain Returns results not containing the value entered. Email domain (@domain) does not contain 鈥榲o鈥. Domain names containing 鈥榲o鈥, such as 鈥榲oila.fr鈥, will not appear in the results.
    Like Similar to the Contains operator, it lets you insert a % wildcard character in the value. Last name (@lastName) like 鈥楯on%s鈥. The wildcard character acts as a 鈥渏oker鈥 to find names like 鈥淛ones鈥.
    Not like Similar to the Contains operator, it lets you insert a % wildcard character in the value. Last name (@lastName) not like 鈥楽mi%h鈥. Recipients whose last name is 鈥楽mith鈥 will not be returned.
  8. In the Value field, define the expected value. You can also use the expression editor to manually define an expression using fields from the database and helper functions. To do this, click the image showing the expression editor icon icon. Learn how to edit expressions

    For date-type attributes, predefined values are available using the Presets option.

    accordion
    See example
    image showing the preset option

Custom conditions allows you to query tables linked to the table currently used by your rule. This includes tables with a 1-1 cardinality link, or collection tables (1-N link).

For a 1-1 link, navigate to the linked table, select the desired attribute and define the expected value.

You can also directly select a table link in the Value picker and confirm. In that case, values available for the selected table need to be selected using a dedicated picker, as shown in the example below.

Query example

Here, the query is targeting brands whose label is 鈥渞unning鈥.

  1. Navigate inside the Brand table and select the Label attribute.

    Screenshot of the Brand table

  2. Define the expected value for the attribute.

    Screenshot of the Brand table

Here is a query sample where a table link has been selected directly. Available values for this table must be selected from a dedicated picker.

Screenshot of the Brand table

For a 1-N link, you can define sub-conditions to refine your query, as shown in the example below.

Query example

Here, the query is targeting recipients who made purchases related to the Brewmsaster product, for more than 100$.

  1. Select the Purchases table and confirm.

  2. Clic Add condition to define the sub-conditions to apply to the selected table.

    Screenshot of the Purchase table

  3. Add sub-conditions to suit your needs.

    Screenshot of the Purchase table

Custom conditions with aggregate data aggregate

Custom conditions allow you to perform aggregate operations. To do this, you need to directly select an attribute from a collection table:

  1. Navigate inside the desired collection table and select the attribute on which you want to perform an aggregate operation.

  2. In the properties pane, toggle on the Aggregate data option and select the desired aggregate function.

    Screenshot of the Aggregate data option

Combine conditions using operators operators

Each time you add a new condition in your rule, it is automatically linked to the existing condition by an AND operator. This means that results from the two conditions are combined.

To change the operator between conditions, click on it, and select the desired operator.

Example of a query

Available operators are:

  • AND (Intersection): Combines results matching all the filtering components in the outbound transitions.
  • OR (Union): Includes results matching at least one of the filtering components in the outbound transitions.
  • EXCEPT (Exclusion): Excludes results matching all the filtering components in the outbound transition.

Manipulate conditions manipulate

The rule buidler canvas toolbar provides options to easily manipulate the conditions within your rule:

Toolbar icon
Description
Move up selection icon
Move the component up a row.
Move down selection icon
Move the component down a row.
Group selection icon
Put two components in a group.
Ungroup selection icon
Separate the components of a single group.
Expand all icon
Expand all the groups.
Collapse all icon
Collapse all the groups.
Remove all icon
Remove all groups and components.

Depending on your needs, you may need to create intermediate groups of components by grouping components into a same group and linking them together.

  • To group two existing conditions, select one of the two conditions and click the Move up selection icon or Move down selection icon button to group it with the condition above or below.

  • To group an existing condition with a new one, select the condition, click the image showing the More actions button button and select Add group. Select the new attribute to add to the group then confirm.

In the example below, we have created an intermediate group to target customers who purchased either the BrewMaster or VanillaVelvet product.

Check and validate your query

Once you鈥檝e built your query in the canvas, you can check it using the Rule properties pane. Available operations are:

  • View results: Displays the data resulting from your query.
  • Code view: Displays a code-based version of the query in SQL.
  • Calculate: Updates and displays the number of records targeted by your rule.
  • Select or save filter: Choose an existing predefined filter to use in the canvas, or save your query as a predefined filter for future reuse.

When your rule is ready, click the Confirm button in the to save it.

IMPORTANT
Selecting a predefined filter from the Rule properties pane replaces the rule that has been built in the canvas with the selected filter.
recommendation-more-help
b22c9c5d-9208-48f4-b874-1cefb8df4d76