> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/engage/-MGi9-KKLwnWfoD36Ot6/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/engage/-MGi9-KKLwnWfoD36Ot6/fundamentals/qualifiers.md). # Qualifiers Qualifiers are specific characteristics used by Engage to identify the visitors who access your website and sort them into one of the three [meter levels](/engage/-MGi9-KKLwnWfoD36Ot6/fundamentals/glossary.md#meter-level) (free, metered, or premium), as well as to control the settings within conversations and actions. \ \ There are four types of qualifiers in Engage: [meter qualifiers](/engage/-MGi9-KKLwnWfoD36Ot6/fundamentals/meter-rules/qualifiers.md), conversation [expiration types](/engage/-MGi9-KKLwnWfoD36Ot6/fundamentals/campaigns/conversations/expiration-types.md), conversation[ filters](/engage/-MGi9-KKLwnWfoD36Ot6/fundamentals/campaigns/conversations/filters.md), and action [criteria](/engage/-MGi9-KKLwnWfoD36Ot6/fundamentals/campaigns/actions/who.md#criteria). {% hint style="info" %} Every time the visitors refresh the page, Engage is re-checking them against the qualifiers, and, if any matching changes are detected, the relevant settings are applied. {% endhint %} Different types of qualifiers are available on different levels of the system. The table below is an overview of all the default qualifiers currently available in Engage 2.7.0, as well as the levels where they can be applied. ## Qualifiers available in Engage from V2.7.0 {% tabs %} {% tab title="Meter Qualifiers" %} Meter Qualifiers are those qualifiers that are available in the Meter Level. The primary job of a Meter qualifier is to sort a visitor into one of the **meter levels**: free, metered, or premium. Below is the list of Meter Qualifiers available in Engage Admin from V2.7.0: 1. Ad Block 2. Article Age (from 2.8.6 only) 3. Blocked Cookies/Local Storage 4. Blocked Third Party Cookies (from 2.8.5 only) 5. Browser Detection 6. Coming From Social (from 2.8.6 only) 7. Country 8. Engagement Rate 9. Engagement Rate Percentile 10. Incognito Mode 11. IsEuMember 12. JS Var (this qualifier is renamed to Javascript from 2.8.3) 13. Mather Segments (from 2.8.6 only) 14. Meta 15. Newsletter Session 16. Registration Walls 17. Start\&End Dates (from 2.8.3 only) 18. Subscription Creation Date (from 2.8.6 only) 19. Subscription Expiration 20. URL Mask 21. URL Param (from 2.8.5 only) 22. User Interests 23. User State {% endtab %} {% tab title="Expiration Types" %} Expiration Types are qualifiers that determine the expiration of a conversation. These qualifiers act at the Conversation Level. Below is a list of available Expiration Type Qualifiers in Engage Admin starting from V2.7.0. 1. AB Experiment (from 2.7.1 only) 2. AdBlock Detected 3. Blocked Cookies/Local Storage (from 2.8.6 only) 4. Coming From Social (from 2.8.6 only) 5. Conversation Views (from 2.8.6 only) 6. DayTime 7. Engagement Rate 8. Incognito Mode (from 2.8.6 only) 9. Javascript 10. Mather Segments (from 2.8.6 only) 11. Meter Views (from 2.8.6 only) 12. Newsletter Reader (from 2.8.6 only) 13. Newsletter Session (from V2.8.6 only) 14. Registration Walls 15. Start\&End Dates (from 2.8.6 only) 16. Subscription Expiration 17. Time (from 2.8.6 only) 18. Url Mask (from 2.8.6 only) 19. Url Param (from 2.8.6 only) 20. User State 21. Visits In the Last Days (from 2.8.6 only) {% endtab %} {% tab title="Conversation Filter" %} These qualifiers select or filter a conversation from a list of conversations configured in the Admin. In other words, the values of these qualifiers determine which conversation becomes the currently active one from the list of conversations. Below is the list of Conversation Filter Qualifiers available in Engage Admin starting from V2.7.0. 1. AB Testing (from 2.7.1 only) 2. Ad Block 3. Article Age (from 2.8.6 only) 4. Blocked Cookies/Local Storage 5. Blocked Third Party Cookies (from 2.8.5 only) 6. Browser Detection 7. Coming From Social (from 2.8.6 only) 8. Country 9. DayTimeFilter 10. Engagement Rate 11. Engagement Rate Percentile 12. Geo 13. Incognito Mode 14. IsEuMember 15. Javascript 16. Mather Segments (from 2.8.6 only) 17. New Visitor 18. Newsletter Reader 19. Newsletter Session 20. Registration Walls (from 2.8.6 only) 21. Start\&End Dates (from 2.8.3 only) 22. Subscription Creation Date (from 2.8.6 only) 23. Subscription Expiration 24. URL Mask 25. URL Param (from 2.8.5 only) 26. User Interests 27. User State 28. Visits In The Last Days {% endtab %} {% tab title="Action Criteria" %} Action Criteria are qualifiers that determine whether a configured Action type (e.g., Banner, Small Info Box, Modal, Messaging, Paywall, Newsletter, etc.) should be displayed to the reader. These qualifiers operate at the Action Level. Below is the list of Action Criteria Qualifiers available in Engage Admin from V2.7.0. 1. AB Testing (from 2.7.1 only) 2. Ad Block 3. Article Age (from 2.8.6 only) 4. Blocked Cookies/Local Storage 5. Blocked Third Party Cookies (from 2.8.5 only) 6. Browser Detection 7. Coming From Social (from 2.8.6 only) 8. Conversation Views 9. Country 10. DayTimeCriteria 11. Device type 12. Engagement Rate 13. Engagement Rate Percentile 14. EZ Pay 15. Free Article Remaining (from 2.8.6 only) 16. Geo 17. Incognito Mode 18. IsEUMember 19. Javascript 20. Mather Segments (from 2.8.6 only) 21. Meta Keyword 22. Meter Views 23. New Visitor 24. Newsletter Reader 25. Newsletter Session 26. Operating System (from 2026.1 only) 27. Registration Walls (from 2.8.6 only) 28. Start\&End Dates (from 2.8.3 only) 29. Subscription Creation Date (from 2.8.6 only) 30. Subscription Expiration 31. URL Mask 32. URL Param (from 2.8.5 only) 33. User Interests 34. User State 35. Visits In The Last Days {% endtab %} {% endtabs %} {% hint style="info" %} **Note**: The qualifiers Engagement Rate, Engagement Rate Percentile, and User Interests will work effectively only if you have an integration with G2 Insights platform. {% endhint %} {% hint style="info" %} **Note**: Some of the Engage qualifiers can be applied in multiple areas of Engage Admin. For instance, the qualifier 'Blocked Cookies/Local Storage' can function as a Meter qualifier, Action criterion, Conversation filter, and Expiration type. The behavior of this qualifier varies depending on its use. When employed as a Meter qualifier, the qualifier's value categorizes the user and assigns the meter level. If used as an Action criterion, the execution of the configured action type is determined by the qualifier's value. When serving as a Conversation filter, the qualifier value filters out conversations. When utilized as an Expiration type, the qualifier's value governs the expiration of an active conversation. {% endhint %} ## **Ad Block** **How it works:** Identifies visitors based on whether or not they are using an ad-blocking browser extension when accessing your website. **Settings:** Detected (if the visitors are using an ad-blocking extension) or Not Detected (if no such extension is used). ## **Blocked Cookies/Local Storage** **How it works:**\ Targets visitors whose browser settings have blocked cookies or local storage when accessing your website. {% hint style="info" %} With this cookie, Engage can verify the disabled status of the first-party cookies and local storage **only**. This qualifier does not check whether the third-party cookies are blocked or not in the browser. {% endhint %} **Settings:**\ **True** (cookies and/or local Storage are disabled) or **False** (cookies and/or local storage are enabled). ![](https://2189759649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGi2iapIi_G2XvKxDCc%2Fuploads%2F4aB2MqxpNS4grUjZarUb%2Fimage.png?alt=media\&token=ad10f5e5-82d1-40fb-9bd0-4f7bc93a84ab) If the qualifier value is set to be True in Engage admin and the cookies and/or local storage are blocked in the visitor's browser, then the corresponding meter level action will be displayed to the visitor. The logic of the qualifier is depicted in the following table: | Qualifier Value in Admin | Setup in the browser | Result on the Plugin | | ------------------------ | -------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | | True | ‘Block all Cookies’ option selected (Cookies are blocked in the browser) | Qualifier passes and the configured Action type will be displayed to the user. | | False | ‘Block all Cookies’ option selected (Cookies are blocked in the browser) | Qualifier does not pass and the configured Action type will not be displayed to the user | | True | ‘Block all Cookies’ option not selected (Cookies are not blocked in the browser) | Qualifier does not pass and the configured Action type will not be displayed to the user. | | False | ‘Block all Cookies’ option not selected (Cookies are not blocked in the browser) | Qualifier passes and the configured Action type will be displayed to the user. | The different combinations of this setting can be summarized as follows:\ Qualifier (value = True), Cookies blocked in browser -> Action will be displayed\ Qualifier (value = True), Cookies not blocked in browser -> Action will not be displayed\ Qualifier (value = False), Cookies blocked in browser -> Action will not be displayed\ Qualifier (value = False), Cookies not blocked in browser -> Action will be displayed ## **Browser Detection** **How it works:**\ Identifies visitors based on the type of browser they are using.\ \ **Settings:**\ Select one or more of the commonly used browsers by checking the relevant boxes: Chrome, Edge, Facebook, Firefox, IE, Safari, Other (includes any other/unidentified browser). Select **Contains** to target the visitors who are using the indicated browser(s) and **Does Not Contain** for those who don't. ## **Conversation Views** **How it works:**\ Counts the number of page views in the course of a particular conversation. This criterion can be used to limit the number of free articles for a particular category of visitors. Each time a conversation expires and the visitor enters the next conversation, the count will be renewed. **Settings:**\ The operators **(=, ≠, <, >, >, >=, <=)** allow you to precisely set up the order of actions, as well as relationships between different conversations depending on the number of page views. ## Country **How it works:**\ Identifies visitors based on their country of residence at the point of accessing your website. **Settings:**\ To add one or multiple countries, simply start typing a country’s name in the field **Countries**, then hit **Enter** to select the autocompleted result. Select **In** (for when the visitor is *in* the given country while accessing your website) and **Not in** (for when the visitor is *not* in the given country while accessing your website). There is also an option to **Include Unknown Country** further below in case no country could be identified. ## DayTime **How it works:**\ Allows you to pick a specific time of day when your visitors are accessing your content for your action to be shown within this timeframe. **Settings:**\ Select **In** (to target the visitors that are active within this timeframe) or **Not In** (to target the visitors who are active during the day, except for the specified timeframe). Enter the time range into the respective fields following the **hh:mm** format. ## Device Type **How it works:**\ Identifies a specific device type being used by the visitors when accessing your website. **Settings:**\ The available options include **Mobile**, **Tablet**, or **Desktop**. You can also select **≠** as your **Device Type** operator to specify that the rule should apply to visitors who are *not* on mobile, tablet, or desktop. ## **Engagement Rate** {% hint style="info" %} **Engagement Rate** and **Engagement Rate Percentile** will be available only if you have integration with the **G2 Insights & CDP** platforms. {% endhint %} **How it works:**\ Identifies visitors based on the level of their engagement when interacting with your website. Engage receives the engagement rate value in a response from **G2 Insights.** The received value is then compared to the value that you enter below.\ \ **Settings:**\ Enter the relevant engagement rate value (from 0 to 1) and select one of the operators (**>, >=, <, <=, =**) from the drop-down menu. ## **Engagement Rate Percentile** **How it works:**\ The **Engagement Rate Percentile** can be defined as the **Engagement Rate** value compared to the rest of the values in the dataset. This value will be converted into a different one to reflect the global engagement situation on your website.\ For instance, a visitor's Engagement Rate value equals 0.9. If the rest of the visitors have Engagement Rate values higher than 0.9, the Engagement Rate value of 0.9 would be considered the lowest value in the dataset. The Engagement Rate Percentile in this example would equal to 0 since 100% of other visitors have an Engagement Rate value that is higher than 0.9.\ \ **Settings:**\ Enter the relevant Engagement Rate Percentile value (from 0 to 1) and select one of the operators (**>, >=, <, <=, =**) from the drop-down menu. ## EZ Pay **How it works:** \ Targets visitors based on whether or not they have set up EZ-Pay payments. **Settings:**\ **Yes** (the visitor uses EZ-Pay) or **No** (the visitor doesn’t use EZ-pay). ## **Geo** **How it works:**\ Identifies visitors by their ZIP codes. **Settings:**\ Add one or multiple ZIP codes, or use a ZIP code mask using the asterisk (\*) wildcards. There is also an option to **Include Unknown ZIP** code in case no ZIP code could be identified. **Include Unknown ZIP** answers the question "should an unknown zip code be included in the list of Zipcodes above?" | **Qualifier** | **Include unknown zip** | **Result** | | ------------- | ----------------------- | ------------------------- | | In | Yes | Includes unknown zip code | | In | No | Excludes unknown zip code | | Not In | Yes | Excludes unknown zip code | | Not In | No | Includes unknown zip code | ![](https://2189759649-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGi2iapIi_G2XvKxDCc%2F-MkDY1brZI1kFSyXCGRX%2F-MkDYkfLF4eYFzuX6fV1%2Fimage.png?alt=media\&token=0f7b1ec3-b151-42ba-924c-ecb750b54943) ## **Incognito mode** **How it works:**\ Identifies visitors based on whether or not the incognito mode is activated in their browser. **Settings:**\ **Detected** (the incognito mode is enabled) or **Not Detected** (the incognito mode is disabled). ## IsEUMember **How it works:**\ Targets visitors based on whether or not they are accessing your website from a country that is a member of the European Union. It differs from the **Country** qualifier in that it is limited to the specific list of countries belonging to the EU. **Settings:**\ **True** (in case the visitor is currently in an EU member country) or **False** (in case the visitor is currently *not* in an EU member country). ## JS Var/JavaScript **How it works:**\ Detects specific JavaScript variables or functions on the page to categorize visitors who are accessing this page. You can use default variables or functions, or customize your own. This qualifier can be used for a variety of purposes. For instance, if your browser's local storage had a key named `myKey` containing the string `a,b,c`, here is how you could set up the qualifier to check whether the string contains the substring `a`: ![Using JavaScript qualifier to look for a string](https://2189759649-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGi2iapIi_G2XvKxDCc%2F-MI3xetBuf3fORWX5GrL%2F-MI450wo5S0n_KevZ5hr%2Fengage_js_qualifier.png?alt=media\&token=597083c7-ec10-458f-9c02-6b8ce6b2bad1) The JavaScript qualifier can also be used with functions. For example, you could enter the function below into the field **JS Var of Func** to look for a URL parameter in a link using the JavaScript location search property: ```javascript function getQueryString() { const queryString = window.location.search; const urlParams = new URLSearchParams(queryString); return urlParams.get('queryStringKey') == 'queryStringValue' } ``` **Settings:**\ The variables holding different data types can be analyzed using a range of operators: **=, ≠** (for strings and numbers), **>, <, >=, <=** (for numbers), as well as methods like **In, Not In, Contains, Does Not Contain**, **Start With, End With, Intersect, Does Not Intersect**. ## Meta Keyword **How it works:**\ Categorizes the page content based on meta keywords used in that page’s HTML. In order for this criterion to be applied, the page must contain a meta tag with keywords (``), which can be found inside the `` element of the page. **Settings:**\ Requires the value of the content attribute within the meta tag. One or multiple meta keywords (separated with commas) can be evaluated. The available operators for this qualifier are **=** or **≠**. ## Meter Views **How it works:**\ Contrary to **Conversation Views**, **Meter Views** are counted each time the visitor accesses an article pertaining to a particular meter level. The **Meter Views** are counted separately for the free, metered, and premium meter levels. Thus, the **Meter Views** criterion can be used to keep track of your visitors' article views (on a particular meter level) regardless of what conversation currently applies to them. **Settings:**\ Use the operators **=, ≠, <, >, >=, <=** to specify the desired number of views. ## Newsletter Reader **How it works:**\ Tracks the visitors who subscribed to your website's newsletter and were redirected to your website after interacting with the newsletter content (i.e. clicking on a link or a button leading back to your website). The [URL parameters](/engage/-MGi9-KKLwnWfoD36Ot6/fundamentals/glossary.md#url-parameters) of such visitors are saved in the local storage of the browser and do not expire after the page is refreshed, or the browser is restarted. **Settings:**\ **True** (the visitor came after reading your newsletter) or **False** (the visitor did not read your newsletter). ## Newsletter Session **How it works:**\ Tracks the visitors who subscribed to your newsletter and got redirected to your website during this particular session. Provides the same functionality as [**Newsletter Reader**](/engage/-MGi9-KKLwnWfoD36Ot6/fundamentals/qualifiers.md#newsletter-reader), with one distinction: the visitor’s URL parameter will be saved in the session storage of the browser instead of the local storage. This means that the saved data survives a page refresh (but not closing the tab or the browser window). **Settings:**\ **True** (the visitor came after reading your newsletter) or **False** (the visitor did not read your newsletter). {% hint style="info" %} In order for Engage to determine that the visitor was redirected to your website after having read your newsletter, you’ll need to append the **G2 Insights** [URL parameter](/engage/-MGi9-KKLwnWfoD36Ot6/fundamentals/glossary.md#url-parameters) `g2i_source=newsletter`to any links in your newsletter that lead back to your website. Additional parameters that you can use for more detailed analytics are  `g2i_campaign=[CampaignName]`(to track your campaigns) and`g2i_eui=[encryptedUserEmail]`(to trigger a network request for the visitor's unencrypted email address). \ Engage will recognize these parameters and create the relevant cookie files for these visitors. {% endhint %} ## New Visitor **How it works:**\ Targets visitors who are accessing your website for the first time. Engage checks whether it's the visitor’s first view on a particular meter level. Visitors can be considered new visitors once on each meter level: free, metered, and premium. **Settings:**\ **Yes** (it's the visitor's first view in terms of the relevant meter level) or **No** (it's not the visitor's first view in terms of the relevant meter level). {% hint style="info" %} Engage backs up the visitor's meter views by sending them to the server (this occurs on every third meter view). There are two ways the visitor's views can be reset: if you check **Clear All Data** when publishing your current configuration *or* if the visitor you clears their browser cache and cookie files before reaching their third meter view on your website (in which case Engage would identify them as a **New Visitor** again). {% endhint %} ## Operating System **How it works:** Targets visitors who are accessing your website using a specific Operating System. **Settings:** The available values for this qualifier are iOS, Windows, Android, macOS, and Others. If you want to configure an Action template for end users who do not use macOS, Windows, iOS, or Android, select the '*Others*' option. **Use Case**: You can configure Action templates based on the end user’s **Operating system** and/or **Device type**. This enables different paywalls, modals, or banners to be displayed depending on the user’s device type and operating system.

Action Filter Qualifier - Operating System

## Promise **How it works:**\ Uses a special JavaScript object called promise. Promise relies on the result of an operation running on your webpage at any given point in time. Different settings may apply depending on whether the promise has been fulfilled (i.e. if the operation was successfully completed and a specific value was returned) or rejected (the operation failed or returned an error).\ \ **Settings:**\ Enter the name and the value of your promise variable into the relevant fields. Select the appropriate operator (**=, ≠, <, >, >=, <=**). ## Registration Walls **How it works:**\ This qualifier is only used as an[ expiration](/engage/-MGi9-KKLwnWfoD36Ot6/fundamentals/campaigns/conversations/expiration-types.md) type for [conversations](/engage/-MGi9-KKLwnWfoD36Ot6/fundamentals/campaigns/conversations.md). Once the visitor has completed the registration on your website, Engage will create a cookie file (isActCr) to identify them. \ The **Registration Walls** expiration type can be used to move the newly registered visitors to another conversation (for instance, if you would like to grant them extra free articles after the registration). \ \ **Settings:**\ Next to the **Equals** option, select either **True** (to identify the visitors who have registered) or **False** (to identify the visitors who have *not* registered). **Note**: From V2.8.6, this qualifier is not only available as an Expiration type but also as a Meter Rule qualifier, a Conversation Filter, and an Action Criterion. This qualifier allows you to target visitors based on the presence or absence of the 'isActCr' cookie. The 'isActCr' cookie is generated only when a user **registers** on the news website through a Paywall and the cookie automatically expires within 24 hours.

Registration Walls Qualifier as an Action Criterion

## Start\&End Dates This qualifier is available at Meter Rule, Conversation and Action levels from version 2.8.3 onwards. With this qualifier, visitors will only pass the filter if current date is between Start and End dates. Both dates are optional but one of them should be populated. ![Start\&End Dates Qualifier](https://2189759649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGi2iapIi_G2XvKxDCc%2Fuploads%2F8EPh6VaaTAfxOI5ihk1f%2Fimage.png?alt=media\&token=3db31257-3c74-45d6-a707-d8e018437d13) **Note**: From V2.8.6 onwards, the 'Start\&End Dates' qualifier has been enhanced to consider the dates that are not WITHIN the specified date range. A new Condition parameter (Within/Not Within) has been added to the qualifier.

Start&End Dates Qualifier with the Condition Parameter

If the ‘Within’ condition is selected, the dates that fall within the specified date range of start & end dates will be considered. If the ‘Not Within’ condition is selected, the dates that do not fall within the specified start & end date range will be considered. For more info, refer the table below: | Condition Selected | Dates Populated in the Admin | Time period considered | | ------------------ | ----------------------------------------------- | ------------------------------------------------------------------------ | | Within | Both Start & End dates entered in the Admin | Greater than or equal to Start date and lesser than or equal to End Date | | Within | Only the Start Date entered in the Admin | Greater than or equal to the Start Date | | Within | Only the End Date entered in the Admin | Lesser than or equal to the End Date | | Not Within | Both Start & End dates are entered in the Admin | Lesser than the Start date and greater than the End Date | | Not Within | Only the Start Date entered in the Admin | Lesser than the Start Date | | Not Within | Only the End Date entered in the Admin | Greater than the End Date | For example, if the ‘Within’ condition is selected with a Start Date of 01 Dec 2023 and an End Date of 31 Dec 2023, then the selected Action in the ‘What’ section of the Conversation will be in effect for the user from 01 Dec to 31st Dec 2023 (both start and end dates inclusive). Similarly, if the 'Not Within' condition is selected with the Start Date of 01 Dec 2023 and End Date of 31st Dec 2023, the specified action will be restricted to the user from 01 Dec 2023 to 31st Dec 2023 (both start and end dates exclusive). This means that the specified action will be effective for the user only on a date that is lesser than 01 Dec 2023 or greater than 31st Dec 2023. {% hint style="info" %} It is mandatory that either Start Date or End Date must be entered for the proper functioning of this qualifier. {% endhint %} This enhancement allows users to specify a date range during which a particular action can either exclusively be offered to or restricted from readers/visitors, based on your defined conditions. ## Subscription Expiration #### **How it works:** **\`**Targets the visitors who subscribed to your website (i.e the ones whose user state object contains `"Subscribed"`) and checks the exact date of their subscription expiration. #### **Settings:** This qualifier needs some entries in fields such as Condition, Value, Qualifier, etc. for it to work. **Condition -** This allows users to select "In" and "Not in" options. These options help the users to have all possible combinations of the Subscription Expiration Options. ![Is and Is Not Conditions applied in different Qualifier sets](https://2189759649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGi2iapIi_G2XvKxDCc%2Fuploads%2F2EsgifDnMjXjqoZxNsN3%2FIs%20and%20Is%20not.png?alt=media\&token=1511735d-70ab-4b66-b64a-e98faef617d0) For example, the above Subscription expirations are: Is Subscription Expiration (happening) Within The Next 3 Days? - Returns the list of the visitors with subscription expiring within the next three days. Is Not Subscription Expiration (happening) Within The Next 3 Days? - Returns the list of the visitors with subscription not expiring within the next three days. **Value** - In this field you can select one of the following **Subscription Expiration Options:**\ \ **1. On:** \ Use this option to target visitors whose subscription expires on a particular day. Select the relevant expiration date from the calendar in the **Value** field. Example: Using "On 30/11/2021" will target visitors with Subscription Expiration Date on November 30th only. ![Subscription Expiry: On](https://2189759649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGi2iapIi_G2XvKxDCc%2Fuploads%2FJxXJpLflTKvAt2DbJ9RI%2Fimage.png?alt=media\&token=28eb7b57-5392-4887-bd8c-af14ae5f6deb) **2. Exactly In:** \ Use this option to target visitors whose subscription expires once a particular amount of time has elapsed. Select the appropriate units of time from the drop-down menu under **Value** (**Days, Weeks,** or **Months**), then enter the time value into the adjacent field. Example: When using "Exactly In 10 days", on November 20th all visitors with Subscription Expiration Date on November 30th will be targeted "Exactly In" allows Value = 0 to target visitors whose subscription expires "today". This feature specialty is available from version 2.8.3 onwards. ![Subscription Expiry: Exactly In](https://2189759649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGi2iapIi_G2XvKxDCc%2Fuploads%2F04pRZWE5zDYz88Yh5imc%2Fimage.png?alt=media\&token=eba3b955-3e8f-44cb-9c69-37a38c1f53a5) **3. Within The Past & Exactly Ago:** \ Use this option to target visitors whose subscription has expired in the past. Select the appropriate units of time from the drop-down menu under **Qualifier** (**Days, Weeks,** or **Months**), then enter the time value into the adjacent field. Example: When using "Within The Past 3 days", on November 20th targets the visitors whose subscription has expired on November 17th, 18th and 19th. Whereas, using "Exactly....Ago 3 days" on Nov 20th targets the visitors whose subscription expired on Nov 17th.
Within The Past Exactly..Ago
**4. Within The Next** Use this option to target visitors whose subscription expires at any moment within the specified time range. Select the appropriate units of time from the drop-down menu under **Qualifier** (**Days, Weeks,** or **Months**), then enter the time value into the adjacent field. Example: When using "Within 3 days" on November 20th will target all visitors with Subscription Expiration Date on November 21st, 22nd, and 23rd. {% hint style="info" %} If a visitor has multiple subscriptions, Engage will use the`ExpirationDate`property containing the latest date. {% endhint %} {% hint style="info" %} Clients can also use Javascript qualifier to get the expiration Date from this local storage value: `pathConnext.Storage.GetUserData().DigitalAccess.Subscription.ExpirationDate` {% endhint %} {% hint style="info" %} **Test with Engage Debug Panel**: CUSTOM TIME field in the Engage Debug Panel can now be used to test the Subscription Expiration Date qualifier. {% endhint %} ## **Time** **How it works:**\ This qualifier is only used as an[ expiration](/engage/-MGi9-KKLwnWfoD36Ot6/fundamentals/campaigns/conversations/expiration-types.md) type for [conversations](/engage/-MGi9-KKLwnWfoD36Ot6/fundamentals/campaigns/conversations.md). It allows you to determine when a particular conversation for a specific category of visitors expires. \ \ **Settings:**\ Click on **Type** next to the **Expiration** option to specify the units of time (Minutes, Hours, Days, Weeks, Months, Years), and on **Value** to enter the number of those units. {% hint style="info" %} Modifying the Expiration would not reset the users. It would just shift the expiration date for them. **Example**: Conversation A has Expiration = 30 days, and for a user that conversation would expire on November 1st. If an Admin extends the expiration from 30 to 60 days, the user's conversation will expire on December 1st and user will not get views reset until December 1st. {% endhint %} ## **URL Mask** **How it works:**\ URL Mask qualifier is available as a Meter Qualifier, Conversation Filter, and an Action Criterion. It allows your settings to apply to any dynamic elements of a URL by means of creating a URL mask. This qualifier can act as a Subdomain qualifier with ease. **Settings:** **Qualifier**: Select the operators "=" or "≠" from the drop-down.\ **Value**: Paste the relevant URL into the Value field and replace any changeable parts of it with an asterisk wildcard (\*). For instance, `http://www.example.com/*` would refer to any subdirectory or multiple subdirectories on the website, like `http://www.example.com/sports/basketball` or `http://www.example.com/sports/basketball/article1.html.` **Note**: From V2.8.6, the URL Mask qualifier has been enhanced to also function as an Expiration type. Furthermore, this qualifier now accepts multiple URLs separated by commas in the value field, including wild card characters. If you select the '=' operator, the qualifier will pass if the current browser URL matches either the single URL or any of the URLs specified in the value field, as the case may be. If you choose the '≠' operator, the qualifier will pass if the current browser URL does not match either the single URL or any of the URLs specified in the value field, as the case may be. {% hint style="info" %} Note: The system will continue to consider wildcards in each URL, even if multiple URLs are included in the Value field, following the same behavior as when a single URL is used. {% endhint %} **Use Case**: The URL Mask qualifier can be useful when you need to deal with a large number of URLs. For example, suppose you have a list of 100 URLs, all of which should fall under the FREE meter level. In this case, if the URLs belong to the same domain, they all can be represented using a single URL mask as **.* If the URLs are different, they can be mentioned in the Value field, separated by commas such as \_*\_, , , \*, etc.

URL Mask qualifier accepting multiple URLs in the Value field

{% hint style="info" %} **Note**: Note: The image above is for representation purposes only. Please remember to include the '[https://www](https://www/).' prefix for each URL or URL mask entered in the Value field. {% endhint %} ## **User Interests** {% hint style="info" %} **User Interests** will be available only if you have integration with the **G2 Insights** platform. {% endhint %} **How it works:**\ Fetches the data from G2 Insights related to your visitors' interests, divided into the following nine categories: "Travel", "Crime", "Food and drink", "Science", "Sports", "Style and beauty", "Entertainment", "Politics" and "Business". **Settings:**\ Select the relevant interest category and operator (**>, >=, <, <=, =**) from the respective drop-down menus, then enter the interest rate value (in a range between 0 and 1). ## **User State** **How it works:**\ Detects visitors based on several different user states defined across the system. **Settings:**\ Use the operators **=** or **≠** to specify in which User State are or are not your visitors when accessing your website.: * **Logged In:** Logged in into Engage, but has no subscription. * **Logged Out** * **Subscribed:** Logged in into Engage, and with a Premium subscription (has access to all articles) * have **No Active Subscription:** Visitor has subscription/s, but they are no longer active. * or are **Subscribed Not Entitled:** The visitor holds a valid subscription for one or more content sections on your website. However, this subscription does not grant the visitor access to articles from other paid sections on the current site. For instance, the reader may have a paid subscription for the Sports content but is not entitled to access paid articles in Lifestyle, Travel, and other sections. User States are exclusive from Engage Admin perspective. Example: If a visitor is Subscribed, it will not be picked up by the filter **User State** = **Logged In**. Despite logically speaking a **Subscribed** visitor is also Logged In, Engage will always consider the most restrictive User State. So, in the example of filtering by **User State** = **Logged In**, visitors with **User State** **Subscribed**, **No Active Subscription,** or **Subscribed Not Entitled**, will not pass this filter**.** ![](https://2189759649-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MGi2iapIi_G2XvKxDCc%2Fuploads%2F4Qxi6h6GIZnwfa35TpOa%2Fimage.png?alt=media\&token=184ac64d-0b02-43fc-9133-cb6b165b125f) Find the relation of the User States with the Engage Authentication Events [here](/engage/-MGi9-KKLwnWfoD36Ot6/getting-started-with-engage/configuring-engage-on-your-website/configuring-the-access-buttons.md#engage-authentication-events). ## **Visits In the Last Days** **How it works:**\ Targets the visitors who have been accessing your website in the last few days. You can use it to set up specific actions to be displayed for those visitors who have been accessing your service more frequently than the others. **Settings:**\ Select the relevant operator (**=, ≠, <, >, >=, <=**) from the drop-down menu. In the field **Number of Days Visited**, enter the total number of days for Engage to establish the range to check for visits. Then, under **Within the Last Number of Days**, enter the relevant number of visits. ## Custom Qualifiers You can create your own custom qualifiers on any level of Engage. These qualifiers are your own modified versions of the [default qualifiers](/engage/-MGi9-KKLwnWfoD36Ot6/fundamentals/qualifiers.md). This feature may come in handy if you are using many qualifiers with identical settings and would like to speed up configuring your Engage flow. To add a custom qualifier, navigate to **Management → Custom Qualifiers** on the side panel of your Engage dashboard. Click **+New** on the top right to add a custom qualifier. A new panel will appear at the bottom of the page where you can configure your qualifier options: ![](https://2189759649-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGi2iapIi_G2XvKxDCc%2F-MNSuBH4Xn8c846pzHEI%2F-MNSz3y-J3a9bm9bjzc8%2FScreen_Shot_2020-11-25_at_16.06.36.png?alt=media\&token=78c0acb8-60aa-4779-b395-145b7e17a302) Enter the name of your new qualifier under **Qualifier Display Name**. Click on the switcher opposite the qualifier's name to activate or deactivate your custom qualifier. The drop-down menu **Qualifier Type** allows you to select any default qualifier on any Engage level that your new custom qualifier will be based on. For example, selecting **Visits in the Last Days (from Action)** will allow us to create a qualifier based on the default qualifier **Visits in the Last Days** that will be available in the **WHO** section of our **Actions** panel. The switcher opposite the **Qualifier Type** menu allows you to enable or disable editing the custom qualifier once it is selected in the Meter Rules, Conversations or Actions. For qualifiers that use operators, you can configure which operators will be available in the additional menu below the qualifier settings. **Allow All:** make the full rage of the qualifier operators available (i.e. **=, ≠, <, >, ≤, ≥**); **Allow only equals/not equals:** the qualifier will use only **=** and **≠** as its operators. For the qualifiers that require an input, there is also an option to specify certain values that you want to be used. To do so, activate the switcher **Create dropdown of values** and enter the desired values into the field **Allowed Values**, separated by commas: ![](https://2189759649-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MGi2iapIi_G2XvKxDCc%2F-MNSuBH4Xn8c846pzHEI%2F-MNT0s36dkF7lJ7b9TDh%2FScreen_Shot_2020-11-26_at_12.52.28.png?alt=media\&token=26a2775e-e9f6-44d0-86aa-f03850f73149) Be sure to save your custom qualifier by clicking on the **Save** button. Once your custom qualifier has been created, you can use it on the relevant Engage level in the same way as you would use the default ones. ## Qualifiers available from V2.8.5 ## Blocked Third Party Cookies The new qualifier Blocked Third Party Cookies is available in Engage Admin as a Meter Qualifier, a Conversation filter, and an Action Criterion. This qualifier will check whether the option ‘Blocked third-party cookies’ has been enabled in the privacy setting on the Chrome browser of a reader/visitor. **How it works:** With this qualifier it is possible to track visitors/readers who have blocked the third-party cookies on their browsers. **Settings:** * **Value**: Select either True or False from the Value drop-down. The logic of this qualifier is summarized in the following table: | True | ‘Block third-party cookies’ option selected (Cookies blocked in the browser) | Qualifier passes and the configured Action type will be displayed to the user | | ----- | ------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------- | | False | ‘Block third-party cookies’ option selected (Cookies blocked in the browser) | Qualifier does not pass and the configured Action type will not be displayed to the user | | True | ‘Block third-party cookies’ option not selected (Cookies not blocked in the browser) | Qualifier does not pass and the configured Action type will not be displayed to the user | | False | ‘Block third-party cookies’ option not selected (Cookies not blocked in the browser) | Qualifier passes and the configured Action type will be displayed to the user | The different combinations of this setting can be summarized as follows: Qualifier (value = True), Cookies blocked in browser -> Action will be displayed Qualifier (value = True), Cookies not blocked in browser -> Action will not be displayed Qualifier (value = False), Cookies blocked in browser -> Action will not be displayed Qualifier (value = False), Cookies not blocked in browser -> Action will be displayed ## URL Param URL Param qualifier is available as a Meter qualifier, Conversation filter, and an Action criterion. **How it works:** This qualifier can serve as a filter to check whether a specified parameter passed in the URL is set to true or not. **Settings:** * **Url param**: Enter the URL parameter. * **Qualifier**: Select '=' or '≠' from the drop-down * **Value:** Enter the value of the URL Parameter. **Example**: Consider the following configuration for the URL Param qualifier. Here, the qualifier checks whether the value of the 'sso-check' parameter in the URL is set to true. If it evaluates to true, the criterion is met, and the configured action for the qualifier will be executed. For example, if the visitor's current browser URL is ',' the criterion is met, and the configured action will occur.

URL Param qualifier as an Action Criterion

## Qualifiers available from V2.8.6 ## Free Article Remaining This qualifier is available only at the Action level as an Action criterion. **How it works**: The primary function of this qualifier is to allow you to configure an Action type (such as a Banner, Paywall, or Message based on your settings) depending on the count of the Free Articles Remaining for a specific visitor/reader. You can allocate free articles to a user in the new 'Free Articles' section on the Campaigns page. The Free Article Remaining qualifier eliminates the need to set up a separate conversation and reduces the manual effort required to provide free articles to readers. {% hint style="info" %} This qualifier works effectively if it comes as the Action criteria when a Paywall is employed as an Action type in the WHAT section. {% endhint %} **Settings**: **Value**: Select True or False from the Value drop-down. The functioning of this qualifier alongside other qualifiers in the same Action is summarized in the following table. {% hint style="info" %} **Note**: To achieve the desired results, it's essential to configure this qualifier logically. {% endhint %}
Qualifier ValueFree Article Remaining CountAction type Displayed?
True0 (No free articles left)No, regardless of whether other qualifiers are passed or not (FAR Qualifier fails here)
TrueGreater than 0 (Free articles left)Yes, but only if other qualifiers also pass (FAR Qualifier is passed here)
False0 (No free articles left)Yes, but only if other qualifiers also pass (FAR Qualifier is passed here)
FalseGreater than 0 (Free articles left)No, regardless of whether other qualifiers are passed or not (FAR Qualifier fails here)
Note: The Free article count is reduced by 1 if the Action in your conversation is a Paywall.
**Example**: If you need to allocate 5 free articles to a first-time anonymous user and display a Paywall after they've consumed those articles, you can achieve this by configuring as shown below: 1. Allocate 5 free articles for a logged-out user (anonymous user) with Action criteria 'User state = logged out' as shown below. Keep the conversation expiration criteria as 'User state = Logged in', so that once the visitor logs in, this conversation expires.

Free Articles section

2. In the Actions section of the same Conversation, configure a paywall as Action type where Action criteria has 'Free Article Remaining' qualifier value false.

Actions Section

According to the settings above, a first-time visitor is initially given 5 free articles and enters the Conversation. The FAR drop-down value is 'False,' while the Free article count is 5 (greater than 0). As per the above table's 4th condition, the Free article count decreases by 1, and no paywall is displayed because the FAR qualifier fails in this case. Once the visitor consumes all five articles (views 5 articles), the Free article count becomes 0. In this scenario, when the visitor attempts to access the sixth article, the Paywall will be displayed (FAR value is 'False,' Free article count is 0, and the Action is triggered). ## Article Age This qualifier is available as a Meter qualifier, Conversation filter, and as an Action criterion. As the name suggests, this qualifier can identify the published date of the article and calculate the age of the article. To utilize this qualifier, a code snippet must be added anywhere within the body tag of the article webpage, following the specified format: ```
(JS date format)
``` {% hint style="info" %} **className**: Can be named by the customer **JS date format**: The date on which the article is published. The date should be entered in the JS standard format. (Ex: Wed Apr 19 2023 16:20:12 GMT+0530 (India Standard Time)). {% endhint %}

Article Age Qualifier

**Example**: As per the settings shown in the above image, if a reader accesses an article that is older than 5 weeks, then the configured Modal template will be displayed to the user. ## Mather Segments This qualifier will be available as a Meter qualifier, Expiration type, Conversation filter, and Action criterion. Mather Segments is specifically designed for users of Listener, the data platform by Mather. Its primary function is to verify the presence of Mather segments within the local storage key '\_matherSegments.' Therefore, this qualifier will only be functional for clients who utilize Mather segmentation, as they will have the '\_matherSegments' key in their local storage, allowing the qualifier to effectively check for the presence of Mather segments. For additional info on this qualifier, check [here](mailto:undefined). **How it works** This qualifier operates by targeting visitors based on the presence or absence of the specified Mather segment values in the local storage. **Settings**: * **Operator:** Select any one of the listed conditions ('Contain all of,' 'Contain at least one of,' 'Contain none of') from the Operator drop-down. * **Value:** Enter Mather Segment values separated by commas (without any quotes) in the Value field.

Mather Segments Qualifier

When 'Contain all of' is selected as the Operator, the qualifier will be passed only if all the segment values specified in the Value field are present in the local storage key '\_matherSegments.' Likewise, when the Operator selected is 'Contain at least one of,' the qualifier will be passed if at least one of the segment values specified in the Value field is present in the local storage key. Similarly, when the operator is 'Contain none of,' the qualifier will be passed if none of the values specified in the Value field are present in the local storage. ## Coming From Social This qualifier is available as a Meter Qualifier, Conversation Filter, Expiration Type, and also as an Action Criterion. The main advantage of 'Coming From Social' qualifier is that it saves the users from using the JS qualifier.

Coming From Social Qualifier

**How it works:** The functionality of this qualifier varies based on its usage, whether as a meter qualifier, conversation filter, action criterion, or expiration type. For instance, when used as a meter qualifier, it identifies visitors arriving at the news website from social network links like Facebook or Twitter. Depending on this identification, visitors are assigned to the corresponding Meter level (Free, Metered, or Premium). If used as an action criterion, the execution of the configured action type is determined by the qualifier's value. **Settings**: * **Social Network**: Choose a social network name (Facebook, Twitter, or Any of the above) from the Social Network drop-down menu. * **Value**: Select either Yes or No in the Value field. **Example**: If you want to categorize the visitors coming from Facebook into Free Meter level, you may employ this qualifier as a meter qualifier. To do so, on the Meter Rules page, select the required Meter Rule from the drop-down. In the Rule Settings tab, select ‘Facebook’ from the Social Network drop-down and ‘Yes’ from the Value drop-down.

Setting 'Coming From Social' as a Meter Qualifier

## Subscription Creation Date This qualifier setting is very similar to the ‘Subscription Expiration’ qualifier. The Subscription Creation Date qualifier is available as a Meter Qualifier, Conversation Filter, and Action Criterion. **How it works**: With this qualifier, it is now possible to target subscribers who possess active subscriptions and were subscribed on a specific date or during a specified time frame. The Subscription Creation Date qualifier is also helpful to target visitors who recently subscribed (by specifying the subscription creation date) to simply say a 'thank you' message or offer special deals, etc., depending on their subscription date. There might be multiple scenarios in which knowing the subscription creation date might be useful. **Settings**: * **Condition**: Select ‘Is’ or ‘Is Not’ in the Condition field. * **Value**: Choose one of the following options in the Value field: ‘Within The Past’, ‘Exactly Ago’, or ‘On’. * **Qualifier**: Specify the time frame (Days, Weeks, or Months) in the Qualifier field. * **Value**: Enter a numerical value to indicate the specified time frame in the Value field (For example 2 weeks, 3 months, etc.) **Example**: Let us consider the values selected in the fields are as follows:\ Condition: Is\ Value: Within The Past\ Qualifier: Weeks\ Value: 2\ In this example, the entered values in the fields would function as follows:\ Subscription Creation Date - ‘Is within the past 2 weeks'.

Subscription Creation Date Qualifier as an Action criterion

{% hint style="info" %} **Note**: If you choose ‘On’ in the Value field, then the Qualifier field will be replaced by another Value field. You can select the exact date using a date picker in the new Value field, that can represent the precise Subscription creation date. For example, ‘Subscription Creation Date - 'Is On 22-08-2023’. {% endhint %}

Subscription Creation Date - ‘Is On’