Mappedin Web v2 Integration Guide
Mappedin Web v2 Integration Guide
The following guide will walk you through how to integrate Mappedin’s Responsive Web App with your website.
Read more about Mappedin Web at https://www.mappedin.com/wayfinding/web-app/
Mappedin Web is a fully packaged solution that can be easily embedded into your website by following this simple guide. Once it's configured, you will have ongoing access to the Mappedin Web platform as it continuously evolves and improves with new features and data driven learnings. Customers using Mappedin Web will always have the best version of our product, with out of the box features including:
- An interactive 3D map
- Location search and category listing
- Turn by turn directions
- A details page for each location including deals,photo gallery, external links, and related locations
- A mobile first, app centric, responsive design
- Deep linking support
... and more.
Before embedding Mappedin Web, please ensure the following requirements have been met
- Venue is fully mapped and tested (demo links will be provided to preview the front-end experience)
- Location data is up to date and ready for production
- Mappedin venue and search keys have been provided to you
Place the following external stylesheet in your
<link href="https://d1p5cqqchvbqmy.cloudfront.net/web2/release/mappedin-web.css" rel="stylesheet" />
If you wish to display different languages for Mappedin Web, you can specify the language via the
language property dynamically from outside Mappedin Web so that you can translate the website where it is embedded while also translating the app’s UI at the same time.
You can access the language property directly like this:
window.mappedin.language = "fr" .This configuration needs to be set before the external mappedin script loads.
Currently supported languages include:
- Catalonian (CA)
- Danish (DA)
- Dutch (NL)
- English (EN)
- Finnish (FI)
- French (FR)
- French - France(FR-FR)
- German (DE)
- Greek (EL)
- Hungarian (HU)
- Italian (IT)
- Japanese (JA)
- Korean (KO)
- Portugese (PT)
- Romanian (RO)
- SimplifiedChinese (ZH-CN)
- Spanish - EU (ES)
- Spanish - US (ES-US)
- Swedish - Finland (SV-FI)
- Ukrainian (UK-UA)
It is embedded as a web component not an iFrame. It utilizes the shadow dom to hold the necessary HTML, meaning it can co-exist with the rest of your site but not be affected by your CSS styling. To ensure the best experience across mobile and desktop, it will work best if your site is already designed to be responsive. On desktop, Mappedin Web can have the rest of your site surrounding it, though we recommend you let the map take up as much space as possible (up to nearly a full screen map experience if you want). On mobile, Mappedin Web will fill the screen and provide its own toolbar on the bottom for a scroll-free, app centric experience.
There are some specific details for integration that should be taken into account:
- Wrap Mappedin Web in its own container. This container should be styled to take up the whole screen on mobile (<1024) and fit into your responsive layout on desktop views.
- On desktop, the minimum width of the container should be 1024px
- On mobile, do not include any more page content than the header and the map; things like footers and other content should be excluded or hidden. Include a header on mobile which allows users to access the - rest of your site, and pass in its height via
- If the host site utilizes hash navigation, Mappedin Web must live on a static page to not interfere.
These are not required, but to get the best possible experience there are a few extra steps that can be taken:
- Allow the map to take up as much space as possible on mobile and desktop
- On mobile, avoid adding too many elements that will decrease the vertical space available for Mappedin Web (this is especially noticeable on smaller devices like the iPhone SE
- Use a one column layout
- If your Location data is being synced in to our system, you can specify
<key>to use your own Ids in the URL and for deep linking Tabs to show categories and info already in Mappedin Web are redundant
- Avoid including unnecessary functionality on the map page that could impact load times of Mappedin Web
You can view how an integration should look via the demo page provided for your venue(s). We recommend the integration follow the demo experience.
Mappedin Web offers a way to link directly to many pages. The following represents all of the deep linking routes that are possible, with a description of what it will do and any parameters you will need. You can see these in action by simply using the map and watching the url. You can then copy and use those urls directly, or use the list below to make your own.
locationId: (LocationId) Location to display
List all available categories
categoryName: (CategoryName) Category to display Lists all locations assigned to the category provided
fromId: Preset departure point Directions page with a preset from field
toId: (LocationId) Preset arrival point Directions page with a preset to field
fromId: (LocationId) Preset departure point
toId: (LocationId) Preset arrival point
false, can set this param to true to enable directions that will prioritize elevators and ramps
false, can set this param to true to show text directions alongside the wayfinding path upon initial load
This can often be caused by a parent
<div> not having a height. The map fills the height available to it, so please make sure that any wrapper or parent divs have an adequate height set.
Unfortunately not as some of the functionality requires scrolling to work. We highly recommend having the map on a page with as little else as possible. This ensure a better user experience especially on mobile devices where the map should have as much screen real estate as possible.
The following domains should be whitelisted in your Content Security Policy for the Mappedin Web v2 to function: