Skip to main content

Setting Up Your Google Maps API Key for FieldKo

Learn how to create a Google Maps API key, enable required services, set up billing, and configure it in FieldKo

Updated this week

FieldKo leverages Google Maps services to power features like account mapping and visit route optimisation. To use these features, you need a Google Maps API key.

This guide will walk you through creating a Google Maps API key on Google Cloud Platform, enabling the necessary APIs (Directions, Distance Matrix, Geolocation, Maps JavaScript, and Geocoding), setting up billing, and configuring the key in Salesforce. We’ll also highlight where FieldKo uses the Google Maps API in its app.

Setting Up Billing (Google Cloud) and the Free Tier

Google requires every Maps API project to have billing enabled, even if you plan to stay within the free usage limits. Setting up billing does not mean you will be charged – it simply means a credit card or payment method is on file. Most FieldKo customers remain within Google’s free usage tier and incur no cost for Google Maps usage.

Add a billing account: In the Cloud Console, navigate to Billing (or Billing > Overview) and add a billing account if you haven’t already​. You’ll need to enter payment details (credit card) and basic information.

Understand the free tier: Google Maps Platform provides a generous free allowance of calls per month. As of 2025, Google has replaced the old $200 monthly credit with free monthly usage caps for each API SKU​. In practice, this means you get roughly 10,000 free requests per month for each Maps API (for core services like Maps, Geocoding, Directions, etc.) before any charges would apply​. This free tier covers the vast majority of FieldKo use cases. For example, standard usage — such as loading maps on account pages or calculating routes for daily visits — typically stays well within these free monthly limits. (For details on Google Maps pricing and free usage, refer to Google’s Maps Platform pricing page.)

(Optional) Set budget alerts: If you are concerned about unexpected charges, you can set up a billing budget and alerts in Google Cloud. For instance, you might set a $0 budget or a small monthly cap – if the free tier is exceeded, the budget can pause the API usage to prevent charges​. This way, if your usage ever grows beyond the free allowance, you’ll be notified or the API will stop rather than accruing costs.

Generating a Google Maps API Key (Google Cloud Platform)

Follow these steps to create a Google Maps API key using the Google Cloud Platform console:

  1. Sign in to Google Cloud: Log in to the Google Cloud Console with your Google account. If you don't have an account, create one first.

  2. Create or select a project: In the Cloud Console, click the project dropdown at the top left next to the Google Cloud logo, and choose New Project. Enter a project name (e.g. FieldKo Maps) and click Create​.

  3. Go to the Credentials page: Ensure your new project is selected. In the left-hand menu, navigate to APIs & Services > Credentials​.

  4. Create an API key: Click + CREATE CREDENTIALS and select API key​. Google will generate a new API key string. Copy this API key and save it somewhere secure (you will need to add it to Salesforce later). You can dismiss the dialog once you have the key.

Enabling Required Google Maps APIs

After creating the API key, you must enable the Google Maps APIs that FieldKo uses. Enabling these APIs in your Google Cloud project allows FieldKo to request maps, directions, and other location services. The APIs to enable are:

  • Maps JavaScript API – for interactive maps embedded in Salesforce (e.g. account location maps).

  • Geocoding API – for converting addresses to coordinates (and vice versa).

  • Geolocation API – for determining a device’s approximate location based on network data.

  • Directions API – for turn-by-turn directions and route data.

  • Distance Matrix API – for calculating travel distances and times between multiple points.

To enable each API: in the Google Cloud Console, go to APIs & Services > Library, then search for each of the above API names. Click on each API and press the Enable button. Repeat this for all five APIs so that all the required Google Maps services are active in your project​. (If you used the Google Maps Platform "Get Started" wizard, make sure it enabled all of the APIs listed.) Enabling these ensures FieldKo can access Google Maps features it needs.

Adding the API Key to FieldKo (Salesforce Configuration)

Once you have your Google Maps API key ready and all required APIs enabled, the next step is to configure FieldKo to use this key. FieldKo stores the Google Maps API key in a Salesforce Custom Setting called “Map Configurations” (this is part of the FieldKo managed package). Here’s how to add the key:

  1. Open Salesforce Setup: Ensure you are logged in as an admin in Salesforce. Click the gear icon and choose Setup.

  2. Navigate to Custom Settings: In Setup’s Quick Find search bar, type “Custom Settings” and select the Custom Settings entry​. This will display a list of custom settings in your org.

  3. Find “Map Configurations”: In the list of custom settings, locate Map Configurations (it may be under the FieldKo package namespace). Click Manage next to “Map Configurations”.

  4. Create or edit the configuration: You should see if a Map Configuration record already exists. If one does (for example, a “Default” entry), click Edit. If none exists, click New to create a new custom setting record.

  5. Enter the API Key: There will be a field for the Google Maps API Key (the exact field label may be like “Google Maps API Key” or similar). Paste the API key value you copied from Google Cloud into this field. Double-check there are no extra spaces.

  6. Save the record: Click Save to store the API key in the custom setting. Salesforce will now hold your Google Maps key for the FieldKo application to use.

After saving, the FieldKo app will automatically use this key for all Google Maps requests (no further coding or changes needed). It’s a good idea to test one of the map features (e.g., open an Account map or try using the route planner in FieldKo) to confirm that the maps load without error. If there’s an issue, re-check that the key was entered correctly in Salesforce and that all the required APIs are enabled and not restricted.

Where FieldKo Uses Google Maps in the App

With the API key configured, FieldKo can embed Google Maps functionality in various parts of the app. Understanding where the Google Maps API is used will help you verify that everything is working and appreciate the value it adds.

Key FieldKo features using the Google Maps API include:

  • Account Maps: FieldKo can display customer locations on a Google Map. For example, on an Account record or in a map view of accounts in a territory, users can see pins for each account’s location. This helps admins and reps visualise where their stores or clients are located relative to each other. (Behind the scenes, this uses the Maps JavaScript API for the map, and may use Geocoding to translate addresses to map coordinates.)

  • Visit Route Optimisation: One of FieldKo’s powerful features is visit planning and route optimisation for field reps. Reps can plan their day’s store visits, and FieldKo will map these stops and optimise the driving route using Google Maps. The app provides turn-by-turn Directions and travel time estimates between stops. This feature relies on the Directions API and Distance Matrix API to suggest the best route and timing. FieldKo’s mobile app allows users to view the optimised route on a map and even get navigation prompts.

  • Current Location & Check-ins: When a field rep checks in to a store visit, FieldKo can capture the user’s current location to verify the check-in. Google’s Geolocation API may be used in cases where GPS is unavailable, to approximate the device’s location via network signals. Additionally, the map views can centre on the rep’s current location to show nearby accounts.

  • Other Mapping Features: Anywhere FieldKo needs to convert an address to a location or display a map, the Google Maps API key is in play. This includes features like Nearby Account search (finding accounts within a radius on the map), visualising territories on maps, or any custom map-based visualisations in FieldKo. All these are enabled by the Maps APIs you activated.

By setting up the Google Maps API key as described, you ensure that all these FieldKo features – from account maps to visit routing – function correctly. Users will see interactive Google Maps and real-time route guidance inside FieldKo, enhancing their ability to plan and execute field work efficiently.

Final Tips

  • Free Tier Confidence: Nearly all FieldKo customers stay within Google’s free monthly usage limits for Maps API calls. Keep an eye on your usage in the Google Cloud Console, and set alerts if needed, but rest assured that Google’s free tier is generous for typical Salesforce field app usage.

  • Accuracy of Addresses: The quality of map results in FieldKo depends on accurate addresses for your Accounts and other records. Consider using Google’s Geocoding service (enabled by your API key) to geocode addresses if you notice any locations not plotting correctly on the map.

By keeping your Google Maps API key properly configured, FieldKo will continue to deliver rich mapping and routing features to your users, helping your team plan their visits and navigate with ease.

Did this answer your question?