Configurable account geo-stamp on first visit
This content is for Spring ’26. Switch to the latest version for up-to-date documentation.
Historically, the first check-in at an account could capture latitude and longitude and persist them on the account as its location. You can now disable that automatic geo-stamp so introductory or off-site meetings do not overwrite coordinates, keeping geofencing and routing data accurate.
JSON example:
"Visits": { "VisitPreventAccountGeoStampOnVisitStart": true}