A connected Google Sheet becomes the source of truth for your locations. You edit the spreadsheet, the app reads it on a schedule, and your map follows. It is the easiest way to run a locator that several people update.
Before you start
Put your locations in a Google Sheet, one row per location, with a header row naming the columns.
A column with the location name is required. Everything else, address, phone, opening hours, tags, is optional.
You need read and write access to the file. The app adds a progus_id column of its own, which is how a row keeps its identity between runs.
Step 1: Connect the sheet
- Open Locations and click Data sources, then Add data source.
- Choose Select Google Sheet and follow the Google sign-in, granting the app access to your Sheets.
- Pick the spreadsheet from your Google Drive, and the sheet inside it if there is more than one.
Step 2: Map the columns
You land on a preview of your data, where you tell the app what each column means. Some are recognised automatically. The name column has to be mapped; the rest are yours to choose. When it looks right, click Save & import now.
How long the first import takes depends on how many rows there are and whether they already carry coordinates. Without coordinates, every row has to be looked up, so a sheet of 2000 locations can take up to an hour.
Step 3: Choose how often it refreshes
Open the source afterwards under Locations → Data sources and set Fetch frequency. There are two settings: every hour, or every day. Between runs your map keeps serving the locations it already has, so a slow or unreachable sheet never empties it.
Keeping the sheet healthy
Do not delete or rename the progus_id column. It is what lets a row update instead of arriving as a duplicate.
Keep the header row intact. If a header you mapped goes missing, the run stops before writing anything and the source is paused, and you get an email saying so.
The sheet is the source of truth: a row you delete removes its location on the next run.
Rows without a name are skipped and counted, so one unfinished row does not stop the rest.
What to do next
"How your locations stay in sync" covers what one run actually does: the checks, the retries, the alerts and the import log.
Prefer a one-off? Bulk import on the same page takes a CSV without connecting anything.
Stuck on any of this? Open the chat in the bottom right corner of the app and we will help you set it up.