Skip to main content

Frequently Asked Questions

Sessions​

Counting Sessions​

Does a session include Mappedin Web or Mappedin MiniMap?​

Yes

  • Total sessions = Mappedin MiniMap + Mappedin SDKs + Mappedin Web.
  • Mappedin Directory sessions are calculated separately under directory metrics.

What doesn't a session include?​

  • Heartbeat pings notify-heartbeat do not constitute sessions.

Does Session by Product focus only on Mappedin Web and Directory?​

Sessions by Product is broken down into Directory, SDK, and Web. SDK is included as a separate product category.

Start and End of a Session​

How is the start and end of a session determined?​

Mappedin Web Start

The load-app event fires when the user opens the Mappedin Web and the application loads and marks session start.

Mappedin Directory Start

A new Mappedin Directory session starts right after the previous one ends after the Are you still there? timer runs out.

Directory sessions could be undercounted during busy times when another user starts using the directory before the previous session ends.

Mappedin Web End

The end-session event fires when the session ends. For Mappedin Web, this is less defined than Directory because there's no explicit "Are you still there?" prompt. The session effectively ends when the browser tab is closed or the end-session event fires.

Mappedin Directory End

The end-session event fires when the session ends. For Mappedin Directory, this is defined by the Are you still there? timer. The session ends when the timer runs out.

A new session starts right after the previous one ends. If no one is using it, this can skew the average session time. The Mappedin Analytics dashboard takes the timestamp from the first change-state event to end-session to get the average time, removing the idle time.

Average Use Time​

Is this per session?​

Yes

Average Use Time is calculated per session.

Does it exclude idle/background time? What counts as "active"?​

No

It includes idle time. The Mappedin Analytics dashboard filters out any Directory session longer than 10 minutes.

Sessions By Platform​

What platforms are recorded as "Other"?​

This is a catch-all for user agents that don't cleanly map to iOS, Android, Windows, Mac, or Kiosk. This includes Linux, ChromeOS, or other uncommon platforms.

What is "On Premises"?​

These originate from users using fixed wayfinding stations or kiosks throughout a venue. These are Windows-based kiosk hardware running Mappedin Directory. The PLATFORM field in analytics shows Windows for these.

What platforms are recorded as "unknown"?​

A platform is recorded as unknown when it cannot be detected.

Total Ad Impressions​

Is this across all ad types (banner, full-screen, happening now)?​

Yes

Total Impressions are the complete count of all ad views across digital wayfinding platforms. They are broken down by content type: Banner ads, Full-screen overlay ads, deals, and Happening Now features.

Origin Sources​

What qualifies as a "Direct" source?​

Visitors who accessed the map directly through a venue's website or branded app are considered "Direct" sources. This is determined by the originContext field in the load-app event. When a user navigates directly to a Mappedin Web URL embedded on a website the LAUNCHED_FROM field is direct.

What is a Mappedin Experience source?​

Visitors who launched wayfinding through Mappedin touchpoints such as scanning a QR Code shown on a Mappedin Directory, chatbot links, or other Mappedin experiences.

The originContext enum values include: web, webv2, gen7, bespoke and external. The LAUNCHED_FROM field in SESSIONS_VIEW tracks: qr-code, kiosk, app-link, etc.