Follow
  • MDX: Manage > Ads > New > Design New HTML5 Ad > Components > Store Locator
  • Sizmek Advertising Suite: Creative > Ads > New Ad > Design HTML5 Ads > Components > Store Locator

Overview

Important: This is a premium ad feature and entails additional costs. For more information, please contact your Sizmek client services manager.

The HTML5 Store Locator component finds the closest stores based on a mobile phone location using GPS, zip code, city, or state. After the location is found, the user can click the location, call the location, receive driving directions, and view the company's virtual business card including the company logo and contact information. This component uses Google Maps direction services.

           

The Store Locator component includes a predefined placeholder poster, a standard map theme with industry defined icons and buttons, and an e-business card for the store. You need to add the csv file, and then you can customize settings. 

  

By default, the Store Locator returns all of the store locations within a predefined radius. The default is set to 10 kilometers, but you can also switch to miles. All stores listed in the csv file are displayed on the map. The user sees the stores in the predefined map and can zoom in or out to see additional stores.

The following table describes the different location points in the Store Locator component.

Location Name Icon Description

'Point of Interest' Location

The Point of Interest location is the store location. The stores are displayed on the maps based on a predefined Point of Interest csv file that you need to build and upload to the ad.
'You are Here' Location   Current location of the user. In case the system cannot detect the user location, the fallback starting point address is used.
'Return to Original' Location

 

Allows the user to return to their original location if you moves away on the map. 
'Fallback Starting Point' Location  N/A Address used in case the user's current location is not found. If you do not assign a fallback address, the component uses the center of London as the default location.

Supported Platforms

PLATFORM

SUPPORTED VERSION

iPhone

iOS 8.0 and later – supported only in IOS 10

iPad

iOS 8.0 and later – supported with limitations in IOS 8, fully supported in IOS 10

Android

Android 4.1 and later( including tablets) – supported Android 5 and up

Configuring the Store Locator Map 

The Map tab contains generic map settings. You can change the map theme, decide whether to show or hide the search box, determine the map units (miles or kilometers), and define the initial map radius.

When your done, remember to preview and test that the locations are displayed accordingly in the platform preview.

Map Tab

Field Description Default Settings
Select/Upload Placeholder Image You can replace the generic placeholder image.
Map Theme Provides four predefined themes. The standard map theme is the default theme.
Select a theme from the Map Theme List to change the theme.
Note that the placeholder image remains the same for all themes.

                  

Show Address Search Box Adds the Search Box option to the map.

Map Units The default map units are defined in kilometers. Select Miles to change the map units to miles.
Initial Map Radius By default, the Store Locator returns store locations within a radius of 10 kilometers from the starting location. However, this can be changed by updating the field.   
Location Images You can use the generic images for the different locations or upload and replace with your own. For more information on the locations, see Locations.  



Configuring the Points of Interest

In the Point of Interest tab, you are required to import a list of your stores. When the user selects a location, a personalized virtual business card is displayed which can be customized to meet your needs.

Prerequisite

Create the 'Point of Interest' file that is the basic csv file that lists the stores. If the csv file is not uploaded, the store locator will function as a standard map.

  1. Create a csv file and manually add the list of store locations to your 'Points of Interest' file. You can either create your own csv file, or download our sample csv file that contains one example address. 

    Important: The CSV format uses the comma to separate values. Do not use commas in location names, addresses, and any contact values.

  2. Save your file with the .CSV extension.
Procedure
  1. In the Store Locator Properties panel.
  2. Click the Point of Interest tab.
  3. In the 'Upload 'Point of Interest' File area, upload your user-defined csv file.
    After the csv file has been uploaded in the Properties tab, it is automatically converted to a JSON file and cannot be download for future updates. 

    Important: Please save a copy of your csv file prior to uploading the file in case you want to update the list. Make sure to rename the updated csv file prior to uploading it to the ad.

  4. Modify the e-business card.
    Each button has its own unique generic icon but you can update it with a customized image, for example, a different color or company logo. 
    The images are automatically adjusted to the size of the standard images. The default settings are displayed in the following image. 
  5. Upload your ad and preview the ad in the platform Preview Device Simulator.

MDX2.0 Publisher Site Only: Retrieving the User Location from the DSP

Sizmek determines the user location in the Store Locator component based on the mobile geo latitude and longitude values retrieved as tokens from the publisher's DSP site. 

During ad serving, the user's location needs to be detected so that the map is centered according to the location.

The publishers need to configure mobile app tokens in the Sizmek MDX 2.0 platform. After configuration, the generated publisher placement tags and tracking pixels include dedicated mobile parameters, which may be replaced in real-time by the publisher ad server technology. This option requires a one-time setup for each publisher.

These tokens do not automatically capture the corresponding device IDs. Publishers must configure their ad server to pass the correct values into the applicable tokens. Before implementing these tokens, Sizmek recommends that the client contact the publishers regarding the media plan directly to confirm that they will provide this data. Sizmek is not responsible for validating the data that publishers pass, or do not pass, through these tokens.

Perform the following workflow for each publisher site prior to configuring the Store Location component:

  1. On the site level, add mobile tokens to your tag. The location tokens are replaced in the URL with the relevant data from the Sizmek server before being sent along on the URL.
  2. On the placement level, generate the code including the tags and publish the placements. 
Prerequisite

Contact the publisher and request for the following device tokens.

Name Token Description Notes
Mobile LAT Geo Location ebmblat Latitude of the mobile location This ID, obtained from the SDK, is only available if the information is exposed.
Mobile LONG Geo Location ebmblong Longitude of the mobile location This ID, obtained from the SDK, is only available if the information is exposed
Procedure 
  1. In the MDX platform, on the site level, perform these steps to place the device token variables that you received from the publisher.
    1. Access the Site section, click System Administration > Accounts > Setup > Account Settings > Site Server Settings section. 
    2. Select the Enable Mobile Tokens check box.
    3. In the Mobile Geo Latitude and Mobile Geo Longitude, type the publisher variable.
  2. Perform these steps to generate a placement code to be sent to the publisher.
    1. Access the Manage > Placements > Tags tab and select the Serving Settings section.
    2. Click Generate Code.
    3. Send the tags to the publisher to be placed on the site.
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments