Skip to Content
GeocodingConceptsUsage, cost and monitoring

Usage, cost and monitoring

For: product owners, customers and platform owners.

What is charged

Only a provider call has a cost. Everything else is free and uses no quota.

SourceCostUses quota
Geofence, Plus Code, coordinatesNoneNo
Internal addressesNoneNo
CacheNoneNo
ProviderOne callYes
Place by hand, rejectNoneNo

A call is charged when the provider responds, even if the place needs review.

Two different prices

PriceWho pays whomWhere it is set
Cost per callThe platform pays the providerPlatform geocoding connection
Plan: monthly price, included calls, price per call over the quotaThe organization pays the platformSettings › Platform › Geocoding › Plan

An organization’s charge in a month:

charge = monthly price + (calls over the quota × overage price)

Overage is charged only if the subscription says Charge overage. With Send to review and Apply the quotas on, when the quota runs out the platform stops calling and new places go to review.

With Apply the quotas off, no call is refused. An organization on Send to review keeps calling over its quota: those calls are not charged to it, but the provider charges them to the platform.

Cost per trip

A place is located once. Later trips to the same place use its geofence. The cost depends on how many new places appear, not on how many trips there are.

Example with assumed values:

AssumptionValue
Trips per month3,000
New places in the first month200
Of those, resolved by geofence, Plus Code, internal addresses or cache120
New places in later months20, of which 8 go to the provider
Cost per callUS$0.005
MonthProvider callsProvider costProvider cost per trip (paid by the platform)
First80US$0.40US$0.00013
Later8US$0.04US$0.000013

What lowers the cost most: geofences already drawn for frequent places, Plus Code in the spreadsheet and addresses written as in the internal sources.

Where to see it

WhoWhereWhat they see
Organization ownerSettings › Trips › Monthly usageCalls against the quota, resolutions by source and result, cache hits, plan charge
Platform ownerSettings › Platform › Geocoding › OrganizationsPer organization: used / quota, cache, provider cost, charge, mode when used up
OperationsSettings › Trips › To reviewPlaces without a reliable point and the reason
Technical teamgeocoding.* metricsResolutions, cache, provider latency and errors, quota refusals

An organization's monthly usage

Alerts

When an organization with a subscription and a quota greater than zero reaches the plan’s alert percentage (80 % by default), the platform publishes the geocoding.quota.threshold event, once per month.

Pitfall: the event does not send messages on its own. For someone to receive the alert, create a rule on that event in the organization. The platform owner receives no alert; check the Organizations table with the On alert or Used up filter.

Audit

RecordWhat it answers
Geocoding usageHow many resolutions, from which source, how many to the provider and at what cost, per organization and month
Trips auditWho resolved, placed by hand or rejected each place, and with which source and geofence
Feed jobs (Integrations › Job console)Which places each feed service tried to locate
Terms historyWhich plan and which quota applied in each month

Details of tables and metrics in Data and metrics.

Risks by country

CountryRiskMitigation
ChileLow for addresses with a number in districts with internal dataWrite street and number as in the official register
PeruHigh: the provider is not certified; many addresses go to review or fall in another districtPlus Code or coordinates in the spreadsheet; drawn geofences
OthersEverything goes to review: no administrative boundaries are loadedCertify the country before offering it
Last updated on