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?
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?
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?
Let's imagine that the users can buy clothes in your app. You can choose to send events related to the process, for instance:
Event properties - example
You can attach several properties to each event. The property provides more details about the event.
Will it be possible to identify specific users?