Google Maps Platform Reporting

It’s important to monitor your Google Maps Platform usage and quota consumption on a regular basis. This can help you track your usage and manage consumption to stay within the limits you have set for your projects. This can also help you detect any unexpected interactions that might occur between your projects and the Google Maps Platform services.

Console dashboards

You can monitor your usage and quota consumption for the Google Maps Platform APIs using the dashboards available in the Google Cloud Platform console.

API dashboard

The console's API dashboard (APIs & Services) provides usage metrics for all APIs enabled for your project: the Google Maps Platform APIs and SDKs as well as other Google APIs and services.

apis & services

Google Maps dashboards

The console's Google Maps dashboards (the Overview, APIs, and Metrics dashboards) provide usage and quota metrics for the Google Maps Platform APIs and SDKs only.

apis & services

Accessing the dashboards

To access the API dashboard:

  1. Open the Google Cloud Platform console.
  2. Select a project.
  3. On the API card, click Go to the APIs overview.
    This will take you to the API dashboard (APIs & Services).

To access the Google Maps dashboards:

  1. Open the API dashboard (APIs & Services).
  2. Select a project.
  3. Scroll down to the table listing the APIs, SDKs, and services.
  4. In the table, click the name of any Google Maps Platform API or SDK.
    This will take you to the Google Maps METRICS page for the API or SDK you selected.
  5. Use the left panel to access the Google Maps Overview dashboard, APIs dashboard, or Metrics dashboard.
  6. Note: Henceforth, the Google Maps Platform APIs and SDKS are referred to as the Google Maps Platform APIs, or simply API or APIs.

Usage reporting

Usage is based on the number of requests your project makes to the Google Maps Platform APIs using the credentials associated with your project. Requests include successful requests, requests that result in server errors, and requests that result in client errors. Credentials include API keys and client IDs (for Premium Plan and migrated Premium Plan projects).

Usage metrics are displayed in tables (Requests, Errors, and Latency) and graphs (Traffic, Errors, and Latency). For tracking purposes:

  • Usage metrics for all APIs can be filtered by time period and API; you can also see traffic, error, and latency grouped by response code, API and credential.
  • Usage metrics for a specific API can be filtered by time period and the API’s versions, credentials and methods; you can also see traffic, error and latency grouped by response code, API method and version, and credential.

API dashboard

The API dashboard (APIs & Services) provides an overview of the usage metrics for all APIs enabled for your project (the Google Maps Platform APIs as well as other APIs and services).

The dashboard features three graphs and a table. You can filter the usage displayed in the graphs and tables by selecting a time period (from 1 hour up to the last 30 days).

The Traffic graph shows usage in queries per second (QPS) per API. The Errors graph shows percentage of the requests that resulted in errors per API. The Latency graph shows the median latency of the requests per API.

Beneath the graphs, a table lists the enabled APIs and services. Requests are the number of requests (for the selected time period). Errors are the number of these requests that resulted in errors. Latency (medium latency and percentile) is the latency for these requests.

For more information, see Monitoring your API Usage.

apis & services

Google Maps Overview dashboard

The Google Maps Overview dashboard includes a table listing enabled APIs and usage in requests for the last 30 days. The dashboard also includes a graph that displays traffic by response code in QPS (Queries Per Second) for all enabled APIs.

Note: If you click the name of any enabled API, you will be directed to the Google Maps METRICS page for that API.

overview

Google Maps APIs dashboard

The Google Maps APIs dashboard includes two tables. The Enabled APIs table shows the number of requests, the number of errors, and the average latency for each enabled API for the last 30 days. The Additional APIs table lists APIs that have not been enabled (hence, no usage is reported).

Note: If you click the name of any enabled API, you will be directed to the Google Maps METRICS page for that API.

apis

Google Maps Metrics dashboard

On the Google Maps Metrics dashboard you can select (and display) up to 10 Traffic, Errors, and Latency graphs — grouped by response code, API, or credential. You can filter the results by selecting a specific API or multiple APIs.

Beneath the graphs, the dashboard includes an APIs table that shows requests, errors, and latency for the APIs you have selected.

You can filter the usage displayed in the graphs and tables by selecting a time period (from 1 hour up to the last 30 days).

Note: You can view additional API-specific usage information on the Google Maps METRICS page.

metrics

Google Maps METRICS page

Note: To access the Google Maps METRICS page, click the name of any enabled API on the Google Maps Overview dashboard or APIs dashboard.

The Google Maps METRICS page displays detailed usage information and has extended filtering functionality for the specific API you have selected.

Using the API drop-downs, you can filter results by setting values for the API’s versions, credentials, and methods. You can also filter results in the graphs by selecting a time period (from 1 hour up to the last 30 days).

The usage in the Traffic, Errors, and Latency graphs can be grouped by response code, API method, API version, and credential.

metrics page

Response Code Graphs

The Traffic by response code and Error by response code graphs split usage by response code class. The table below shows the mapping between the Google Maps Platform API response status and response code class:

Response Status Response Code Class
(2xx, 4xx, 5xx)
Notes
OK 2xx Successful response.
ZERO_RESULTS 2xx Successful response returned no result.
REQUEST_DENIED 4xx Client error caused by authentication error, access error, etc. Check the API response for more details.
OVER_DAILY_LIMIT,
OVER_QUERY_LIMIT,
dailyLimitExceeded,
userRateLimitExceeded
4xx Client error caused by too many requests per allowed time period. Retry the request at a later time. Check the API response for more details.
INVALID_REQUEST,
INVALID_ARGUMENT
4xx Client error caused by invalid request. Check the API response for more details.
NOT_FOUND 404 For the Geolocation API, this indicates that the inputs were not sufficient to produce a location estimate. This is a billable request and therefore will consume quota.

For Roads API, this indicates that the inputs could not be reasonably snapped to roads. This is a billable request and therefore will consume quota.

For other APIs, this is a client error indicating that the wrong URL was used to access the API. Please refer to the intended API's documentation for the correct URL.
INVALID_REQUEST (INVALID_VALUE),
MAX_WAYPOINTS_EXCEEDED,
MAX_ROUTE_LENGTH_EXCEEDED
4xx Error caused by invalid parameter value, too many values provided, etc. Check the API response for more details.
UNKNOWN_ERROR 5xx Server error indicating that request cannot be proceeded: internal error, service overloaded, not available, time out, etc.

For more information about status codes and error messages, see the response documentation for the API you are interested in (for example, Geocoding Responses or Directions Responses).

Quota reporting

Quotas set limits on the number of requests your project can make to the Google Maps Platform APIs. Requests can be limited in three ways: per day, per second, and per user per second. Only successful requests and requests that cause server errors count against quota (requests that cause client errors do not count against quota).

Quota usage is displayed in graphs and can be grouped in requests per day or per 100 seconds. The current quota limits for selected APIs are displayed in tables below the quota usage graphs.

Google Maps QUOTAS page

Note: To access the Google Maps QUOTAS page, click the name of any enabled API on the Google Maps Overview dashboard or APIs dashboard.

The Google Maps QUOTAS page shows quota limits and quota consumption for the specific API you have selected.

The page shows only requests that consume quota: successful requests (OK, ZERO_RESULTS) and requests that cause server errors (NOT_FOUND, INVALID_VALUE, UNKNOWN_ERROR).

Requests that cause client errors — authentication/authorization/invalid argument errors (REQUEST_DENIED, OVER_QUERY_LIMIT, INVALID_REQUEST) — do not consume quota and are not displayed in the Quota reports.

The quota unit is a request for most of the Google Maps Platform APIs (Static Maps API, Street View Static API, Geocoding API, Directions API, Places API, Timezone API, Geolocation API, and Elevation API). But there are some exceptions:

  • For the Distance Matrix API, the quota unit is an element which is an origin-destination pair.
  • For the Maps JavaScript API, the quota unit is a map load.
  • For the Maps SDK for Android and Maps SDK for iOS, the quota unit is a Street View request/Panorama load (Map loads are free and do not consume quota).
quotas page

Quota Units

The table below shows the quota unit for the Google Maps Platform APIs.

Google Maps Platform API Quota Unit
Maps
Maps SDK for Android 1 Panorama
Maps SDK for iOS 1 Panorama
Maps Static API 1 Request
Maps JavaScript API 1 Map Load
Street View Static API 1 Request
Maps Embed API 1 Map Load
Routes
Directions API 1 Request
Distance Matrix API 1 Element (origin-destination pair)
Roads API 1 Request
Places
Places API 1 Request
Geocoding API 1 Request
Geolocation API 1 Request
Time Zone API 1 Request