Skip to main content

Shared Tables

Analytics data is provided in two shared tables: session_events_view and kiosks_view

Session_events

The session_events_view table contains all user interaction data in its original, unprocessed form. This gives you access to the complete details of every action users take with your wayfinding system.

How the data is organized:

  • Standard information (like timestamps, venue details, and session IDs) appears in its own dedicated column for easy analysis
  • Action-specific details are stored in a special column called DATA. This column contains additional information that varies depending on what the user actually did (such as search terms, selected destinations, or navigation preferences)

All columns contain complete information unless specifically marked as optional. Optional columns may occasionally be empty when that particular piece of information isn't relevant to the specific user action being recorded.

Column nameTypeCommentExample
IDINTEGERThe ID of the row. A kind of sequence number guaranteed to be unique across all events.4033671436
TIMESTAMPTIMESTAMP_LTZ (timestamp with timezone)The datetime at which the event occurred, expressed in the timezone of the current Snowflake session (UTC by default).2025-06-08 10:16:55.629 +0000
TIMESTAMP_WALLTIMESTAMP_NTZ (timestamp without timezone)The time at which the event occurred, expressed in the timezone of the venue where the event occurred (as one would observe on a "wall clock").2025-06-08 06:16:55.629
ACTIONSTRINGThe event action. Use this to determine the event type.search
VENUESTRINGThe slug of the venue where the event occurred.mappedin-stadium
VENUE_NAMESTRINGThe name of the venue as observed at the time the event occurred.Mappedin Stadium
ORGANIZATIONSTRINGThe ID of the organization that owns the venue as observed at the time the event occurred.1a23b456789cde0f1g234h56
ORGANIZATION_NAMESTRINGThe name of the organization that owns the venue as observed at the time the event occurred.Mappedin
SESSION_IDSTRINGMappedin generated ID of the session. Events belonging to the same session have the same session_id.abcqAP3ZSetWnGkvct+Ia8tBw2/GWSP0PGNjIX7HijK=
DEVICE_IDSTRINGMappedin generated ID of the device. May refer to a directory when the source is a directory. Refers to a browser for web sources2a33b456789cde0f1g236m34
CONTEXTSTRINGThe context of the event source. Sometimes referred to as the 'product'.webv2
PLATFORMSTRINGPlatform of the source (Windows, MacOS, Android, iOS, etc)iOS
LANGUAGESTRING (optional)The user's selected languageen
VERSIONSTRINGThe version of the schema found in the DATA column for this ACTION2.3.1
DATAOBJECTA schemaless object that carries extra data specific to the type of event (action){ query: "Footlocker" }

Context Values

The CONTEXT column can contain the following values:

  • "Directory Legacy (6)" - Legacy directory (v6)
  • "Web Legacy" - Legacy web
  • "Web"
  • "Premium Directory"
  • "Directory" - Traditional directory

Kiosks_view

The kiosks_view is a reference table that maps kiosk device IDs to human-readable information. It allows translation of device identifiers (like 65f51072c6) into meaningful kiosk names (like MAPPEDIN-DR01) along with their venue details.

PropertyDescriptionTypeExample
kiosk_idThe device ID of the directory.STRING65f51072c6
kiosk_nameThe name of the directory device.STRINGMAPPEDIN-DR01
venueThe slug of the venue where the directory is located.STRINGmappein_demo_airport
venue_nameThe name of the venue.STRINGMappedin Airport (Demo)
organizationThe ID of the organization that owns the venue.STRING12das1a5ds64651aad