Your Google Sheet may keep changing as people add locations, correct addresses, and update statuses. The team needs a geographic view that still represents the records they're working on, so they can use the map alongside the list.
When someone returns to the map after another round of edits, they need to recognize which records they're seeing. A corrected address belongs to an existing record, while an added location may be a new one. The team also needs to know whether the view reflects the Sheet's latest changes.
| Sync choice | Source-to-map behavior | Map-to-sheet behavior | Check before relying on it |
|---|---|---|---|
| One direction | Sheet changes flow to Maptive | Map edits don't automatically return to the sheet | Change a source field and inspect its mapped record |
| Two directions | Sheet changes flow to Maptive | Use the sync button to send map data changes back | Test a reversible edit in each direction |
Prepare the Sheet for a connection
Use a header row with clear column names. Each following row should represent a location or record you want to map. Keep the fields needed to place it, along with the identifying and business fields you need to inspect on the map.
For an address list, separate the address, city, state, and ZIP code where those fields are available. If you're using latitude and longitude, keep them in clearly named columns. A category or status column is useful when you want to check how a source change appears in the map's data or marker display.
Choose what one row represents. A customer with several service locations can legitimately have several rows. Several jobs at the same address can also be separate records. Your identifier needs to distinguish those records if you want to keep them separate through updates.
A stable ID is often the simplest choice. Keep the same ID when the record's address or status changes. A spreadsheet row number isn't a suitable long-term substitute, because sorting or inserting rows changes its position. A customer name can repeat, too, so don't assume a name identifies one location.
Where possible, give one person responsibility for the source structure. Other people can update agreed fields, but everyone should know which sheet supplies the map and which columns the connection depends on. Once connected, avoid casually renaming identifier or location headers. Check any planned structural change before applying it to the working list.
Create the connected map
In Maptive, click Create New Map. Give the map a name, add a description if useful, and click Continue. Under Your Data, choose Google Sheets.
An exported spreadsheet file gives you a copy of the data at the time you export it. The Google Sheets connection is the option to use when the list will keep changing.
Use a name that helps you recognize the purpose of this connection later. If you manage several changing lists, include the region or work type. A short description can identify the source sheet and the person responsible for its data.
The connection setup then presents Sync Google Sheets Method. Decide how changes should flow before continuing. This choice determines whether you keep all source changes in Google Sheets or also use Maptive to send edits back.
Keep the intended sheet available while you work through setup. Check its name and headers rather than selecting a similarly named copy. A successful connection to the wrong sheet can produce plausible markers while leaving your actual working list disconnected.
Choose how edits should flow
Keep the Sheet as the source
Choose Sync 1 Direction: Google Sheets >> to >> Maptive when Google Sheets should supply the map's updates. This is a useful arrangement when people already maintain the list there and Maptive is where they inspect its geography.
In this mode, map edits don't automatically return to Google Sheets. If someone corrects a business field in the map, don't assume the source sheet has received that correction. Make the agreed source change in the sheet and check the corresponding record in Maptive.
A one-direction setup gives the team a clear place to maintain the list. It also makes your first update test easier to follow, because you can change a single source value and inspect what reaches the map. Keep that source responsibility clear after the map is shared.
Allow changes in both directions
Choose Sync 2 Directions: Google Sheets >> Maptive and Maptive >> Google Sheets when you want changes to flow in both directions. The reverse direction uses the sync button to send changes from the map's spreadsheet data back to Google Sheets.
Plan that action as part of the editing workflow. Someone making an edit in Maptive should know when to use Sync and where to check the result in the sheet. Don't treat a saved map edit as proof that a source cell has already changed.
Choose your mode, then click Continue. Select or sign into the Google account when prompted. Use an account with access to the intended sheet, choose the sheet, and click Select.
Before people start editing in both places, agree on who owns corrections and when each person should work. If simultaneous edits will be part of the job, test that behavior using noncritical data. A direction choice alone doesn't tell you what will happen when two people change the same field at once.
Tell Maptive which records match
Use an ID column
At Select a Unique Identifier, choose Id Column if your sheet has a suitable ID field. Use an ID that's unique for each record and remains the same as the record changes.
Check the IDs in the source before relying on them. Blank IDs and repeated IDs can prevent a clean match between the old and new versions of a row. Two locations owned by the same customer may need different location IDs, even if they share a customer ID.
Choose the record level that matters for the map. If one row represents a job, a customer ID shared by all that customer's jobs won't distinguish them. If one row represents a branch, the branch's own ID is more useful than a company name shared by every branch.
A good identifier lets you change an address without changing the identity of the record. That is useful when a location moves or when someone corrects a misspelled street name. Run Check before you create the map so the setup can check the chosen identifier.
Use address-based identifiers carefully
You can also choose Address Column as Unique Identifier. Select the field in the Address Column dropdown and use the Additional Column dropdown when another field is needed to distinguish records. Add Another Identifier lets you add another identifying field.
An address combined with a city can distinguish otherwise repeating address text. Check your actual list rather than assuming those two fields will always be enough. Several records can share a full address, and some cities can share a street name and number.
Check address-based identifiers when addresses will change. If the fields used to recognize a record are edited, test how that change appears in the connection. For a frequently changing list, a stable ID can be easier to manage than an identifier built from editable location details.
After selecting the identifying fields, click Check. Resolve any identity problems before continuing, then click Create New Map. Record the chosen fields so the person maintaining the sheet knows which values the connection uses.
Confirm the location matches
Inspect the dropdowns on Categorize Data. Match your actual address, city, state, ZIP code, latitude, and longitude columns where they exist. Use No Match for a field you don't have. You don't need to manufacture a coordinate column just because the screen offers one.
Check the name field as well. It supplies the title or hover information that helps you recognize a location. An ID may help you match records, while a branch or customer name can make the visible marker easier to understand.
Click Done after checking the matches. Inspect a few known places on the finished map. Include records from different cities or regions, along with any address format that differs from the rest of the list.
If a point appears in the wrong place, first inspect its source address and the category matches. Correct the actual problem before judging the connection's update behavior. A marker placed from the wrong column can obscure whether the right record was updated.
Test updates in the working map
Make a reversible change to one record in Google Sheets. A category or status field can be a convenient first test because you can identify the record without moving it. Check the corresponding marker and its data in Maptive, then restore the original value.
Add a distinct test row with a unique identifier and a known location. Confirm that it appears as the added record you intended. Check both its position and its identifying fields so you know it wasn't confused with an existing row.
If you chose two-direction sync, make a reversible change to a field in the map's data. Use Sync, then inspect the corresponding cell in Google Sheets. Restore the value through the agreed editing process and verify the result in both places.
Observe how long your tests take and how you confirm that changes have arrived. Don't build a workflow around an assumed fixed interval or instant write-back. If an update is needed before a daily review, include a check of the relevant records before that review begins.
Test row deletion separately before using it on important records. When you remove the test data, inspect both the sheet and the map to see what remains. Use the same care with changes to identifier fields and with simultaneous edits if those actions will be common.
Record the selected mode, identifying columns, source owner, and results of the update tests. Keep Google Sheets access separate from map-view access. A recipient who only needs to explore the shared map doesn't need editing access to the source sheet.
