associating place-ids & other questions[ Edited ]
August 2016 - last edited August 2016 by Terry W
We're having some trouble understanding the exact workings and constraints for associating GMB (Google My Business) locations with place_ids. We're referring to the documentation here.
- can we associate multiple place ids with the same GMB location? The documentation seems to suggest that is not the case, but I'd want a confirmation about that.
- while testing, I created multiple GMB Locations with the same name and address and they show up as multiple locations on the GMB API list endpoint. But we saw that more than one of these places have the same place_id – so we're tending to think that Google does some sort of matching to know if multiple GMB locations are duplicates of each other. Is that correct?
- we see that in all of our tests, the `locationState.isVerified` field is absent. Is it safe to assume the `false` in these cases?
- we noticed that findMatches can only be done on unverified places. What should be the process to associate/remove matches (matches are potential duplicate listings of a place, we assume.) once a place has been verified?
Re: associating place-ids & other questions
Hi @Ashesh A,
- You can’t associate multiple place IDs with a single unverified location because when you send a POST request to associate a location to a specific place ID, any previous association is overwritten. However, you can associate multiple unverified locations to the same place ID. The association must be valid, that is, it appears in the list of locations.findMatches. The placeId field can also be set during the Create call for an unverified location, but not for the Update call. Please note that a location on Google can have only one verified owner and once a location has been verified and is connected to/appears on Google Maps, the placeId field is fixed and cannot be updated.
- Yes, you may get a duplicate locations error in your account if a location you created is a duplicate of another location. Learn more
- If the isVerified boolean field of the LocationState object is absent in your location, that location is not verified.
- The locations.findMatches endpoint finds all of the possible locations that are connected to/appears on Google Maps (not duplicate listings in your account) that are a match to the specified unverified location and returns the MatchedLocation objects listed in order from best to least match. If there is an exact match, it will be in the first position of the list of MatchedLocation objects. You can’t perform this operation once the location is verified because the placeId field is permanent for a verified location.