Statistics and usage
Your account's Statistics page displays usage information for all billable products found on the pricing page.
To access the Statistics page, log into your account and navigate to account.mapbox.com/statistics.
The purpose of the Statistics page is to provide insight into an account's usage data for the billable products listed on the pricing page. Information about API rate limits, API performance, and HTTP status codes of requests to the Mapbox APIs are not displayed on the Statistics page. Please visit the API documentation for additional information about each service.
There are two ways to filter the Mapbox usage data on your Statistics page:
- By date: Choose a standard period (such as week or month) or enter a custom date range. All dates are in UTC (Greenwich Mean Time). Usage data will be available on the Statistics page within 24 hours.
- By access token: See usage for all access tokens or one specific, active access token. Legacy SDKs for Mobile statistics are not available when filtering by access token. To see Legacy SDKs for Mobile statistics, filter by All tokens and connected apps.
Your account usage is organized by product on your Statistics page. For each product, you'll see the number of metered units for the token and time period selected.
You will only see statistics for the products you’ve used within the specified time period and with the specified token. For more detailed explanations of how usage is metered for each product, see Pricing by products.
For many products, you can load additional metrics about the Countries, Browsers, Domains, and Tileset IDs associated with your requests. These additional metrics are presented as percentages of the total number of metered units for the specified time period and token.
Additional metrics are not available for products that are metered by user count (such as Maps SDK for Mobile). They are also not available for time periods exceeding 31 days.
When you see Not set as an additional metric value, it means that for some requests we are not able to find a value for that metric. With the additional metric Domains, for example, Not set means the request did not include a referrer from which we could parse a domain, which may because your requests are not coming from web browsers, or because you are using a legacy version of GL JS. Upgrading to the latest version of GL JS should reduce the number of Not set domains and is a requirement for implementing URL restrictions.
When you see Other as an additional metric value, it means our systems are not able to convert the value to a legible display format. For example, for the additional metric Browsers, Other means we are not able to simplify the request's user agent to a display format.
When an access token is deleted, caching throughout our global infrastructure may result in successful requests to that deleted token. Caching settings vary - not all Mapbox services cache requests for the same length of time.
It is not possible to isolate statistics for a token after it has been deleted. Deleted tokens do not show up in the drop-down filter list, rather, usage data tied to a token before and after its deletion will be aggregated in the All tokens and connected apps view.
Temporary tokens (
tk) are not displayed in the drop-down filter list. Instead, usage data tied to temporary tokens will be aggregated in the All tokens and connected apps view. To visualize statistics generated by
tk tokens in a time period, append
?&token=tk to the end of the statistic page's URL.
It's possible that your Mapbox implementation is using a legacy version of a Mapbox service that does not pass access tokens to our servers when requests are made. If this is the case, usage data cannot be isolated by token. Usage in this category will be aggregated and displayed when the All tokens and connected apps view is selected.
Similarly, Legacy SDKs for Mobile statistics are not available when filtering by access token. To see Legacy SDKs for Mobile statistics, filter by All tokens and connected apps. To isolate MAUs by token from a point in time moving forward, upgrade your applications to the latest versions of the Maps SDKs, and review statistics after the update is deployed.
If you've set the custom date on your Statistics page to match your billing cycle and notice a discrepancy in the values of services you were billed for, it's most likely an issue with timezones. Requests attributed to your billing period that were not invoiced during that month will roll over to the next invoice.
Have questions about the Statistics page? Let our Support team know- we're happy to help!