Simple rules for when to use ignoreInToken

 
The number of match tokens generated has a direct impact on the performance of a match rule. Therefore, you must ensure that your tokenization scheme is configured correctly to produce the desired match results. The match document is the record that is compared to another match document by a comparator to identify whether they matched or not. 
 
There are some basic rules to keep in mind when it comes to ignoreInToken. Always use ignoreInToken when:

• Match rule uses the “notEquals” operator
• You are using “ExactOrNull” or “ExactAndAllNull” operators
• You are using the thresholdChars with the DistictWordsCompartor
• If your fuzzy comparator is generating too many tokens.
• You have similar match rules generating similar tokens

For more detail, please review the documentation in https://docs.reltio.com/en/model/consolidate-data/configure-match-rules-overview/create-initial-match-rules/design-your-match-tokenization-scheme.
 
Our recommendation at this point is to:
 
a.  Understand your match rules and how they should be design at deeper level.
b.  Execute a match rule analyzer 
c.  Make changes in your match rules as necessary.
d.  Execute Rebuild your match tables task (reference: https://docs.reltio.com/en/explore/get-going-with-apis-and-rocs-utilities/reltio-rest-apis/engage-apis/tasks-api/rebuild-match-table-task)