Actions
This article details the type of event data that customers can see in the session_events_view table.
change-language
Records when users switch the display language on your wayfinding system. To see which language they selected, look at the LANGUAGE property in this event's data. Available for wall-mounted directories only.
When this occurs: A user clicks or taps the language selection option to change from one language to another (for example, switching from English to Spanish).
What this means: You can identify language preferences among your visitors, track the effectiveness of multilingual support, and understand the diversity of your user base. This helps optimize language options and demonstrates the value of accessibility features.
Properties
| Property | Description | Type | Example |
|---|---|---|---|
| fromLanguage | The language that was set before it was changed. | STRING | fr |
| userPosition | An object containing geolocation information | OBJECT (optional) | { "accuracy": 0, "bluedotTimestamp": 1749981867589, "latitude": 50.405827664043784, "longitude": 30.611356094604353 } |
| userPosition.accuracy | The accuracy of the position in meters. | INTEGER | |
| userPosition.bluedotTimestamp | The timestamp the measurement was made in UNIX time. | INTEGER | |
| userPosition.latitude | The latitude of the position. | NUMBER | |
| userPosition.longitude | The longitude of the position. | NUMBER |
change-state
Records when users navigate between different screens or sections within your wayfinding system.
When this occurs: This event is triggered when a user moves from one view to another, such as switching from the main map to search results, moving from search to directions, or navigating between different interface screens.
What this means: You can analyze how users navigate through your wayfinding system, identifying the most popular features and views, understanding user journey flows, and spotting potential areas where users might get stuck or lose interest. This helps optimize the user experience and interface design.
Properties
| Property | Description | Type | Example |
|---|---|---|---|
| state | There is a list of states on web and directories that the user can land on. | STRING | home |
| from | STRING (optional) | IDLE | |
| to | STRING (optional) | START | |
| type | STRING | next-gen |
found-floor
Records when your wayfinding system successfully identifies which floor a user is currently on. This event captures location updates that include floor-level information, giving you more detailed insights into how people move through multi-story venues.
Unlike basic location tracking, this event specifically captures when the system knows the user's exact floor level, not just their general building location.
When this occurs: The system receives this information when a user's device (typically an iPhone or iPad with indoor positioning enabled) provides precise location data that includes floor elevation. This allows the wayfinding system to pinpoint not only where someone is, but which floor they're on within your venue
What this means: Users with advanced positioning capabilities are providing you with the most detailed movement data possible. This high-precision tracking allows you to analyze floor-by-floor traffic patterns, optimize tenant placement in multi-story venues, and provide the most accurate navigation experience.
Properties
| Property | Description | Type | Example |
|---|---|---|---|
| userPosition | An object containing geolocation information | OBJECT | { "accuracy": 0, "bluedotTimestamp": 1749981867589, "floorLevel": 2, "latitude": 50.405827664043784, "longitude": 30.611356094604353 } |
| userPosition.accuracy | The accuracy of the position in meters. | INTEGER | |
| userPosition.bluedotTimestamp | The timestamp the measurement was made in UNIX time. | INTEGER | |
| userPosition.floorLevel | The floor of the venue where the position was read. | INTEGER | |
| userPosition.latitude | The latitude of the position. | NUMBER | |
| userPosition.longitude | The longitude of the position. | NUMBER |
found-position
Records when your wayfinding system tracks a user's location without specific floor details.
When this occurs: This happens when a user's device provides location data that shows where they are within your venue, but doesn't include the elevation information needed to identify their exact floor level. Common scenarios include:
- Devices without indoor positioning capabilities
- Users located outdoors where the system relies on standard GPS
What this means: Users are successfully being tracked within your venue, allowing you to analyze general traffic patterns, popular areas, and dwell times, even when precise floor-level data isn't available.
Properties
| Property | Description | Type | Example |
|---|---|---|---|
| userPosition | An object containing geolocation information | OBJECT | { "accuracy": 0, "bluedotTimestamp": 1749981867589, "latitude": 50.405827664043784, "longitude": 30.611356094604353 } |
| userPosition.accuracy | The accuracy of the position in meters. | INTEGER | |
| userPosition.bluedotTimestamp | The timestamp the measurement was made in UNIX time. | INTEGER | |
| userPosition.latitude | The latitude of the position. | NUMBER | |
| userPosition.longitude | The longitude of the position. | NUMBER |
query-directions
Records when your wayfinding system creates directions for a user's requested route.
When this occurs: This event is triggered when the system successfully calculates a route between two points (such as from a user's current location to their desired destination).
This event captures when directions are created by the system, but doesn't necessarily mean the user has seen the directions on their screen yet. The directions may need an additional moment to appear visually on the map, though this typically happens almost immediately afterward.
What this tells you: Users are successfully requesting and receiving navigation assistance, indicating active engagement with your wayfinding system's core functionality.
Properties
| Property | Description | Type | Example |
|---|---|---|---|
| accessible | Whether the requested directions should be wheelchair accessible | BOOLEAN | false |
| start | The ID of the navigation start target. Can be a space or location or node or coordinate. | STRING | n_578ab05 |
| end | The ID of the navigation end target. Can be a space or location or node or coordinate. | STRING | n_223cd3f |
| userPosition | An object containing geolocation information | OBJECT (optional) | { "accuracy": 0, "bluedotTimestamp": 1749981867589, "latitude": 50.405827664043784, "longitude": 30.611356094604353 } |
| userPosition.accuracy | The accuracy of the position in meters. | INTEGER | |
| userPosition.bluedotTimestamp | The timestamp the measurement was made in UNIX time. | INTEGER | |
| userPosition.latitude | The latitude of the position. | NUMBER | |
| userPosition.longitude | The longitude of the position. | NUMBER |
query-suggest
Records when your wayfinding system provides auto-complete suggestions as users type in the search box.
What are auto-complete suggestions? These are the dropdown suggestions that appear while someone is typing - for example, if a user types "Star" they might see suggestions like "Starbucks" or "StarTech Store" appear below the search field.
How this differs from search results: These suggestions are quick text matches to help users complete their search faster, rather than full location details with maps and directions that appear after someone completes their search.
When this occurs: Each time the system generates a list of suggested completions based on what the user has typed so far.
What this tells you: Users are actively engaging with your search functionality, and you can see popular search patterns and terms even before people complete their full searches.
Properties
| Property | Description | Type | Example |
|---|---|---|---|
| query | The input string to generate a suggestion from | string | ne |
| suggestions | A list of suggestion strings to complete the query | string[] | ["nespresso", "new", "necklace"] |
| userPosition | An object containing geolocation information | OBJECT (optional) | { "accuracy": 0, "bluedotTimestamp": 1749981867589, "latitude": 50.405827664043784, "longitude": 30.611356094604353 } |
| userPosition.accuracy | The accuracy of the position in meters. | INTEGER | |
| userPosition.bluedotTimestamp | The timestamp the measurement was made in UNIX time. | INTEGER | |
| userPosition.latitude | The latitude of the position. | NUMBER | |
| userPosition.longitude | The longitude of the position. | NUMBER |
search
Records when your wayfinding system displays search results to a user.
When this occurs: This event is triggered when someone finishes typing their search term and the system shows them a list of matching locations or points of interest. The system waits until the user has stopped typing (rather than generating results for every keystroke) to ensure they see relevant, complete results.
Example: A user types "coffee shop" in the search bar, pauses, and then sees a list of all coffee shops in your venue - this is when the search event is recorded.
What this tells you: Users are completing searches and receiving results, giving you insights into what people are looking for in your venue and whether your search functionality is meeting their needs.
Properties
| Property | Description | Type | Example |
|---|---|---|---|
| query | The input string to generate search results from | STRING | vans |
| userPosition | An object containing geolocation information | OBJECT (optional) | { "accuracy": 0, "bluedotTimestamp": 1749981867589, "latitude": 50.405827664043784, "longitude": 30.611356094604353 } |
| userPosition.accuracy | The accuracy of the position in meters. | INTEGER | |
| userPosition.bluedotTimestamp | The timestamp the measurement was made in UNIX time. | INTEGER | |
| userPosition.latitude | The latitude of the position. | NUMBER | |
| userPosition.longitude | The longitude of the position. | NUMBER |
select-category
Records when users choose a category to browse locations by type.
When this occurs: This event is triggered when a user clicks or taps on a category option to see all locations of that type. For example, selecting "Restaurants," "Retail Stores," or "Services" to view all venues in that category.
What this tells you: Which types of businesses or services users are most interested in finding, helping you understand popular categories and visitor preferences in your venue.
Properties
| Property | Description | Type | Example |
|---|---|---|---|
| categoryId | The ID of the category that was selected. | STRING | 67f5c8 |
| categoryName | The name of the category that was selected. | STRING | Food & Drinks |
| userPosition | An object containing geolocation information | OBJECT (optional) | { "accuracy": 0, "bluedotTimestamp": 1749981867589, "latitude": 50.405827664043784, "longitude": 30.611356094604353 } |
| userPosition.accuracy | The accuracy of the position in meters. | INTEGER | |
| userPosition.bluedotTimestamp | The timestamp the measurement was made in UNIX time. | INTEGER | |
| userPosition.latitude | The latitude of the position. | NUMBER | |
| userPosition.longitude | The longitude of the position. | NUMBER |
select-event
Records when users click on promotional content, advertisements, or special offers displayed in your wayfinding system.
When this occurs: This event is triggered when a user taps or clicks on promotional content such as:
- Special sales or promotional banners
- Event announcements
- Advertisement displays
- Featured offers in the events section
What this tells you: How effectively your promotional content is engaging visitors, which offers or events generate the most interest, and how well your advertising placements are performing.
Properties
| Property | Description | Type | Example |
|---|---|---|---|
| id | The event ID. | STRING | a1b2c3 |
| name | The event name. | STRING | Ad Banner |
| locationId | The location ID associated to the event. | STRING | 5b628bacc |
| locationName | The location name associated to the event. | STRING | Hi Bakery |
| type | The event type. | STRING | advertisement |
select-location
Records when users choose a specific location or point of interest from your wayfinding system.
When this occurs: This event is triggered when a user clicks or taps on a specific location, such as:
- Clicking on a store or restaurant from search results
- Tapping on a point of interest directly on the map
- Selecting a location from a category list
What this tells you: Which specific businesses, services, or areas in your venue are attracting the most user interest and engagement, helping you understand popular destinations and visitor behavior patterns.
Properties
| Property | Description | Type | Example |
|---|---|---|---|
| locationId | The ID of the selected location. | string | 674f060ffa |
| locationName | The name of the selected location | string | Apple |
| userPosition | An object containing geolocation information | OBJECT (optional) | { "accuracy": 0, "bluedotTimestamp": 1749981867589, "latitude": 50.405827664043784, "longitude": 30.611356094604353 } |
| userPosition.accuracy | The accuracy of the position in meters. | INTEGER | |
| userPosition.bluedotTimestamp | The timestamp the measurement was made in UNIX time. | INTEGER | |
| userPosition.latitude | The latitude of the position. | NUMBER | |
| userPosition.longitude | The longitude of the position. | NUMBER |
show-qrcode
Records when a QR code appears on the screen for users to scan.
When this occurs: This event is triggered whenever the system displays a QR code, typically to help users transfer information from a wall-mounted directory to their mobile device (such as directions, maps, or location details).
What this tells you: How often users are being presented with the option to continue their navigation experience on their personal mobile devices, indicating potential cross-device usage patterns.
Properties
| Property | Description | Type | Example |
|---|---|---|---|
| from | From location ID or kiosk node ID for generating directions on web redirect. | STRING | 65f51072c6 |
| to | To location ID(s) for generating directions on web redirect. | ARRAY<STRING> | [ "6140c85d" ] |
| locationId | The location ID tied to the QR code displayed. | STRING | 6140c85 |
| state | The UI state that the QR code was displayed at. Refers to the same state as that found in the change-state event. | STRING | location |