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.
You may know that LeanData can update fields, but sometimes you may need to append additional text to a field instead of replacing it entirely. Here is how to do that in LeanData Router.
As a new lead continues to interact with assets on your website, it may get updated multiple times shortly after it is created, leading to routing the record twice. Here is one way to go about preventing double routing.
As a native Salesforce solution, LeanData is subject to any validation or duplicate prevention rules you have in Salesforce. Here is a way that you can exclude specific Users.
Some organizations use Salesloft cadences to manage sales engagement. Learn how you can incorporate LeanData's Salesloft Integration to automate follow up based on campaign activity.
When merging duplicates in LeanData sometimes you only want certain fields overwritten. Here is a way that you can selectively choose which fields you want to be overwritten on a merged record.
When using LeanData Router, you can begin your process on one object, then continue it on a different object. You just need to know how to identify the other object record and properly trigger it for routing purposes.
Sometimes you need to use different matches for different purposes. LeanData's Object Variables will allow you to store different matches in different Variables and reference them whenever you need.
Do you ever need to update a different record than the one you are routing, such as a Matched Account, or a Related Activity? We walk through how you can do so using LeanData's Update Record Node.