Screenshots are corrupted or not accurate
- Why are my screenshots blank or not accurate?
My users can't submit screenshots in the widgets
- Content Security Policy (CSP)
- Why can't your users submit a screenshot when your DOM (HTML) is too huge?
The widget or feedback button is not showing
Emails or notifications are not arriving
Performance and maxima
Does Usersnap support this ...
Integration connection issues
Please, check your spam folder.
Every email that comes from the Usersnap applications should come from our email server:
That includes new screens, email integration, invitation, notifications, etc. If you whitelist that hostname, the emails shall go through smoothly.
This could have been caused by the console recorder. Please kindly check if your console recorder feature is activated. If so, please deactivate it and things should be working normally again.
In this case please check if the project was set live or if it's been paused. It can be seen from the projects' overview or inside a specific project.
If the project is "set live" but the button/widget still does not appear, please kindly double-check on its display rules and see if they were configured accordingly.
The Usersnap widgets are loaded asynchronously (like Google Analytics). It DOES NOT impact your page loading and rendering times. Additionally, we are using a strong CDN to ensure the best user experience.
With every screenshot, our widget is currently also submitting a snapshot of your DOM (document object model) of your HTML page. Sometimes, this DOM can be huge especially if you have a Single-Page-Application (SPA) or your company is using a framework like VUE.js, etc.
Due to protect Usersnap against any attacks we limit the so-called payload (size of the DOM) to 20 MB (mega-bytes). If your DOM is bigger than that, you will not be able to submit the screenshot.
We are working on an alternative to make that work for you, but currently, this is a hard limit.
The connection of the integration from Usersnap to Azure DevOps does not work
This can happen when using ActiveDirectory in conjunction with Azure DevOps if the connecting account is only a guest account in the ActiveDirectory.
In this case, you should use a dedicated account that is a "real member" in the ActiveDirectory to connect to Azure DevOps. That should solve your issue.
Updated 17 days ago