Want different pages on your website to show different subsets of your locations? You can start each page with selected groups, then choose whether visitors stay inside those groups or can clear the selection to see all locations.

That choice applies to this page. You can also set the default for existing installed pages under Widget > Settings. The default applies only to pages that already start with selected groups. Pages without selected groups still show all locations, and a choice made on the Install page takes priority.

The URL and data-attribute methods below are useful when you edit code by hand. A visible filter in a ?filters= link is a clearable starting selection. A hidden filter preselected through ?filters= or data-storerocket-filters stays applied through Clear and Show all for backward compatibility. For a new fixed page, use No, only these groups on the Install page.

You can pre-filter by filter slug or filter ID. Both work exactly the same way, so use whichever you find easier to read.

Go to your Filters page.

Two things worth knowing about slugs:

The filter's display name never works. ?filters=Whole Foods Market will not match anything. It has to be the slug or the ID.

Add ?filters= to the page URL where your store locator is embedded.

Single filter:

Multiple filters:

This is handy when you want one page to serve several different pre-filters, for example from links in a nav menu or from your product pages.

?search= does the same job for location instead of filters. The widget geocodes whatever you pass, drops it into the search box, and centres the map there on load:

Any city, postcode or address works, and it combines with the filter parameters:

If you want every visitor to start in the same place rather than a specific link, set the initial map position under Widget > Settings instead. One thing to watch: if your widget is set to use the visitor's own location on load, that wins over a fixed starting point for most people, so turn it off in the same screen if you want the fixed position to apply.

You can also bake the pre-filter straight into the embed code by adding data-storerocket-filters to the same div that already has your data-storerocket-id:

Multiple filters:

IDs work here too, and you can mix both formats in the same list if you want:

Use this when you want different embed codes on different pages, each showing a different set of locations.

By default StoreRocket uses AND logic, which means a location has to have every filter you list to show up. Listing whole-foods-market,fresh-thyme shows only the locations tagged with both, which is often zero.

You can change this in two places.

Per embed (recommended when only one page needs it) — add data-storerocket-filter-operator:

Use or to show locations tagged with any of the filters you list, or and to show only the ones tagged with all of them. Leave the attribute off entirely and the widget follows your account setting exactly as before. any and all work as alternative spellings.

This also works as a URL parameter, so one page can serve both: ?filters=whole-foods-market,fresh-thyme&filter_operator=or

For the whole account — go to Widget > Settings and change the filters behaviour dropdown to "Show locations that have ANY of the selected filters". This affects every embed that doesn't set the attribute itself.

When in doubt, start with a single filter and confirm the results before adding a second one.

Hidden filters work as pre-filters too, using either the slug or the ID. Hiding a filter removes it from the visitor controls. When that hidden filter is also preselected through a URL or embed, StoreRocket keeps it applied through Clear and Show all. Hiding the filter on its own does not limit a page. For a new fixed page, choose No, only these groups on the Install page.

Edit any filter on your Filters page and toggle Visible off. It disappears from the widget's filter list but still works in ?filters= and data-storerocket-filters.

When filters are pre-selected, the store locator loads with those filters already active. With No, only these groups, Search, Clear and Show all stay inside the installed page groups. With Yes, start with these groups, visitors can clear visible starting selections to see all locations. Hidden preselected filters keep their legacy fixed behavior.

The map is empty after adding a pre-filter. Check these in order:

Only one brand or category is showing and I didn't ask for that. Someone may have left a data-storerocket-filters value in your embed code from an older campaign. View the page source and search for data-storerocket-filters on the widget div.

If you need completely separate store locators (different locations, different settings), create separate projects instead. See How to create multiple store locators.

For a full guide on filters, see How to use search filters.