Click here to see your recently viewed pages and most viewed pages.
Hide
Google Maps API for Work

Quota and Reporting

Quota

Client-side APIs in the Google Maps API for Work suite apply page views against the purchased quota. A page view is defined as:

  • A single load of the Google Maps JavaScript API into a page.
  • A single request for a Google Street View Image API image or Google Static Maps API image.
  • A single load of the Google Earth API into a page.

User interactions with a map, such as panning, zooming, or changing map types, do not generate additional page views.

A page view is generated if the API is loaded into the page even if the API is not then used to display a map. We therefore recommend against including the <script> tag that loads the API in page templates, and recommend loading the API asynchronously on pages where maps are only displayed in response to optional user activity.

When you have used all of your purchased quota, you will need to renew your license promptly.

Reporting

You can analyze your usage statistics in two different ways:

  • To get detailed information about your Google Maps API for Work usage as it pertains to billing, access the reports available from the Maps: Usage Report tab of the Enterprise Support Portal.

  • To learn how customers are interacting with your Google Maps JavaScript API v3 application, you can enable Analytics for Google Maps API for Work.

Usage reports

The Enterprise Support Portal provides detailed reports for the Google Maps JavaScript API v3 and the Google Maps Image APIs.

Once logged in to the portal, click Maps: Usage Report from the left navigation panel. You can filter by channel and by date range.

The data in these reports is the same data that Google uses when determining your usage-based billing.

Channel reports

To track usage across different applications using the same client ID, you may provide an optional channel parameter with your requests. By specifying different channel values for different aspects of your application, you can determine precisely how your application is used.

For example, your externally-facing website may access the API using a channel set to customer while your internal marketing department may use a channel set to mkting. Your reports will break down usage by those channel values.

Channel reporting is available for applications using the Google Maps JavaScript API v3, the Image APIs, the Google Earth API, or any of the Google Maps API for Work services.

The channel parameter must use the following format:

  • Must be an ASCII alphanumeric string.
  • Period (.), underscore (_) and hyphen (-) characters are allowed.
  • The channel parameter is case-insensitive; upper-case, mixed-case, and lower-cased channel parameters will be merged into their lower-case equivalent. For example, usage on the CUSTOMER channel will be combined with the usage on the customer channel.
  • The channel value must be a static value assigned per application instance, and must not be generated dynamically. You may not use channel values to track individual users, for example.

Up to 2,000 distinct channels can be used, per client ID.

The channel parameter should be appended to the src value of your script tag:

<script src="https://maps.googleapis.com/maps/api/js?v=3&client=gme-yourclientid&channel=YOUR_CHANNEL"></script>

Analytics for Google Maps API for Work

With Analytics for Maps API for Work you can learn how people are interacting with your maps so that you can improve your application based on real usage statistics. Analytics for Maps API for Work answers such questions as:

  1. What zoom level and map type are most common?
  2. For which countries are users requesting geocoding results?
  3. How often are the JavaScript services used?

Analytics can be enabled without any changes to your code, and all data is aggregated and anonymized to protect users' privacy. Reporting is available for the JavaScript v3 API and related services.

This *Zoom Interactions* report shows that, for the sites associated with
this client ID, most users are using zoom levels between 4 and
7.

Access Analytics

Visit the Google Enterprise Support Portal and select Maps: Analytics from the Resources list. If you have multiple client IDs associated with your account you will be asked to select the client ID and channel you wish to use each time you access Analytics.

Enable Analytics for your Client ID

Analytics is disabled by default and must be enabled on a per client ID basis. You will be asked to confirm that you want to enable Analytics the first time you try to access the reports for each client ID. It can take up to 5 minutes for Analytics to start recording data after this process has been completed.

It is not necessary to modify your existing code, unless you intend to utilize the channel feature and do not currently specify a channel when loading the JavaScript library.