Google Maps Platform Reporting

Stay organized with collections Save and categorize content based on your preferences.

Reporting in the Google Maps Platform provides a set of predefined visual reports that let you easily see basic API usage, quota, and billing information in the Google Cloud Console. You can quickly determine the number of API calls, how close you are to hitting API usage quotas, and monitor billing usage over time.

Types of reports include:

  • Usage reports: Reports the number of requests your project makes to the Google Maps Platform APIs using credentials associated with your project.
  • Quota reports: Reports quota usage in graphs that can be grouped in requests per minute. The current quota limits for selected APIs are displayed in tables below the quota usage graphs.
  • Billing reports: Reports costs over time as a stacked line chart. View the current month’s quota usage, inclusive of any usage-specific credits applied, as well as the total forecasted cost for the entire current month.
  • Engagement reports: Reports the number of views, interactions, and engagement rate for Locator Plus users.

See Response status and reports below for a complete list of the response statuses and response codes that define whether a request appears in the Usage, Quota, and/or Billing reports.

View the reports of Google Maps Platform usage, quota, and billing using the Cloud Console.

Usage reports

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.

APIs & Services Dashboard page

The APIs & Services Dashboard page 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 page 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.

monitoring apis

To access the APIs & Services Dashboard page:

  1. Open the Project selector page in the Cloud Console:

    Project selector page

  2. Select your project. The APIs & Services Dashboard page appears.

    If the page does not appear, select the menu button menu and then select APIs & Services.

For more information, see Monitoring your API Usage.

Google Maps Overview page

The Google Maps Overview page includes a table listing enabled APIs and usage requests for the last 30 days. Requests by API are also shown in graph form. A billing graph shows your current bill and total usage for the last 3 months.

Screenshot of an Overview chart showing a table listing enabled APIs and
  API requests for the last 30 days.

To access Google Maps Platform Overview page:

  1. Open the Google Maps Platform page in the Cloud Console:

    Go to Google Maps Platform page

  2. In the left menu, select Overview.

Google Maps Platform APIs page

The Google Maps APIs page 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.

apis

To access Google Maps Platform APIs page:

  1. Open the Google Maps Platform page in the Cloud Console:

    Go to Google Maps Platform page

  2. In the left menu, select APIs.

Google Maps Metrics page

The Google Maps Metrics page displays three graphs: Traffic, Errors, and Median Latency. The usage data in the graphs can be grouped by Response Code, API, API method, or Credential.

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

Using the API drop-down at the top, and the filtering options in the right pane, you can filter displayed usage metrics by selecting specific or multiple APIs, Credentials, Response Codes, and/or Platforms. You can also select a time period (from one hour up to the last 30 days) and granularity (per second or day) for the displayed usage metrics.

The metrics page displaying three graphs: Traffic, Errors, and Median Latency.

The Platform filter appears only when a single API is selected.

To access Google Maps Platform API Metrics page:

  1. Open the Google Maps Platform page in the Cloud Console:

    Go to Google Maps Platform page

  2. In the left menu, select Metrics.

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, 3xx, 4xx, 5xx)
Notes
OK 2xx Successful response.

This is a billable request and will consume quota.
OK 3xx Successful response.

This is a billable request and will consume quota.

For example, the Place Photo successful requests return 302 redirect to the referenced image.
DATA_NOT_AVAILABLE 2xx Successful response indicating that there's no available data for the input locations.

This is a billable request and will consume quota.
ZERO_RESULTS 2xx Successful response returned no result.

This is a billable request and will consume quota.
NOT_FOUND 2xx For the Directions API this indicates that at least one of the locations specified in the request's origin, destination, or waypoints could not be geocoded.

For the Places API this indicates that the referenced location (place_id) was not found in the Places database.

This is a billable request and will consume quota.
INVALID_REQUEST (invalid parameter value),
MAX_WAYPOINTS_EXCEEDED,
MAX_ROUTE_LENGTH_EXCEEDED, etc.
4xx Error caused by invalid parameter value. Check the API response for more details.

This is a billable request and will consume quota.
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,
RESOURCE_EXHAUSTED,
rateLimitExceeded,
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/missing parameter, request parsing/validation error) 4xx Client error caused by invalid request. Check the API response for more details.
NOT_FOUND (404) 4xx For the Geolocation API, this indicates that the inputs were not sufficient to produce a location estimate.

For the Roads API, this indicates that the inputs could not be reasonably snapped to roads.

This is a billable request and will consume quota.
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).

Google Maps Platform solutions parameter

Google Maps Platform provides many types of sample code to help you get up and running quickly. For example, you can use Quick Builder in Cloud Console, follow the industry solutions implementation guides, and learn from codelabs.

To understand usage and ways to improve our solutions, Google includes the solution_channel query parameter in API calls to gather information about sample code usage:

  • The solution_channel query parameter is included by default in solution sample code.
  • The query parameter returns analytics on solution adoption to Google to improve solution quality in future iterations.
  • You can opt out by deleting the solution_channel query parameter and its value from sample code.
  • There is no requirement to keep the parameter. Removing the query parameter will not affect performance.
  • The query parameter is only used for sample code usage reporting.
  • The query parameter is separate from any API-specific analytics and reporting. That means removing the parameter from solution sample code will not disable internal Maps JavaScript API reporting.

Quota reports

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 minute, and per user per minute. Only successful requests and requests that cause server errors count against quota. Requests that fail authentication do not count against quota.

Quota usage is displayed in graphs on the Quotas page in the Cloud Console, and can be grouped in requests per minute. The current quota limits for selected APIs are displayed in tables below the quota usage graphs.

Use this calculator to get your per-minute quota value for any GMP API product.

Google Maps Quotas page

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

The quota usage chart on the Google Cloud Console shows the total traffic for your API keys and client IDs. Client ID traffic is also available in the Metrics chart on the Cloud Console.

The page shows only requests that consume quota: successful requests (OK, ZERO_RESULTS, DATA_NOT_AVAILABLE) and requests that cause server errors (NOT_FOUND, INVALID_REQUEST/INVALID_VALUE (invalid parameter value), UNKNOWN_ERROR).

Requests that cause client errors — authentication/authorization/invalid argument errors (REQUEST_DENIED, OVER_QUERY_LIMIT, INVALID_REQUEST (invalid parameter, request parcing error)) — do not consume quota and are not displayed.

The quota unit is a request for most of the Google Maps Platform APIs (Maps Static API, Street View Static API, Geocoding API, Directions API, Places API, Time Zone 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 available at no charge and do not consume quota).

Screenshot of the Maps' Quotas page in the Google Cloud Console. It shows
  quotas by API using a selector, then shows Map Loads relative to the set quotas
  for the API in question.

To access Google Maps Platform Quotas page:

  1. Open the Google Maps Platform page in the Cloud Console:

    Go to Google Maps Platform page

  2. In the left menu, select Quotas.
  3. Select an API from the API drop-down list.

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

Billing reports

View your billing report

Billing reports for your use of the Google Maps Platform products are available in the Google Cloud Console (see Billing).

To access the billing reports:

  1. Open the Project selector page in the Cloud Console:

    Project selector page

  2. Select a project.
  3. Select the menu button menu and then select Billing.
  4. If you have multiple billing accounts, select Go to linked billing account to open the Overview page for the linked billing account.
  5. In the left menu, select Reports to open the billing Reports page for the linked billing account.

How to read the billing report chart

Billing reports plot cost over time as a stacked line chart. The default view displays the current month’s daily usage-specific costs grouped by project (for all products), inclusive of any usage-specific credits applied, as well as the total forecasted cost for the entire current month. Each line in the chart (and row in the summary table) corresponds to the project, ranked largest to smallest by cost. Learn more about interpreting the billing report chart.

Screenshot of the billing report displaying chart and table using the
default preset view
Figure 1: The billing report displaying chart and table using the default preset view.

Tip: Analyze the usage and cost per SKU

To more accurately understand the details of the pay-as-you-go pricing model and how it impacts your implementation, look at your usage and cost by SKU.

Billing report grouped by SKU
Figure 2: The billing table displaying usage and cost line items by SKU.
Screenshot of the billing report filters
Figure 3: The billing report filters.
To change the report view to display line items by SKU:
  1. In the panel to the right of the chart, expand the Group by filter.
  2. Select SKU.

Other billing-report filters available include Time range, Projects, Products, SKUs, and Locations which lets you filter by where the API requests are served from.

To categorize the source of your usage in addition to the product, group billing reports by one of the listed values. The three keys that relate to Google Maps Platform APIs are goog-maps-api-key-suffix (the final four characters of an API key), goog-maps-platform-type (the platform: Android, iOS, JavaScript or webservice), and goog-maps-channel (a set numeric channel value from an API query). More information on filtering and grouping.

You can change the chart view to exclude usage-specific credits by unchecking the Include credits in cost checkbox in the right panel.

Monitor and restrict consumption

To help you to plan your budget and control costs, you can do the following:

  • Set a budget alert, to track how your spend is growing toward a particular amount. Setting a budget does not cap API usage, it only alerts you when your spend amount gets near the specified amount.
  • Cap your daily API usage, to manage your cost of use of billable APIs. By setting caps on requests per day, you can limit your spend. Use a simple equation to determine your daily cap depending on how much you want to spend. For example: (Monthly spend /price per each SKU)/30 = requests per day cap (for one API). Note that your implementation may use multiple billable APIs, so adjust your equation as needed. Remember, a $200 USD Google Maps Platform credit is available each month, so be sure to factor that into your calculation.

Usage tracking per channel

To track your usage via numeric channels, you must add the 'channel' parameter to your API requests. The only acceptable channel values are numbers from 0-999. Here are a few examples:

  • Geocoding Web Service API
    https://maps.googleapis.com/maps/api/geocode/json?address=1600+Amphitheatre+Parkway,+Mountain+View,+CA&key=YOUR_API_KEY&channel=1
  • Maps JavaScript API
    <script src="https://maps.googleapis.com/maps/api/js?key=YOUR_API_KEY&channel=2&callback=initMap"
    async defer></script>

Monitor your channel usage directly on your Billing Report. Channels will reflect under Labels as key goog-maps-channel.

Filter by Labels
Figure 4: Filter by SKU and Channels
To filter your billing report by SKU and channel
  1. Use the Group by SKU filter.
  2. Select the Labels caret.
  3. Select the Key dropdown and select goog-maps-channel.
  4. Select the Value dropdown and select the numerical channels you want to filter.

Group by Label key goog-maps-channel to see the cost generated by each channel.

Once you have implemented channel usage data in your requests, there may be a short delay (up to 24 hours) before the data is reflected in your billing report.

Export your billing data with BigQuery

You can also export your billing data to BigQuery.

BigQuery Export enables you to export detailed Cloud Billing data (such as usage and cost estimate data) automatically throughout the day to a BigQuery dataset that you specify. Then you can access your billing data from BigQuery for detailed analysis. This gives an extra layer of granularity in understanding the source of your Google Maps Platform usage.

If you'd like to get started with BigQuery exports and querying the data, you can try the sample query below. Prior to running this query, you must:

  • Enable billing and BigQuery billing export on your account.
  • The table format is PROJECT_ID.DATASET_NAME.gcp_billing_exportv1BILLING_ACCOUNT_ID where:
    • PROJECT_ID is your actual project ID (e.g. "my-project-123456").
    • DATASET_NAME is the name of the dataset you created (e.g. "SampleDataSet").
    • BILLING_ACCOUNT_ID is a reference of your Billing Account ID, prefixed with "gcp_billing_exportv1", and changing dashes (-) to underscores (_). For example, billing account ID 123456-7890AB-CDEF01 would become gcp_billing_export_v1_123456_789AB_CDEF01.

  #standardSQL
  SELECT   Date(usage_start_time, "America/Los_Angeles") AS billing_day,
           invoice.month                                 AS invoice_month,
           service.description                           AS service,
           sku.description                               AS sku,
           (
                  SELECT l.value
                  FROM   Unnest(labels) AS l
                  WHERE  l.KEY = 'goog-maps-channel' ) AS goog_maps_channel,
           Round(Sum(usage.amount), 2)                 AS usage_amount,
           usage.unit                                  AS usage_unit,
           Round(Sum(cost), 2)                         AS cost,
           cost_type,
           currency
  FROM     PROJECT_ID.DATASET_NAME.gcp_billing_export_v1_BILLING_ACCOUNT_ID
  WHERE    invoice.month = '202002' -- Change the invoice month with the same format as the example.
  GROUP BY billing_day,
           invoice_month,
           service,
           sku,
           goog_maps_channel,
           usage_unit,
           cost_type,
           currency
  ORDER BY billing_day,
           service,
           sku
  

Cloud Billing:

Google Maps Platform:

Response status and reports

The table below lists the response status, HTTP response code class, HTTP response code class in Usage Report, and indicates if the corresponding request appears in the Usage, Quota, and Billing reports.

Response Status HTTP Response Code Class
(2xx, 3xx, 4xx, 5xx)
HTTP Response Code Class - Usage Report
(2xx, 3xx, 4xx, 5xx)
Usage Report Quota Report Billing Report
OK 2xx,
3xx
2xx,
3xx
Yes Yes Yes
DATA_NOT_AVAILABLE,
NOT_FOUND,
ZERO_RESULTS
2xx 2xx Yes Yes Yes
NOT_FOUND (Street View Static, Geolocation and Roads APIs),
ZERO_RESULTS (Street View Static API)
4xx 4xx Yes Yes Yes
INVALID_REQUEST (invalid parameter value),
MAX_ROUTE_LENGTH_EXCEEDED,
MAX_WAYPOINTS_EXCEEDED,
etc.
2xx/4xx 4xx Yes Yes Yes
INVALID_REQUEST (invalid/missing parameter, request parsing error) 2xx/4xx 4xx Yes No No
REQUEST_DENIED 2xx/4xx 4xx Yes No No
OVER_DAILY_LIMIT,
OVER_QUERY_LIMIT,
RESOURCE_EXHAUSTED,
dailyLimitExceeded,
rateLimitExceeded,
userRateLimitExceeded
2xx/4xx 4xx Yes No No
UNKNOWN_ERROR 2xx/5xx 5xx Yes Yes No

Engagement reports

For Locator Plus users, an analytics dashboard helps you analyze and generate insights from your data, giving a clear picture of how well your shoppers are engaging with your store locator. You can measure your performance week over week, including number of views, number of interactions with Search and Place Details, and overall engagement rate. In addition, the dashboard provides important benchmarks on how your implementation compares against other retailers.

The benchmarking report lets you compare your data with aggregated industry data from other companies who share their data. The comparison provides valuable context, helping you set meaningful targets, gain insight into industry trends, and find out how you are doing compared to your competition.

To see benchmarking data, your engagement data is included anonymously in Google benchmarks. To opt out of both viewing and including your engagement data anonymously in benchmarking reports, file a support ticket. The support ticket will generally be resolved within 3 days.