Define condition dialog
Overview
You use the Define condition dialog to select characteristics of your visitors that you use to build filters for various features of Sitefinity Insight, such as defining rules for conversions, touchpoints, personas, and lead scoring types. In this article you learn how to use the various options of this dialog in the most efficient manner.
The dialog has two modes of operation:
- By behavior
In this mode, you specify an interaction or activity that a visitor completes on your site and the data that you want to collect from this interaction that you can afterwards use as a filter.
For example, a visitor visits a page and you want capture the URL of the page.
Interactions may span across different channels that characterize the visitor’s experience on your website. This experience may include what content the visitor sees, clicks, downloads, searches for, and so on. You can choose whether visitors score points just once or every time they complete the interaction.
- By contact property
In this mode you base your filter on a personal or a demographic characteristic of the contact profile who performs the interaction.
These rules consist of a contact profile property and its value.
For more information, see Configure contact properties.
By defining a rule, you specify the interaction and the object, or the contact property and its value. The following screenshot displays the Define conditions dialog:
Filter by contact properties
NOTE: This feature is not available when you define touchpoints.
To use contact properties as filtering criteria, perform the following:
- At the top of the dialog, select By contact property radio button.
- In the left dropdown box, select the contact property.
- In the right, click the header to choose the type of the filter you want to apply.
For more information about the operators, see the table below.
- In the input field on the rights, you enter the matching criteria.
- To save your changes, click Done.
Following is a detailed list of the operators that you can use to match the criterion. This example assume that you have selected FirstName as a contact property and have entered John as matching criterion:
| Operator |
Description |
| Exact match |
the string that you enter must exactly match the value of selected contact property.
In this example, all contacts with first name John match, but contacts with first name John-Angus do not match. |
| Is not |
the string that you enter must differ by at least one character from the value of selected contact property.
For example, all contact with first names which are not strictly John match, including names which contains these letters as part of the name. |
| Contains |
the string you enter must be present somewhere in the value of selected contact property.
In this example, all John, Johnny, Angus-John, or Christopher Johnnathan Anthony match. |
| Doesn’t contain |
the string that you enter must not be present anywhere in the value of selected contact property.
For example, Anthony would match, but Christopher Johnnathan Anthony would not match, because it contains John. |
| Starts with |
the string that you enter must be at the start of the value of the selected contact property.
For example, Johnnathan would match, but Anthony-John would not. |
| Doesn’t start with |
the string that you enter must not be at the start of the value of the selected contact property.
For example, Anthony would match but Johnnathan would not. |
| Ends with |
the string that you enter must be at the end of the value of the selected contact property.
For example, Anthony-John would match but Johnnathan would not. |
| Doesn’t end with |
The string you enter must not be at the end of the value of the selected contact property. For example, Johnnathan would match but Anthony-John would not. |
| Any provided |
all visitors that have provided a first name will match. |
| Not provided |
all visitors that have not provided a first name will match. |
IMPORTANT: Sitefinity CMS reports multi-valued user properties as a list of values separated by comma. Therefore, to create a rule which consists of a singular value, you must use the Contains operator and not the Exact match/Is operator.
For example, lets assume that you want to create a rule about visitors who are in the Content editor Sitefinity role. Sitefinity CMS reports the roles like this:
User, Background User, Administrator, Content editor
Therefore, you define the rule like this:
Role Contains Content editor.
Filter by visitor behavior
To use visitor actions and behaviors for selection criteria, perform the following:
- At the top of the dialog, select By behavior radio button.
- Click the title of the left dropdown box and select one of the following:
- Visitors who…
This filters the visitors who perform the specified action.
- Visitors who don’t
This filters the visitors who do not perform the specified action.
- In the dropdown box, select the action that you want to use for filtering.
When you do this, the right part of the dialog changes to the relevant configuration settings for your choice. For example, if you choose the Visit page with UTM parameters behavior, the right part allows you to enter an URL which Sitefinity Insight would automatically parse for UTM parameters. If you select Login, you do not need to enter any additional details, because all logins would be automatically counted.
- After you have chosen the visitors’ behavior, on the right you chose what data you want to capture.
You can also choose an exact or a loose filter. For example, if you want to capture an URL, use the exact filter, click the title above the right box and choose Exact URL. To use a loose filter, click the title above the right box and choose Part of the URL.
For text fields, you click the title to choose between Exact match and Contains. If you choose the latter, Sitefinity Insight matches all string containing the text you entered anywhere.
Some behaviors, such as Register and Login do not require additional filters. Sitefinity Insight matches these behaviors every time they happen.
- To save your changes, click Done.
Track Google Analytics UTM parameters
As a marketer, you often create multi-channel campaigns and you use different tools, such as Mailchimp or Eloqua, to handle different channels and traffic sources. To gather all the data about the performance of your campaigns, you can use UTM parameters.
You'll learn how to use UTM parameters to track page visits.
Sitefinity Insight enables you to create touchpoints, persona and lead scorings, and conversions based on UTM parameters.
To do this, when defining these metrics in the respective interaction picker, use the Visit page with UTM parameters interaction from the dropdown box. For example, when defining a new Touchpoint, the window looks like this:
For more information about defining the respective metric, see Define touchpoints, Add and manage lead scoring rules, and Conversion events.
There are the following considerations when using the interaction picker window to create metrics based on UTM:
- You always need to enter the complete page URL.
- You must enter at least one of the UTM parameters: Campaign, Source, Medium, Term, or Content in the corresponding text fields. As a convenience, when you paste a full URL with UTM parameters, Sitefinity Insight parses it and fills out the relevant text fields automatically from the URL.
NOTE: Unlike other interactions, the only supported relation among parameters is AND which is always used. Therefore, all parameters are considered when matching the interaction.
View content with tag or category rule
IMPORTANT: This rule is available only when defining rules for Personas and Lead scoring types.
The rule View content with tag or category differs from the other rules. You use this rule to define scoring rule not for a particular interaction but for entire class of interactions. For example, you can define a rule not for a particular news item, blog post, dynamic item, or page but for multiple such content items that you have classified using tags, categories, or custom classifications.
PREREQUISITES: Support for pages requires Sitefinity CMS 13.2 or later.
When you use this rule, you can choose from the following conditions:
- All of… indicates that all classifications that you have set must be satisfied for this rule to categorize a particular visitor.
If you assign different classifications to content items at different times, the visitor scores only once, at the moment when all classifications become applicable.
- Any of… indicates that at least one of the classifications that you have set must be satisfied for this rule to categorize a particular visitor.
If you assign different classifications to content items at different times, the visitor scores every time when any of the classifications become applicable.
NOTE: When you use hierarchical classifications, Sitefinity Insight flattens the hierarchy and considers all classifications at the same level. For example, consider the following classification hierarchy:
In this case, if your rule includes Soccer, items belonging to Sports, News, or Soccer will trigger the rule. If your rule includes News, the rule will trigger if your items are classified as either News or News » Soccer in Sitefinity CMS.
IMPORTANT: Sitefinity CMS always report the classifications to Sitefinity Insight in the site default language, even if the visitors see these classifications translated. When you create rules, use only the default site language.
If you have multiple sites reporting to the same data center, these sites use different default language, and they share the same classifications. In that case, you must create your rules to contain classifications in all default languages. For example, if you have two sites that share their tags, but have different default languages - English and German, your rule must look like tagEN or tagDE. This ensures that Sitefinity Insight correctly matches the reported events.
IMPORTANT: When you change your rule definitions, Sitefinity Insight recalculates the rules using historical data stored in your data center. Keep in mind that the View content with tag or category rule processes only data collected on or after December 9, 2020.