Install Zipy

If you have integrated the Zipy SDK following the steps mentioned here, and you still do not see any sessions recorded in the Zipy dashboard, then this section is for you.

• After integration, please ensure you run your application or load or hard reload the page where you have installed Zipy. Also perform some interactions with the page like clicks or scrolls to activate zipy recording.

  Note: by default Zipy will not record a session without any user activity. If you want to change this, please contact support.

• If you still don’t see a recorded session please confirm the API Key that you have used to initialize Zipy SDK. You can check this in the Project Settings Section of the app.

• Browser extensions like Ad-blockers or script blocking plugins if installed can also block Zipy from being downloaded and hence from recording and sending the data to our backend. Please ensure that those are disabled.

• Some browsers like Brave have built-in Ad blockers which again will block Zipy script from getting downloaded. A workaround to that will be to use our npm instead of script. But then, the subsequent backend calls to record the data can still be blocked without a way to bypass.

• Zipy uses ‘zipy.ai’ domain to download the SDK and also to communicate with its backend. If you are behind a firewall OR using VPN where access to all the third party domains are restricted, you will need to whitelist zipy.ai so that packets start flowing to and from the zipy backend. You should then start seeing your sessions in the ZIpy dashboard.

  How to check this? If zipy.ai is not whitelisted or there are restrictions accessing domains like zipy.ai in your organisation, then you will see one of the following Console errors while zipy is trying to access its backend servers.

  • DNS resolution errors like "ERR_NAME_NOT_RESOLVED" or "ERR_CONNECTION_TIMEDOUT" or "ERR_CONNECTION_RESET"

  • HTTP errors like "403-FORBIDDEN" or "502 BadGateway"

Another reason why sessions might not be getting recorded is if you have configured Content Security Policy (CSP) HTTP header in your application to deny downloading scripts from unlisted domains or prevent these scripts from making XHR/fetch requests.

• Network calls would show blocked:csp on the Zipy's network request and at the same time, in the browser console you would see the CSP violation error clearly indicating that the CSP header has denied loading the script or executing certain calls.

• Network calls would result in net::ERR_BLOCKED_BY_CSP error

If sessions are still not recording, please feel free to ping on the chat or reach out to [e-mail] for further assistance. Provide them with details about your installation and any error messages you may have encountered.

Note: Sometimes, in rare cases, a session might take around 5-10 minutes to start showing up in your dashboard. So appreciate your patience.