More About Rules

Rules are used across Hushly for a variety of purposes. Rules act to build containers of content to make content tracks and personalized recommendations for the appropriate users. Rules:

• Trigger Experiences.
• Automate the addition of Assets to a Stream.
• Determine Recommendations for Content in a Hub.
• Constitute the definition of a Segment.
• Establish Exit Intent Suppression at a company level for all Experiences.
• Define the Suppression and Restriction of unwanted leads.

Parts of a Rule

A rule is a condition. The basic structure of a rule is <LHS> <COMPARISON OPERATOR> <RHS>.

Note: 

Based on the LHS selection, the comparison operators and the RHS vary. 

The LHS is of two types: Free Text and List. 

• Free text fields will have all the comparison operators to select from.
• List-type fields will have a subset of the comparison operators shown in the table. 

Examples

• If LHS is a page URL, the RHS will be text. 
• If LHS is a country, the comparison operators are a subset of the operators and the RHS will be a picklist.

Important:

Every Hushly account includes MaxMind as the Default Data Provider. To ADD a Data Provider (Bombora, 6sense, and/or Demandbase) to your Hushly account, please contact your Customer Success Manager. 

Experiences and Streams of content are customized for the user based on what the Data Providers may already know about the user, such as the location and industry.

How to Define a Rule

Rule Builders are used in Hushly to manage Experiences, Hubs, and Setup.

Examples 1 and 2 below are based on external parameters and are found in the following areas:

• Experience rule builder.
• Recommendation rules for Hubs.
• Segments in the Setup section.
• Suppression and restriction rules are in the Setup section.

Example 1: Defining a Rule with a Standard Field

To define a rule with a standard field in the LHS, select the LHS field, a comparison operator, and enter a text value or pick from a list.

Example 2: Defining a Rule with a Data Provider Field

To define a rule with a Data Provider field in the LHS, select the LHS field, a comparison operator, and enter a text value or pick from a list.

Example 3: Defining a Rule with a Custom Field

To define a rule with Custom or Asset fields in the LHS, select the LHS field, a comparison operator, and enter a text value or pick from a list.

Note: However, example 3 is defined based on internal parameters.

Example 4: Defining a Rule with the Contains Operator set.

To define a rule with any one of the contains operators set, select the LHS field, a comparison operator (contains/contains only/ doesn't contain), and pick a value from the Multi-Select Pick List.

Example: When a rule is defined for Industry - Healthcare with any of the Contains Operator Set, the following would be the behavior: 

• Contains: The contains operator indicates a search for any of the specified values. Example: When the operator has a defined value, the Assets that contain Healthcare are fetched.
  
  
• Contains only: The contains only operator indicates a search requires a match of the specified words or phrases. Example: When the operator has a defined value, the Assets that contain only Healthcare are fetched.
               
  Note: If an Asset has more than one value selected in a multi-pick list, i.e., Healthcare AND Legal, and "contains only" is used as defined above this Asset will not appear. 
               
• Doesn't Contain: The doesn't contain operator indicates a search that doesn't require a match of the specified words. Example: When the operator has a defined value, the Assets that don't contain Healthcare are fetched.
  
  

Example 5: Defining a Rule with H-Signal

To define the rules based on H-Signal, select the audience using H-Signal based on Visitor Topics, Visitor Score Boost, Account Topics, and Visitor Score Boost. Then select comparison criteria to define the rule and specify the H-Signal value on the right field.

Matching Rules

After defining two or more rules, you can match them in 3 ways:

• Match any rule (Match Any)
• Match all rules (Match All)
• Match the rules selectively (Advanced)
  
  

Example: Match Any Rule

The rules below trigger the desired behavior when any of the rules are met.

Result: 

When any one of the above rules is satisfied, the rule evaluates as True.

Example: Match All Rules

The rules below trigger the desired behavior when all of the rules are met.

Result: 

When all of the rules below are satisfied, they are collectively evaluated as True.

Example: Match the Rules Selectively

Some campaigns may need a plethora of rules that should be matched selectively or in groups. Advanced rule matching supports selective rule matching.

Result: 

The condition evaluates to True if the user is from a medium-small healthcare company with 50-199 or 500-999 employees in the USA.