Add a store locator to Drupal

Module available as a downloadFor Drupal 10 and 11 with its own block "My Store Locator map". The embed code keeps working.

Published on drupal.orgVersion 1.0.0 since 7 November 2026. Install with Composer: composer require drupal/my_store_locator. Updates then come through Composer.

My Store Locator for Drupal

Module · Version 1.0.0 · 50 KB

Works with: Drupal 10 and 11

Download zip

File my_store_locator-1.0.0.zip · SHA-256 ecc897489fedfabc734162a923fd13a7ceb893575d49de965ad10e916593bd8e

What you get

A location map with list, search and filters on your Drupal website. You manage locations in My Store Locator; Drupal only shows the map.

Before you start

A My Store Locator account (sign up free)
A published map (status "Live")
For our module, access to the files of the Drupal installation (or your agency)
For the way without our module, the embed code from the Embed Studio in the app and permission in Drupal to use the Full HTML text format (or another format that allows <iframe>)

Install the module

Download the zip file above and unzip it.
Copy the folder my_store_locator to modules/contrib/ of your Drupal installation (in Composer projects usually web/modules/contrib/).
Open Extend, tick My Store Locator and click Install. With Drush: drush en my_store_locator.

Connect to My Store Locator

Open Configuration → Web services → My Store Locator (/admin/config/services/my-store-locator).
Paste the token into the Default map token field. The embed code or the map link work too. Or click Connect with My Store Locator, log in and pick your map (HTTPS sites only). Click Save configuration.
Open Structure → Block layout, click Place block in a region (for example "Content"), then Place block next to My Store Locator map. Untick Display title, set the path under Visibility → Pages if needed (for example /stores) and click Save block.

Two-click consent (Consent mode (click to load)) is on by default. If you leave Map token empty in the block, it uses the default token. Each block can have its own map and settings.

Updates

Drupal does not update a module installed from a zip by itself. For a new version, replace the folder my_store_locator with the one from the new zip and then run /update.php (or drush updb). If you installed the module with Composer, get new versions with composer update drupal/my_store_locator and then run drush updb. Project page: drupal.org/project/my_store_locator (external link).

Without our module: as a content block

In Embed Studio, copy the code from the iframe tab.
Open Structure → Block layout and click Place block in the region you want.
Choose Add content block and set the text format below the field to Full HTML.
Switch the editor to code view with Source and paste the code.
Save, set under Visibility → Pages where the block should appear, and save the block.

<iframe src="https://app.my-store-locator.com/#/m/YOUR-TOKEN" title="Store locator" style="width:100%;height:640px;border:0;max-width:100%" loading="lazy" allow="geolocation"></iframe>

Alternative: inside the content

For a single page such as "Locations" you can paste the code straight into the content's text field: choose Full HTML, switch to Source, paste the code and save.

In Embed Studio, turn on "Load the map only after a click (GDPR)" and copy the code again. Visitors then see a placeholder with a privacy notice first, and the map only loads after a click. More under GDPR & security.

If the map does not show up

Code gets stripped: the chosen text format does not allow iframes. Use "Full HTML" or add <iframe src title style loading allow> to the format's allowed tags.
Block not visible: check the region, visibility rules and whether the block is enabled.
"Map not available": the map is still a draft. Publish it in the app.
Content Security Policy: if your site sends a CSP, frame-src must allow app.my-store-locator.com (for the widget also script-src).

All options are explained in the embedding guide.

FAQ

Do I need an extra module?

No. Blocks and text formats are part of Drupal core and are enough. Our module saves enabling "Full HTML", connects your account and brings two-click consent.

Is "Full HTML" a security risk?

Only grant the format to trusted roles. Alternatively, create a text format that allows just the <iframe> tag with the attributes it needs.

Does this work with Drupal 7?

The steps are similar, but the menus look different. Drupal 7 no longer receives regular security updates.