Use Exact Match Operators in Social Listening to refine search queries
Updated
Learn how to use Exact Match operators to refine your search queries while creating Topics and Themes.
In Social Listening, the Exact Match Operators help you search for a specific term or phrase while creating queries during topic creation. There might be situations in which you want to find the index items containing an exact term/phrase and you are not interested in other items containing variants of this term/phrase. In such a situation, you need to use an Exact Match query syntax.
Sprinklr usually normalizes data by ignoring punctuation marks and articles like a, an & the. However, in the case of an exact match, keywords given in the query are taken in their exact form to match the data. For example:
Spider-man and Spiderman will be treated as 2 different words under Exact Match.
Without an exact match query – message: (spider OR man) will match spider-man.
With an exact match query – only exactMessage: (spider-man) will match spider-man.
Other than Exact Match Operators, Sprinklr supports two more operator types:
List of operators available in Exact Match with syntax
exactTitle: (Finding an exact match in the title)
exactMessage: (Finding an exact match in messages)
exactUserBio: (Finding an exact match in userbio)
exactParentMessage: (Finding an exact match in parent messages)
exactParentTitle: (Finding an exact match in parent title)
exactContent: (Finding an exact match in the title, message, and userbio)
To know about the syntax for Search Operators, see – Search Operators in Listening Advanced Queries.
Note:
The Exact Match Operators can be used in Topics and Themes.
The Exact Match Operators will not be supported in Quick Search (previously known as Listening Explorer).
The Topic Preview option is supported with all the Exact Match operators.
The Backfill option is supported with exactTitle, exactMessage, and exactContent.
Below are the common impacts of using Exact Match Operators:
Impact | Example |
Case Sensitivity | Exact match will make queries case sensitive.
|
Accents/Latin symbols/Characters | Accents can be retained with exact match.
|
Punctuation | Punctuations are considered for exact match.
|
How to create queries using Exact Match operators?
Below are a few examples for creating queries using Exact Match operators –
Query | Result |
(exactMessage: "USA") | This will fetch the mentions whose message contains text keyword USA. It will not match keywords like usa OR Usa OR us. |
(exactTitle: (#Dell AND #Microsoft)) | This will fetch mentions that have #Dell and #Microsoft in their title. |
(exactMessage: ("our planet") OR exactUserBio: ("Super Human")) | This will fetch the mentions whose message contains text Earth is our planet, or the mention should have a bio of the author that contains the phrase I am a Super Human. |
(exactParentMessage: "Customer Feedback" ~2) | This will fetch the mentions whose parent message contains the text keywords customer most valuable feedback in the proximity of 2. |
(exactParentTitle: "World Cup" AND userbio: "biggest cricket fan") | This will fetch mentions that have WorldCup in their title, and the bio of the author of the post should contain the phrase biggest cricket fan. |
exactContent syntax
Query | Result |
(exactContent: ("Nadal" AND "Tennis")) | This will fetch mentions that have Nadal and Tennis in their title, message, and/or userbio. It will not match keywords like "Rafal aka nadal is the best player". |
exactContent syntax with NEAR
Query | Result |
(exactContent: ((WCC OR world-cup) NEAR/2 (Nadal OR Rafael))) | This will fetch mentions that have "WCC Nadal"~2, "world-cup Nadal"~2, "WCC Rafael"~2, "world-cup Rafael"~2 in their title, message, and/or userbio. It will not fetch mentions that have keywords like "wcc-cup Oldest rafael". |
For frequently asked questions related to Operators, see Operators FAQs.
Scope and limitations
The Exact Match operators (e.g. exactMessage, exactTitle) do not work with these languages – Chinese,
Japanese, Korean, Thai, Lao, Khmer (Cambodian), Myanmar (Burmese), Tibetan, Georgian, Amharic, Tigirinya (Tigrinya), Oromo, and Somali.
In topic query fields, the colon is not supported in Exact Match. In the advanced query field, it is supported.
The Exact Match operators can only be used in advanced query field queries.
The exactMessage operator is available in keyword query filter on widgets.
The exactMessage operator is case sensitive.
The exactMessage operator is sensitive to special characters ( - _ @ # $ & *).
The exactMessage operator is not sensitive to punctuations (, : ; ‘ ’. ?).
The exactMessage operator and combination of AND or OR operator work is supported ((exactMessage: Dell OR XPS)) OR ((Alienware)).
The exactMessage operator and combination of NEAR/n function is not supported ((exactMessage: Dell NEAR/5 XPS)).
NEAR/n function is supported within exactMessage query ((exactMessage: Dell NEAR/5 XPS)).
Complex queries that have Proximity/Near operators between a search and exact operators will not work. For e.g.
message: (exactContent: (BCC OR #BCC) NEAR/3 (message: association OR title: association))
It seems to be an invalid query because NEAR/3 is between exactContent and message operators.