Align Zip to Territory versus Align Brick to Territory
Key Takeaway
The rule's GeoCodeType decides which job runs, not the country. ZipToTerritory rules need Align Zip to Territory. BrickToTerritory, GeoGroup1, and GeoGroup2 rules need Align Brick to Territory, even when the geo group code is a US state such as Florida.
Territory Management uses batch jobs to align accounts to sales territories, so reps can access the healthcare providers they cover. Align Zip to Territory and Align Brick to Territory both align accounts by the geography in their addresses. Each job reads rules of a different type, so the way the rules are set up decides which job you run.
Explicit versus geographic alignment
Territory Management uses batch jobs to align accounts to territories at scale. The jobs work in one of two ways.
Align Account to Territory works from explicit mappings. These mappings are manual assignments, stored as Object Territory Association records with AssociationCause = Territory2Manual. Users create them in the standard territory management tools, or load them from external systems.
Align Zip to Territory and Align Brick to Territory work from geography instead. They compare each account's address with territory alignment rules, so you don't need an explicit assignment for each account. Both geographic jobs automatically create and update the records that give sales reps access to the aligned accounts.