Managing spend.
WHY IT REQUIRES ATTENTION
Costs scale directly with usage, and a public page with a map is called by every visitor and every bot.
WHAT DRIVES COST
Map loads Autocomplete requests Place details, by fields requested Matrix elements Geocoding requests
WHAT TO DO FIRST
Establish which products you call, and the cost of each.
WHAT TO SET
Daily quotas per API, below what a runaway would consume Budget alerts at several thresholds
WHY QUOTAS SPECIFICALLY
They are the only hard stop. Budgets alert but do not prevent.
WHAT TO IMPLEMENT
Session tokens for autocomplete Field masks on details requests Static maps where interaction is unnecessary Caching, within the terms Debouncing user-triggered requests
WHAT TO RESTRICT
Keys, so scraped keys cannot be used elsewhere.
WHAT TO MONITOR
Requests per API, per day Any sudden change
WHAT A SUDDEN RISE USUALLY MEANS
A defect, a loop, or a key being used by someone else.
WHAT TO REVIEW
Whether you could use a cheaper product for the same outcome.
