Sometimes when you're using both LeanData Tagging and Routing, you may notice that LeanData routes to a different Account than it is tagged with. Here is a way to prioritize the Account Match stored in the Reporting Matched Account field.
When using Round Robins, sometimes you actually want to assign two different User fields with the Round Robin. Here is how to do that, whether you want to assign to the same User or to different Users within the same Round Robin Pool.
Sometimes you are uploading a large list or making some bulk changes to records, and you want to skip or bypass LeanData routing for these records. Here is a way to exclude these records from LeanData Routing without affecting routing for other records.
If you use multi-select picklists, you might want to use something like the “contains” operator to look for one of several different values in a field. Even though there isn’t a contains operator , here are two ways you can set up your nodes to look for a one out of several options in a multi-select picklist.
Sometimes you want to trigger a record to route depending on the prior value on a field, such as triggering on an increase in Lead score, but not a decrease. This will explore a way you can compare a field's new value with its prior value in determining when to trigger routing.
Tracking the history of certain fields is incredibly useful for troubleshooting, but there are limits to how many fields you can track in Salesforce. Here is how to set up Routing Metrics Mapping to track fields in your LeanData Logs.