Skip to main content

Mapsted

Mapsted Integration Guide

Overview

This guide explains how to connect Bridged with Mapsted to read event content including venue layouts, location data, points of interest (POI), and real-time positioning information. The integration supports reading this data for activation, qualification, and nurture playbooks where location context and venue navigation are needed.

Mapsted specializes in location intelligence and hardware-free indoor positioning technology . It provides real-time indoor navigation that updates for room adjustments or session capacity, helping managers reduce congestion. The platform offers SDKs for mobile (Android/iOS), web, and kiosk applications .

Primary Use Case: Read Event Content

For Bridged's event experience integrations, the primary use case is reading event-related location data, including:

Data Type

Use in Bridged

Venue maps / floor plans

Answer attendee questions about building layout and room locations

Points of Interest (POI)

Provide information about session rooms, exhibitor booths, restrooms, etc.

Real-time positioning

Track attendee location for context-aware conversations

Alert/notification zones

Trigger location-based messages when attendees enter specific areas

⚠️ Integration Limitations

Mapsted is primarily a mobile SDK provider for embedding indoor navigation into native apps, not a data warehouse with a public REST API . Key limitations:

Limitation

Impact

No public REST API

Mapsted does not offer a documented REST API for programmatic data extraction

SDK-only access

Data is accessed via mobile SDKs (Android/iOS) or web SDK, not via HTTP APIs

Requires mobile app

To use Mapsted features, you must embed their SDK into a mobile application

Connection Methods

Given the limitations, here are the available options:

Method

Best for

Setup complexity

Manual Export (via Mapsted Hub Dashboard)

Batch data pulls for venue maps and POIs

Low

Mobile SDK Integration

Real-time positioning within a mobile app

High

Web SDK Integration

Real-time positioning within a web app

Medium

Recommendation: For event data extraction, use manual export from Mapsted Hub Dashboard. For real-time location triggers, consider embedding Mapsted SDK into a mobile app that also integrates with Bridged.

Step 1: Export Venue and POI Data from Mapsted Hub

Mapsted provides a Hub Dashboard for managing properties, maps, and alerts .

  1. Log in to your Mapsted Hub Dashboard

  2. Navigate to the property (venue) you want to export data from

  3. Locate the Points of Interest (POI) or Venue Map section

  4. Export POI data as CSV/JSON (if export feature is available)

Data that can typically be exported includes:

  • Venue/building name and structure

  • Floor levels and room names

  • Point of Interest categories (sessions, exhibitors, restrooms, entrances)

  • Alert zones and geofenced areas

Step 2: Configure Alerts for Location-Based Triggers (Optional)

Mapsted supports location-based alerts that trigger when a user enters or exits specific zones .

Using Mapsted Alerts with Bridged

If you have a mobile app with Mapsted SDK integrated:

  1. In Mapsted Hub Dashboard, set up Scheduled Alerts for specific zones

  2. When a user enters a zone, Mapsted SDK triggers the alert

  3. Your mobile app can capture this event and send it to Bridged via API

Mapsted Alert API methods :

  • addScheduledAlertTriggerListener() - Register callback for alert triggers

  • addAlertsOnChangeListener() - Register listener for property alerts

Example flow:

  1. Attendee enters session room (detected by Mapsted positioning)

  2. Mapsted SDK triggers ScheduledAlertTriggerListener

  3. Your mobile app sends event to Bridged webhook

  4. Bridged agent provides session-specific information

Step 3: Manual Data Import to Bridged (Primary Method)

For automated or recurring data pulls:

  1. Export venue and POI data from Mapsted Hub Dashboard

  2. Convert data to CSV format (if not already)

  3. Upload CSV to Bridged via dashboard or API

  4. Configure mapping between CSV columns and Bridged profile/event attributes

Bulk sync limit: Each bulk operation is limited to 50 records per request.

Step 4: Alternative - Custom Web Integration

Mapsted offers a Web SDK that is compatible with Chrome, Firefox, Safari, and Opera .

If you have a web-based event portal:

  1. Embed Mapsted Web SDK into your event website

  2. Capture location events via Mapsted's map interaction listeners :

javascript

// Example: Capture map click events (conceptual)
mapApi.mapView().addMapClickListener((event) => {
    const clickedEntity = event.getClickEntity();
    // Send entity data to Bridged via API
});

  1. Send captured data to Bridged via webhook

Available map event types :

  • MAP_IDLE - Map rendering complete

  • MAP_MOVED - Map gesture in progress

  • MAP_STABLE - All animations complete

Common Use Cases

Playbook

How Location Data Is Used

Activation

Send venue maps and session room locations to attendees before the event

Qualification Agent

Track which sessions/exhibitor booths attendees visit for lead scoring

Nurture & Conversion

Provide real-time wayfinding assistance during the event

Example Conversations Powered by Mapsted Data

Venue navigation:

  • Attendee: "Where is the keynote session?"

  • Bridged: Reads room location data → Provides turn-by-turn directions

Exhibitor location:

  • Attendee: "How do I get to Booth 1234?"

  • Bridged: Reads POI data → Provides walking route

Context-aware assistance:

  • Attendee enters session room (detected via Mapsted)

  • Bridged proactively: "Welcome to the AI Keynote. Here is the session agenda."

Security & Permissions

  • Mapsted SDK requires API keys for authentication

  • Mapsted is hardware-free; no beacons or Wi-Fi access points needed

  • All location data is processed on-device

  • Credentials should be stored securely in your mobile/web app

Troubleshooting

Issue

Likely cause

Solution

Cannot extract data via API

Mapsted has no public REST API

Use manual export or SDK integration

Alerts not triggering

Incorrect alert setup in Hub

Verify scheduled alert configuration

Map events not captured

Listener not registered

Use addMapEventListener() or addMapClickListener()

Web SDK compatibility issues

Browser not supported

Use Chrome, Firefox, Safari, or Opera

Support

For integration support, contact your Bridged account manager or email support@bridged.media.

For Mapsted-specific questions: