Guides
for everything Geocodio
Guides
Understanding your usage page
Guides
for everything Geocodio
Understanding your usage page
The Usage page shows what your Geocodio account has been doing, from a monthly total down to a single request. It has three tabs: Overview, History, and Recent lookups.
Lookups, fields and credits
The Usage page splits activity into Lookups, Fields and Distance so you can see where it came from. The split is there for visibility. It does not change how you are billed. A data field append still counts as an additional lookup, and one lookup still uses one credit. See Credits and What's a 'lookup'? for the details.
Overview
Overview covers a single month. Pick the month at the top and the rest of the tab follows it.
Four summary cards. Which cards you see depends on your plan.
A Daily lookups chart. Switch between Chart and Table view, and group it by API key, request type, or country.
A Breakdown table, which regroups the same month by API key, team member, request type, or country.
The Breakdown table has these columns:
| Column | What it shows |
|---|---|
| Name | The API key, team member, request type or country, depending on how you grouped the table |
| Owner | The team member an API key belongs to |
| Lookups | Lookups that row ran |
| Fields | Data fields that row appended |
| Distance | Distance calculations that row ran |
| Returned nothing | Requests that finished successfully but matched nothing |
| % of lookups | That row's lookups as a share of the total lookups shown |
| Last used | The most recent activity for that row |
History
History covers a longer stretch of time. Choose a range from 12 to 60 months and you get a bar chart of monthly lookups, plus a table with one row per month: Month, Lookups, Fields, Distance, and Keys used. Each row has a "View days" action and a "CSV" action, and expands to show a breakdown by API key for that month.
Why past months don't show credits
Months before the current one come from Geocodio's monthly archive, so they are final and will not shift after the fact. The archive records activity rather than credit figures, which is why archived months show no Included or Billable credits.
Recent lookups
Recent lookups is a rolling window of the last 24 hours, newest first, with one row per request as Geocodio recorded it.
A batch request appears as one row, showing its size and, outside Geocodio Enterprise, the first address in it.
A request that geocoded addresses in more than one country still appears as one row, with every country listed in the Countries column.
A geocoded spreadsheet appears as one row once it has finished processing. On Geocodio Unlimited, it appears in chunks as it processes instead.
Click a row to open a detail panel with what Geocodio received, the status, the accuracy type and score, the total response time, and which API key was used. Rejected requests (403) do not include what was sent. Geocodio Enterprise never stores what you send, so on Enterprise the rows and the detail panel leave it out.
What the terms mean
| Lookups, Fields, Distance | A breakdown of your activity, so you can see where it came from. For billing they behave exactly as the Credits guide describes. |
| Included and Billable | Both are expressed in credits. |
| Returned nothing | The request finished successfully but matched nothing. It is not an error, and Geocodio counts it separately from failures. |
| Days | Days follow Eastern Time (ET), which is the clock the daily allowance resets on, wherever you happen to be. |
| Response time | The full time spent on the request. |
What each role can see
Every role can see account totals. Access is narrower for anything that names an individual API key or team member.
| Owner / Admin | Developer | Member | Billing | Read Only | Compliance | |
|---|---|---|---|---|---|---|
| Page totals on Overview and History | ||||||
| Charts and Breakdown grouped by API key | All keys | All keys | Own keys | |||
| API key owner names | ||||||
| Breakdown grouped by team member | ||||||
| Recent lookups tab | All keys | All keys | Own keys |
"Own keys" means the API keys that person created. A Member sees their own keys by name, with everything else gathered into a single "Other keys" row.
Export permissions work along the same lines. See Exporting your usage for the full picture, and Roles and permissions for what each role can do elsewhere in the dashboard.