It is commonplace for organizations to support multiple applications that use Google Maps APIs, each consisting of multiple environments. Here are some strategies for structuring Google Cloud resources to maintain order and provide the proper level of billing and usage insight.
Google Cloud Project - Separate products, product lines, or applications by GCP Project
API key - Separate applications, application platforms (web, mobile), or environments (dev, test, stage, prod) by API key
Use the table below to determine if the Maps construct gives visibility to the type of metric you are interested in.
|Construct||Usage Reports||Billing Reports||Big Query Billing Export|
|Project||✅ Yes||✅ Yes||✅ Yes|
|API Key||✅ Yes||✅ Yes||✅ Yes|
|Client ID** (Former Premium Plan)||✅ Yes||❌ No*||❌ No*|
|Channels (Labels)||❌ No||✅ Yes||✅ Yes|
* costs for Client ID usage is listed in the billing report as "[Charges for other usage]", when grouping by API key suffix
** not recommended for new code
For more information on Premium Plan Client ID, see the Google Maps Platform Migration Guide.