Case Study: How a Customer Shaped MetForm’s Google Places Map Search

Most feature requests sit in a backlog for months.

This one shipped in four days.

Here is the story of how one chauffeur company in Switzerland pushed us to look closer at the MetForm Map field, and how that single conversation turned into a better Google Places experience for every MetForm user.

Let’s dig in.

First, What Is the MetForm Google Map Integration?

Before we get into the problem, let’s cover the basics.

MetForm is our Elementor form builder for WordPress. When you want to add a location field to a WordPress form, the Google Map integration lets you add a map field, and your visitors get live location suggestions as they type, powered by Google.

Here is how it works under the hood:

• Get autocomplete: Once connected, a plain text box turns into a smart location search that suggests results as the visitor types.
  Who the Customer Is
• Connect with a key: You link MetForm to Google using a Google API key.
• Enable the right APIs: In your Google Cloud console, you turn on the APIs you need. For location search, that means the Google Maps API und das Google Places API.

Who the Customer Is

The customer is Nicola Cibin, who runs Prime Limousine, a premium chauffeur and transfer service based in Switzerland. His website runs on WordPress, and his booking flow uses MetForm, our Elementor form builder.

The important part is the form itself. It has two location fields powered by the MetForm Google map integration: a departure field (labeled Partenza) and an arrival field (labeled Arrivo). When a visitor books a ride, they type where they are starting from and where they want to go.

It’s simple, and for a limousine service, that simple form is the whole business.

The Challenge: The Google Map Field Only Showing Addresses

Here is the problem Nicola ran into.

His customers do not always book by street address. They book by place names. They type things like the name of a hotel, an airport terminal, or a well-known landmark. That is how real people think about where they are going.

But the Map field was only suggesting street addresses. When a customer searched for a hotel, nothing useful came up.

In Nicola’s words from the ticket, the address suggestions were working, but businesses and points of interest such as hotels were not appearing in the suggestions.

So the field was behaving like an address directory, not a Places search. For a chauffeur business, that gap is not a small annoyance. It is a booking that does not get completed.

And here is the part that made it frustrating for him. He had already enabled the Google Places API in the Google Cloud console. According to our own documentation and the Google Map Location widget setup, both Google Maps and Google Places APIs were supposed to work. On paper, this should have already been possible.

The Investigation: What We Checked First

When a report like this comes in, the first job is to separate what works from what does not.

Our support engineer, Ikbal, started there. Since the address suggestions were loading properly, it indicates that the Google API key and the basic map integration were already working. A broken key would show nothing.

So the real question became narrower. Was the Map field configuration filtering results down to addresses only, or could it return Places and POI results at all?

To check the frontend behavior properly, we asked Nicola for a short screencast covering:

• His field configuration
• His Google API settings
• How the autocomplete behaved when he typed

He sent a video. On his side, everything in the Google Maps API was enabled, yet places still would not load.

That video mattered. It moved the conversation from “it should work” to “let’s see exactly what the plugin does on a real site.”

The Honest Part: A Request That Got Pushed Back

Now, this case study would be dishonest if we skipped the middle.

The first answer Nicola got was that this capability was not currently available in MetForm and that we had logged it as a feature request for the roadmap.

He did not accept that. And he was right to push.

He pointed straight at our own Map integration documentation, which explains how to enable the Google Places API for search features. He had purchased a Premium license specifically because the documentation said this was supported. From his side, he was asking for something the product had promised.

Let’s see why his request was valid –

❌ Not requesting advanced functionality such as: Custom pin dropping, selecting arbitrary map coordinates, or capturing latitude/longitude from the map.
✔️ Simply expected standard Google Places results in the search suggestions, not just addresses

That clarity is what turned a vague “make the map better” request into a specific, buildable task.

The Solution: A Fix, Not Just a Roadmap Note

Once the scope was clear, the ticket was escalated to the development team. They investigated the plugin behavior directly and found it.

The MetForm Map widget had a limitation that caused certain locations, including Places and points of interest, not to display properly in the search suggestions.

So the team did two things:

• Resolved the limitation so the Map field returns Google Places results, not just addresses.
• Added improvements to the Map widget while they were in there.

The fix was delivered the way plugin fixes should be: through a normal update. Nicola updated both MetForm kostenlos Und MetForm Pro to the latest versions, cleared his site and browser cache, and checked again.

And the timeline is the headline here. From deciding on the conversation to shipping the fix, it took about four days.

The Result

Nicola confirmed it himself. The places were now appearing correctly in the list, in addition to the addresses that were already working.

His booking form now does what a chauffeur booking form should do. A customer can type a hotel name and actually find it.

Here is what changed, at a glance:

Vor	Nach
Map field returned street addresses only	Map field returns Google Places (businesses, POIs) plus addresses
Hotel and landmark searches came up empty	Place-name searches now surface real results
Feature “documented” but not working as expected	Feature working on the live site, confirmed by the customer

Before:
The list showed addresses correctly, but it did not show places yet. Only part of the data was appearing.

Nach:
The list now shows places correctly too. Addresses still work as before, and places have been added alongside them.

What This Says About How MetForm Gets Built

So, why tell this story at all?

✓ Well, it shows how our roadmap actually moves. Not by guessing. By listening to a real user with a real problem, then building.
✓ A feature request isn’t forgotten when it’s specific. It needs a clear use case. It should line up with what the product promises. Then it can move fast.
✓ And of course, it helps when the request comes with a valid, well thought out approach, like this one.

The quiet truth: The best feature requests aren’t the loudest ones.

Abschließende Gedanken

One customer needed his booking form to understand hotels, not just house numbers. Four days later, every MetForm user could do the same.

Here are the points worth keeping in mind from this story:

1. A working address search and a working Places search are not the same thing. Enabling the API is step one, not the finish line.
2. If a feature is in your documentation, a customer is right to expect it to work. Documentation is a promise.
3. Clear, specific feedback moves faster than angry, vague feedback. Scope is a gift to the team building the fix.

Users do not just want a product that works today. They want a team that listens when it does not.

NOTE: If you use the MetForm Map field and you want place-based search on your forms, make sure you are on the latest version of MetForm Free and Pro, then enable the Google Places API in your Google Cloud console.

Häufig gestellte Fragen