I'm thinking about using the Google Maps API, but I'm not clear on how much I might have to pay for it. Google lists different prices for different types of SKU (which they don't expand, so not sure what that stands for). See here: hidden link
What type of SKU will the Toolset Map use? What is the difference between Embed, Static Maps, or Dynamic Maps?
Toolset Maps use both the Maps API and the Places API. In the Maps API, the Embed and Static Maps SKUs are not typically used. You would have to implement those manually with your own custom code if you wanted to use them. A static map is just a picture of a map, it does not allow panning or zooming. An Embed map is displayed inside an iframe, so it would have to be coded manually. In general the Dynamic Maps SKU is used to display a map, and the others are not required.
In the Places API, Toolset Maps uses the Geocoding API to interpret an address custom field and store the location of its marker. This usually only happens once per location, unless you clear the location cache. It also uses the Autocomplete - per request SKU to handle autocomplete suggestions. There will be quite a few of these for custom searches.
Thank you, this is really useful!
So I'm trying to get my head around what are the actual likely costs of implementing this. The problem is the very vague way a 'load' is defined. I'm not sure how many loads a user is likely to use up when browsing the map, zooming in and out, opening specific pins, etc. Do you have some models I could base on?
On the front-end of the site, any time any User loads a page that includes a map it counts as one load. If there are multiple maps on the page, each of those maps counts as a separate load. Opening pins, zooming in and out, panning and so forth do not add costs:
https://developers.google.com/maps/billing/gmp-billing#dynamic-maps
When you store a custom address field in the back-end of the site (or in Forms when creating a post on the front-end of the site), that counts as a Geocoding API hit. Then that location is stored in the Maps cache so it doesn't have to hit the Geocoding API in the future, and the marker can be mapped. So count one Geocoding API hit per location you have stored as a custom field value.
Autocomplete hits are somewhat more complex. They are billed according to User session and interaction:
https://developers.google.com/maps/billing/gmp-billing#about-autocomplete-sessions
Autocomplete hits are logged when one searches for a location on the backend of the site to set a custom field value, or in Forms to set a custom field value, or in a custom search View to set a location for search.
