Documentation

Territory Mapper help

For the Salesforce administrator who has just installed Territory Mapper, or who inherited it. These pages are in reading order, not alphabetical — and The two hierarchies is the one not to skip.

Setting it up for the first time? Start at Admin setup. Four of the steps cannot be shipped with the package and have to be done by hand in your org, and three of them fail silently when missed.

• Getting started Your first territory model, in about ten minutes.

• The two hierarchies There are two trees, and they have nothing to do with each other.

• Building a territory model Read The two hierarchies first if you have not.

• Editing boundaries on the map Drawing a boundary means selecting census areas.

• Roles and assignment Two different things get attached to a territory, and mixing them up is the second most common confusion in this product after the two hierarchies.

Administration

• Admin setup Everything that has to be true before Territory Mapper works, in the order to do it.
• Geocoding clean rules Salesforce's built-in geocoding data integration rules turn a billing address into a latitude and a longitude and write them onto the record, along with an accuracy telling you how precisely the address matched.

When something is wrong

• The exception queue Assignment Exceptions is where every record that could not be assigned ends up, with the reason and what to do about it.
• Coverage gaps A coverage gap is an area inside your territory model that no territory covers, and where records are actually landing.
• Troubleshooting By symptom.

• Vocabulary The words this documentation uses, what they mean, and — where they differ — what the app calls the same thing.