For example, those URLs:
www.my-sample-store.com/product/mango-123
www.my-sample-store.com/product/lemon-456
www.my-sample-store.com/product/organe-798
It can be treated as a single “Product Page”
www.my-sample-store.com/product/**
Pages can be used as a filter in session search. In the future, we will allow the use of Pages in Click maps.
Today, we’re excited to announce a powerful new feature for LiveSession: the ability to use Webhooks as a delivery channel for Alerts.
Webhooks are a powerful tool for developers, allowing them to receive real-time notifications when events occur in their applications. This makes them an ideal delivery channel for LiveSession's Alerts, which notify users when key events occur in their applications.
Learn more about how to start using Webhooks on our developers' site: https://developers.livesession.io/webhooks/introduction/
If you have any questions about setting up Webhooks, our support team is always here to help.
Starting today, LiveSession lets you watch your live users with almost no-delay streaming. Clicking on the "Go live" button, allow you to turn on the live preview:
To give you more information, we display if the user is active or the user's mouse isn’t moving (inactive), or the user is in another tab (unfocused):
This functionality and our customer support software integrations like Intercom, LiveChat, or Zendesk can make your support process easier.
Live preview is currently in the Beta phase, so feel free to let us know what you think about it!
LiveSession allows you to create business-friendly names for the most crucial events in your application. This makes data more understandable for you and your team. For example, if there is an event that defines a click on an element with text “Sing up”, you can define it as a “Sign up” event.
Defined Events can be created under the Settings tab. Once created, Defined Devents can be used like any other filter:
We made security improvements to protect your LiveSession code from being added to unauthorized sites by creating a list of trusted domains.
Using trusted domains, you can create a list of domains that you know and trust. Only those domains will be allowed to start recording. It won't work if someone tries to add your script to any website outside your trusted list.
You can set up your trusted domain in Settings -> Websites -> (chose website) -> Settings -> Trusted Domains.
By default, the list is empty, which means every domain is allowed.
The user with the owner role has the most powerful privileges with access to all LiveSession sections. There can be only one owner at a time, so in some cases, you might want to transfer your organization ownership to another person. From now on, you can do it by switching the user role to "Owner".
We're excited to announce that Alerts notifications are now available!
Integrate LiveSession with Slack and get instant notifications about important events made by users. This integration sends notifications from LiveSession Alert to Slack.
Read more about how to start with alerts here.
We hope you find this new feature helpful. As always, let us know if you have any questions or feedback.
We are excited to announce that DevTools: Network Logs are now available! This new feature will help you debug network requests and responses.
Read our help article and start capturing network requests.
We hope you find this new feature helpful! If you have any questions or feedback, please let us know.
It's possible to delete individual sessions from now. To delete session open right-top dropdown in playback view, and click delete. This option is only visible for users with admin and owner role permissions.
Please note that deleting sessions will not refill your session quota.
We’re introducing an easier way to protect sensitive content from being recorded. From now on, you can exclude elements by creating a rule in LiveSession's application.
This feature is available in website settings under the "Recording elements" tab. To create a new rule, click on the "Add rule" button and add a selector of the element you want to anonymize. Please note that the child nodes will be affected too (eg. excluding "body" will anonymize the whole page). Also, changes in the rules are applied to future sessions only.
