Every search your shoppers run is a small piece of market research: a town you have no stockist in, a product nobody near them carries. The Analytics page in the app collects it.
What is on the page
Most popular locations: which of your stores shoppers actually look at.
Most popular countries, provinces and cities: where the people searching are, which is not always where your stores are.
Search heatmap: the same demand on a map, which is the fastest way to spot a gap.
Searches summary: the underlying list, which you can export as a CSV.
A card reading "No data available" means nobody has searched that way yet, not that something is broken. A new locator takes a while to say anything.
What to do with it
A city high in the searches with no location near it is a stockist worth recruiting, and your dealer form is how you recruit them.
A product searched often and stocked rarely is a distribution problem you can now name.
A location nobody ever opens may simply be listed wrongly: check its address and its tags.
Sending the events to Google Tag Manager
If you already measure your storefront in GTM, the locator can feed it. It sends interaction events to the page that contains the map, and a small listener on that page pushes them into the dataLayer. Settings → Installation has the card, the listener to copy and a step-by-step guide.
Two things people get wrong. The listener goes on your storefront page or in GTM, never inside the Progus embed code. And in a GTM Custom HTML tag you paste the snippet exactly as shown, including the script tags, because without them the listener never runs. If you do not use GTM, skip the whole card: the map works without it.
Stuck on any of this? Open the chat in the bottom right corner of the app and we will help you set it up.