In store POS/ Kiosk Applications – UXCam

This article describes how UXCam can be used for in-store POS/Kiosks.

1 » Can I use UXCam if I have a POS/Kiosk mode app?

2 » What would count as a session?

3 » When can I stop a session to upload it?

4 » Is it possible to add an ID to each session?

5 » Can I send other session’s related information to UXCam?

6 » Events example

7 » Event Properties example

8 » Will it be possible to identify specific users?

Can I use UXCam if I have a POS/Kiosk mode app?

Sure! It’s possible to use UXCam with your POS app. Please check all the questions to find out more about the details. If you have any other questions, don't hesitate to reach out to us using the chat bubble.

Users of my application use it throughout the whole day. What would count as a session?

UXCam automatically stops and uploads a session when the app goes to the background. We recommend controlling the recording by using our API. Using this API you'll be able to stop a session and upload it at any moment. This will be counted as one session.

When can I stop a session to upload it?

Using the API, you can stop the session at any moment.

Let’s imagine that your application is used in a restaurant and the users can place their orders there. It’s possible to base your choice on the screens they visit or events they complete. In this case, the Purchase completed screen can be considered the last one, and the Home or Menu screen can start another session. Alternatively, the Payment completed event can end the session and the Clicked on the menu event can start another one.

Is it possible to add an ID to each session?

By default, each session has a unique ID. You can also send an ID as an event for each session. It can be, for instance, an Order ID that will help you track the session based on the actual order’s number.

Can I send other session’s related information to UXCam?

Sure, this is possible! You can send events and events' properties to UXCam to gather more insights into your users' behavior. It will help you to create valuable funnels, track each step of your users' journey and analyze their adoption of the new features. You can find more information about sending events here.

Events example

Let's imagine that the users can buy clothes in your app. You can choose to send events related to the process, for instance:

Screenshot_2023-03-01_at_12.45.03.png

Event properties - example

You can attach several properties to each event. The property provides more details about the event.

Screenshot_2023-03-01_at_12.36.39.png

Will it be possible to identify specific users?

When it comes to POS apps, as all the users use the same device, we’ll assign the same ID to all of them. However, if you want to differentiate users based on, for instance, their loyalty card number, you can send this information to UXCam as event and event property, for example:

Event: loyalty_card_number_entered
Event property: 1234EXAMPLE (different for each loyalty card)

This way you’ll be able to find sessions for specific users.