With UXCam, you can go beyond typical engagement and usage metrics to find usage patterns and trends, discover pain points and roadblocks in the user journey, and take a closer look at the interaction with all elements of your application.

Let’s see what you can do:

With Event analytics and custom events, you can see how many times a certain action has been completed in the last week and view how this changes over time. E.g. If you have a fitness app you can track the action ‘workout completed’, if you have a music app you can measure ‘played song’ or if you have an e-commerce app you can track ‘purchase completed’.

Feature: Event analytics | Implementation needed: Custom events

By grouping your actions or custom events by user properties such as gender, subscription type, profession, etc. you can identify different user patterns.

E.g. if you have a cinema app you can group your event purchase completed by avg. quantity of tickets and age group. In the example below, we can see that users between 20-29 and 30-39 usually buy 3 tickets on average, so there is an opportunity for group promotions and sales of snack packs.
​

Feature: Event analytics | Implementation needed: Custom events and custom user properties

Use custom event properties to drill down into event details and form better hypotheses.

E.g. users using iOS devices almost never select Credit card payment, we could consider adding an alternative to pay with Apple pay to better suit their needs.

Feature: Event analytics | Implementation needed: Custom events with properties and custom user properties.

Measure user interaction with specific elements of your app and/or test the call to action performance.

E.g. send the event for the button ‘add payment’ to filter those sessions and see how users interact with it.

Feature: Session list | Implementation needed: Custom events (optional, can also be done with screens)

Find users or sessions that didn’t complete a certain action in your app to watch the recordings and analyze their behavior or reasons to drop out from a certain process.
​

E.g. identify sessions where users didn’t add a payment method and see whether they faced some issues with the payment details.

Feature: Session list | Implementation needed: Custom events (optional, can be done with screens)

See the adoption rate for your new features and discover how your users use them in a real context. Watch the sessions to identify opportunities to educate late adopters.

E.g. if you added a new feature to receive alerts or notifications when a product is back in stock in your e-commerce app, you can send it as an event and see how many users are using that feature, next replay the videos to see how they interact with it, how easily they find it, etc.

Feature: Session analytics and session list | Implementation needed: Custom events

How are the changes you made impacting the usage of your app or your users' experience? Was it the right decision? Are your users confused? You can answer all these questions by measuring new features and changes with custom events and monitoring interaction by watching sessions.

E.g. if you changed the option to add a product to favorites and are sending the event add_favorite you can check the usage trends and group it by app version to see whether the changes impacted the feature usage.

Feature: Event analytics and session list | Implementation needed: Custom events.

Discover which features or content drive more engagement and retention. See what kind of features or content your users prefer by sending them as events, view if there’s any trending or difference between different devices, OS systems, or user segments then optimize your content or invest more in those types of features.

Feature: Event analytics | Implementation needed: Custom events.

Don’t limit yourself to one environment - integrate UXCam with your Beta version.

When you launch a beta version you can integrate it with UXCam with a different app key in order to keep your data separate. This can help you get more visibility into feedback or bugs reported by beta testers, and identify issues that they may not even have noticed.