Optimizing Alerts with Conditions

Table of Contents:

1. How Conditions Work?
2. Global and Local Conditions
3. How to add or delete conditions?
4. Text Types
5. Condition Types
6. Number Format
7. Which Condition Triggered?
8. Common Usecases
9. Condition in Legacy Version
10. Troubleshooting Common Issues.
11. FAQ

Conditions lets you receive alerts only when the change matches the criteria set by you. You can use it effectively and reduce the volume of unimportant alerts.

How Conditions Work

An alert is triggered under the following circumstances:

1. Change Detection: A change occurs on the monitored webpage. And,
2. Condition Evaluation: The change satisfies the defined conditions (both global and local).

This dual requirement ensures that alerts are both relevant and meaningful.

Examples

Price Alerts

• Scenario: Receive an alert when an item’s price, currently $80, drops below $70.
• Without Conditions: Alerts for any price change.
• With Conditions: Set a condition for alerts only if the price drops below $70. Added Text is less than 70.

Keyword Monitoring

• Scenario: You wish to be alerted only when monitored text includes specific keywords.
• With Conditions: Add a condition specifying that an alert should only be triggered if the added text contains “yourkeyword”. You can add multiple conditions to cover various keywords. Added Text contains keyword1 OR Added Text contains keyword2.

Global and Local Conditions

Global conditions apply to all monitors in your watchlist, suitable for uniform criteria across monitors.

Here is how to navigate to the Global condition:

1. Click on the Hamburger icon from the Watchlist.
2. Click on the “Global Conditions”.

Local conditions apply to a specific monitor. When both are set, both conditions are evaluated for alerts.

How to add or delete conditions?

Following are the steps to add conditions to a monitor:

Step 1: Click the “menu” button on a monitor to access menu options.

Step 2: Select “Edit Options” to open the options window.

Step 3: Click “Add Condition” to add a new condition or the cross button beside an existing condition to remove it.

Step 4: Save your changes.

Text Types

Following are the different text types on which conditions can be applied for evaluation.

Example - Changes in the monitored content

• Original Text: “Distill is an awesome monitoring app for web”
• Updated Text: “Distill is the best web monitoring app”

This is how it will appear in the change history. By default, the change history shows the added text highlighted in green. The deleted text has not shown as Deleted is unchecked in the change history.

Based on the above example, here is a table showing values of different text types. Note the change in the position of the word ‘web’ in the example, which affects the values of Added Text and Net Added Text.

Text Type	Description	Values based on the above example
Text	Applies conditions to the whole monitored text, suitable for comprehensive content analysis.	Distill is the best web monitoring app
Added Text(Preferred)	Targets only the text that was added after the latest change, ideal for incremental updates or additions. Use case: Trigger a notification when new keywords are added to a document.	the best web
Deleted Text	Focuses on text that was deleted during the latest update, critical for tracking content removal. Use case: Alert when specific terms are removed from a policy document.	an awesome for web
Previous Text	Conditions are evaluated on the whole text available before the latest change.	Distill is an awesome monitoring app for web
Net Added	Evaluates on the added text and ignores reordering of the texts. Use case: Ideal for dynamic content like news feeds, product lists, and ticketing sites that frequently reorder text sections. Use case	the best
Net Deleted	Works like Net Added, ignores reordering of text. Use case: Ideal for dynamic content like news feeds, product lists, and ticketing sites that frequently reorder text sections.	an awesome for

You can click on the bell icon from the change history to see values of different text types. You can also see how the conditions (if set) were evaluated to trigger an alert.

Condition Types

Following are the condition types available in Distill latest version. You can use one or more of them based on your requirement.

Type	Description
contains	Checks if the text includes a specified keyword or phrase.
does not contain	Verifies that the text does not include the specified keyword or phrase, similar to contains.
starts with	Determines if the text begins with a specified text.
doesn't start with	Ensures the text does not start with a specified text.
ends with	Checks if the text ends with a specified text.
doesn't end with	Confirms the text does not end with the specified keyword or phrase.
is empty	Verifies if the text is empty.
is not empty	Confirms that the text is not empty.
has number less than (<)	Applies when the numeric value in the text is less than the specified number.
has number more than (>)	Determines if the numeric value has increased by more than the specified amount.
has number that decreased more than	Checks if the numeric value has decreased by more than the specified amount.
has number that increased more than	Determines if the numeric value has increased by more than the specified amount.
has number that decreased more than percentage (%)	Verifies if the numeric value has decreased by more than the specified percentage.
has number that increased more than percentage (%)	Checks if the numeric value has increased by more than the specified percentage.
length is less than	Applies to texts whose length (number of characters) is less than the specified amount.
length is greater than	Useful for texts whose length is greater than the specified number of characters.
matches regular expression	Allows for matching text against a specified regular expression pattern. This can be used for case-sensitive matching. gim flags can be added based on the need. g stands for global, i stands for insensitive and m stands for multi. Usage: matches regular expression \w+ It checks the occurrence of 1 or more word character (a-z, A-Z, 0-9, _).
doesn't match regular expression	Used for cases where the text should not match the specified regular expression pattern.
doesn't match any previous text	Used for cases to track if latest text change differs from any previous updates in the change history. Use case

You can include multiple conditions to meet your specific needs, separating them with either AND or OR. Use AND to require that all conditions are true. Use OR to require that at least one condition is true.

Notes:

1. By default, conditions are case insensitive in Distill.
2. Numeric conditions (less than, greater than, etc) work well if the selection contains 1 numeric content. In case of multiple numbers in the selection, numeric condition will evaluate to each number in the selection and return to True on any match.

Number Format For Numeric Conditions

To ensure accurate evaluation of numeric data, our system defaults to the United States numeric format (e.g., 1,000.00 for one thousand). If your data uses a different numeric format, such as the European format (e.g., 1.000,00 for one thousand), please select the appropriate format from Conditions. This setting ensures that numeric comparisons and calculations are performed correctly according to your regional standards."

How to find out which condition triggered the alert?

The change history in Distill tracks all detected changes, regardless of conditions. When a change meets the criteria defined in the conditions, the following actions occur:

• An alert (email, push, etc if set) is received.
• The monitor’s status changes to unread.
• The bell icon in the change history will show the notification triggered status as shown below. You can click on the bell icon to open the condition debugger modal. This will show result of condition evaluation. When the final result of evalutation is True, actions are triggered.

The following image shows up after clicking on the bell icon from the change history for a notification triggered case.

Conversely, if a change does not satisfy the condition criteria, bell icon will not show the alert as triggered. You can click on the bell icon to see further details on the condition evaluation.

Common Use-Cases for Text Alerts

Alert on text additions only

• Added text is not Empty

Do not alert on minor changes

• Added Text length is greater than 10.
• This condition will check if the character length is greater than 10.

Alert on price increase only

Added Text has number that increased more than 0

Case-sensitive match

Added text matches regular expression your-keyword with gm (Flag)

Alert on Alphabet changes only

• Added text matches regular expression [a-zA-Z]{1,} with gim (Flag)
• This will alert for changes involving alphabets without considering numeric or date changes. The above regular expression will match one or more occurrence of the alphabet characters.

Numeric change alerts

• Added text matches regular expression [0-9]{1,}
• The above regular expression will match one or more occurrence of the numeric characters.

Adding multiple keywords for change alert

• Added Text matches regular expression keyword1|keyword2|keyword3|keyword4 with gim(Flag)
• All keywords are separated using a pipe (|) while using the regular expression with gim flag. You can also use multiple condition using contains condition type.

Alert if the latest update is unique in change history

• doesn't match any previous text operator can be used to check if the latest text change differs from any previous updates in the change history. E.g: While monitoring a list of job postings, in cases where jobs are intermittently added or removed, this operator filters out unnecessary alerts caused by these changes.

Example: Here is a screenshot of the condition:

For the above condition, no alerts will trigger for the latest change, as it fully matches a previous entry in the change history.

Track only net changes in text and ignore re-ordering or movement of text

• Net Added is not empty. Eg: Previous text: ABC , Changed text: BDC. This will trigger change alert only for the added text “D” and ignores change in position of “B”, “C” and deletion of “A”. If ABC changes to CAB there is no alert as there is only change in order and no content is added or deleted.
• Net Deleted is not empty. Eg: Previous text: ABC , Changed text: BDC. This will trigger change alert only for the deleted text “A” and ignores change in position of"B", “C” and newly added text “D”.
• Compound condition of both of the above will get alerts for net added and net deleted text “D” & “A” respectively and will ignore change in position of “B” & “C”.

Conditions in V1 (Legacy Version)

Selections from the web page can contain characters, numeric or other data types. In add conditions, you can choose either “Text” , “Added text” and “Previous text” from the drop-down as shown below in the image.

“Text” and “Added text” refers to current version of text and additions that could have been made to it. “Previous text” refers to the second most recent version of the text selected in the page. For example, if the originally text was “hello world” that changed to “hello world!”, the values used in conditions will be as follows for each type of text:

• Text: hello world!
• Added text: world!
• Previous text: hello world

Selecting the type of text will depend on your use-case. “Added text” makes sense when you are monitoring a list of items. For example, you are monitoring IMDB top 5 movie of the month which keeps on changing. Currently, top 5 movies are: alpha, beta, gamma, delta, omega. You want to get notified when “zeta” appears in the list. After some time it changes to alpha, beta, delta, zeta, omega. Here if you add condition text has zeta or Added text has zeta both will work. After some time it changes to alpha, beta, delta, zeta, omega, gamma. If the condition is text has zeta, then you will get notification. But this notification is redundant as you received the notification for appearance of zeta earlier. You will not receive notification if you choose “Added text”. So, here Added text has zeta is a better choice.

Another dropdown list in the condition window shows various option as shown below:

• is not empty : The text/selection sometimes goes empty and you won’t be interested in notification for those empty texts. This condition comes handy in those cases.
• has: You can use it to match the text with certain text (word, number). When that certain text appears in your monitor, you will get notification.
• does not have: It works similarly like “has” condition.
• has number less than (<): It can be used when your monitored selection is of numeric type.
• has number more than (>): It is used for numeric type selection.
• has number that decreased more than : Only used for numeric data type selection. Suppose your monitor has text “50”. You want notification only when this text goes below 40. You can use this condition has number that decreased more than 10.
• has number that increased more than: This works in a similar way as above condition.
• matches regular expression: You can use this condition to match regular expression in your text. This can also be used to match case sensitive text.

Compound Conditions (V1)

You can use compound conditions for multiple combinations of conditions. For example, your text currently is “50”. You want to get notified either if it goes above “60” or it stays between “41-45”. The image given below shows this case:

You can add compound conditions by clicking on down caret icon adjacent to add condition button as shown below:

Troubleshooting Common Issues

To effectively troubleshoot and refine your alert conditions, follow these steps:

1. Review Change History: Access the change history for your monitor to understand what changes have been detected. This insight can help you identify why an alert was or was not triggered.
2. Condition Evaluation: Click on the bell icon within the change history to view how conditions were evaluated for each detected change. This can help you pinpoint inaccuracies in condition setup.
3. Modify Conditions: Based on your review, adjust your conditions to better match your monitoring needs. Consider simplifying or specifying your selections for more precise monitoring.

FAQ

Keyword is showing on the page but the alert did not trigger

• Alerts trigger when changes are detected on a monitored page. If the page content remains unchanged, alerts will not be triggered, even if the keyword exists on the page. This ensures alerts are meaningful and related to new changes only.

Not receiving an alert even after removing conditions

• It’s possible that global conditions are affecting your alerts. Check if you have set any global conditions which apply to all monitors.

Numeric Conditions are triggering unwanted alerts

• Numeric conditions are best used when the selection targets a single numeric value. If multiple numbers are present, the condition evaluates each number independently, potentially causing false alerts. To avoid this, refine your selection to include only the numeric value of interest. This will ensure accurate and relevant alerts.

How to ignore changes triggered due to change in position of text?

• Use Net Added is not empty and Net Deleted is not empty as condition. These operators ignore changes in text fragments that are due to text movements and reordering. It gives you alert only when there are net changes in the tracked section.

How to ignore Flip-Flopping Text Changes?

• Use text doesn't match any previous text. Please check this for more details.