Salesforce Maps
Salesforce Maps is a location intelligence add-on that plots Salesforce records on an interactive map so sales and field teams can see their data by geography.
Definition
Salesforce Maps is a location intelligence add-on that plots Salesforce records on an interactive map so sales and field teams can see their data by geography. It turns address fields on accounts, leads, contacts, and custom objects into pins, then layers routing, proximity search, and territory planning on top of that map.
The product answers questions that a list view cannot, like which customers sit within ten miles of a rep, where coverage gaps exist, and what the fastest order of visits is for a given day. Maps is a paid add-on rather than part of the base license, and it serves outside sales, field service, and operations teams who plan work around physical locations.
How Salesforce Maps turns records into a working map
Layers: how records become pins on the map
Everything you see in Maps sits on a layer, and the Layers tab is where you toggle them on and off. A marker layer is a set of records plotted as pins, with each pin placed from the address fields on the source object. You define a marker layer against a Salesforce report or object, choose which fields drive the location, and pick how the pins render. Render modes include individual markers, clusters that group nearby pins into a single count, a heatmap that shades areas by density, and scatter. Shape layers draw boundaries such as zip codes, counties, or states, so you can frame the map around regions you care about. Data layers bring in business, demographic, or property information to overlay context on top of your own records. A sales manager might switch on open opportunities in green, past due accounts in red, and a competitor data layer at the same time. Because layers stack, the map becomes a flexible canvas rather than one fixed view. Reps save the layers they use most, which keeps the daily map fast to open.
Proximity search and acting on records from the map
Proximity search is the feature reps reach for most. Drop a point on the map, set a radius, and Maps returns every record of a given layer inside that boundary. A rep heading to one meeting can find every nearby account and decide who else to visit while in the area. You can search around your current location, around a specific address, or around any pin already on the map, and you can limit how many markers a proximity boundary returns so the view stays readable. Once records are on screen, Maps is not read only. You can act on a pin without leaving the map: log a call, create a task or event, send an email, or update fields on the underlying record. Maps also supports adding new prospects through Click2Create, where you find a business in a data layer or on the map and create a lead or account from it in one step. This keeps field activity flowing back into Salesforce, so the CRM reflects what happened in the field instead of waiting for end of day data entry.
Routing, from simple sequencing to Advanced Routing
Routing is the productivity engine of Maps. At the basic level, you select a group of pins and Maps calculates an efficient order to visit them, optimizing for the shortest or fastest sequence and producing turn by turn directions. That alone saves windshield time for reps who plan their own days. Advanced Routing goes further with constraint based optimization. Instead of sequencing a handful of stops, it can plan routes across a whole team using business rules. You can encode visit cadences, time windows for when a customer can be seen, visit durations, and priority levels, then let the optimizer build schedules that respect those rules. Salesforce describes planning routes for up to four months ahead this way, which suits regular service or merchandising visits where each account needs to be seen on a set frequency. The result is a plan that balances drive time against the cadence each customer requires, rather than a manually built spreadsheet. For field service and consumer goods teams, this turns route planning from a daily chore into a repeatable, rules driven process that scales with the size of the territory.
Territory Planning: alignments, units, and optimization
Territory Planning is a distinct capability inside the Maps family for designing balanced sales territories on a map. You start from a data set, often a Salesforce report, and an alignment, which is the working model of how geography maps to territories. The building blocks are units, typically geographic areas like zip codes that carry attributes such as revenue, account count, or number of reps. You assign units to territories by drawing on the map or by rule, and an assignment ID such as Account Owner ID ties each record back to the right territory. The Optimize action is where the tool earns its keep. It can automatically distribute units to meet a goal, and you choose what matters: Balance spreads a chosen attribute evenly across territories, Continuity keeps reassignments to a minimum, and compactness keeps territories geographically tight. A checkbox can auto assign nearby containers so unassigned zip codes attach to the closest territory and you avoid coverage gaps. Proposed changes appear before you commit, so you can review how each attribute shifts and lock units you do not want moved. The output can then push assignments back into Salesforce.
Live Tracking and the field operations picture
Live Tracking is a Maps capability aimed at field operations rather than individual reps. It shows the real time location of vehicles, technicians, drivers, or other assets on the map, so a dispatcher or operations leader can see where the field workforce is at a given moment. Paired with geofences, it can trigger business processes when an asset enters or leaves a defined area, which supports automation like recording arrival on site. This gives leaders visibility into work that happens away from a desk and helps with decisions like which technician is closest to an urgent job. Live Tracking is worth understanding alongside a planning note. Salesforce is consolidating its mobile story, and the standalone Salesforce Maps mobile app is set to retire on August 31, 2026, with users directed to the Maps experience inside the main Salesforce mobile app. Certain Live Tracking mobile subscriptions and some third party Live Tracking integrations are also being retired, and Salesforce advises exporting geolocation data you want to keep before a subscription ends. The core Maps product remains current; these changes affect specific delivery channels and add-ons, not the platform as a whole.
Where Maps fits, and what it is not
Maps is a paid add-on that layers onto an existing org, so the value depends on clean address data on the records you plan to plot. Pins are only as accurate as the geocoded addresses behind them, which means data quality work pays off directly in map quality. Maps is built for teams whose work is organized by place: outside sales reps planning visits, field service technicians dispatched to sites, merchandisers covering retail accounts, and managers designing coverage. It is not a replacement for Sales Cloud or Field Service. It sits next to them and adds a geographic lens. The map reveals patterns that tabular reports hide, such as customer density, white space where you have no coverage, and routes that waste drive time. Compared with the older display geolocation features built into the platform, Maps is a far deeper toolset, with routing, territory optimization, and external data layers that the base product does not offer. Teams adopt it when geography is a real constraint on how work gets done, not just a field on a record, and when the cost of inefficient travel or uneven territories is large enough to justify the license.
Enable Salesforce Maps and build your first marker layer
Salesforce Maps is a managed package add-on. After your org is provisioned with Maps and the package is installed, an admin enables access and builds a first marker layer so reps can see records on the map. These are the broad strokes; follow the current Maps setup guide for exact steps in your release.
- Confirm provisioning and install the package
Make sure your org has the Salesforce Maps add-on, then install the Maps managed package from the link Salesforce provides. Installation adds the Maps app, objects, and tabs to your org.
- Grant access with permission sets
Assign the Maps permission sets and license assignments to the users who need the map. Without the license and permissions, the Maps tab will not appear for a user.
- Build a marker layer
In the Maps app, open the Layers tab and create a marker layer from a report or object. Map the address fields that drive pin placement and pick a render mode such as markers, clusters, or heatmap.
- Tune the view and save
Set colors, filters, and any proximity limits so the layer stays readable, then save it. Reps can now toggle that layer on the Layers tab and run proximity searches against it.
The records the marker layer plots. A focused report keeps pin counts and load times sensible.
The address or geolocation fields Maps uses to place each pin. Clean, geocoded addresses produce accurate placement.
How pins display: individual markers, clusters, heatmap, or scatter. Choose by data volume and what you want to read at a glance.
Controls who can open Maps and which features they reach. Required before the Maps tab shows for a user.
- Pins are only as good as the address data behind them; ungeocoded or messy addresses place markers in the wrong spot or not at all.
- Maps is a separate paid add-on with its own license, so budget and provisioning are prerequisites, not just configuration.
- Plan around the August 31, 2026 retirement of the standalone Maps mobile app and move field users to the Maps experience in the main Salesforce mobile app.
- Large marker layers can slow the map; use filters, clustering, or proximity limits to cap how many pins render at once.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Salesforce Maps.
Hands-on resources to go deeper on Salesforce Maps.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is Salesforce Maps?
Q2. Who benefits most?
Q3. What spatial patterns does it reveal?
Discussion
Loading discussion…