1. Browsers supported

iAdvize is a SaaS application based primarily on modern web technologies and therefore it requires a powerful web browser. 

Generally, iAdvize is best with the two last versions of Google Chrome, Mozilla Firefox, Edge and Safari to the extent that such versions have been tested and approved by our technical team.

iAdvize may work on older versions (details below) but they are not officially supported anymore. That is why we do not undertake to make systematically fixes on these older versions.

Also, we advise you to update your browser regularly.

 

Note : If you do not know your browser’s version or how to update it, take a look at this page : https://updatemybrowser.org/ 

1.1 Visitor side (Livechat)

Recommended browsers:

• Edge, the last two versions
• Firefox, the last two versions
• Chrome, the last two versions
• Safari, the last version 

Supported browsers: 

• Edge 92+
• Firefox 78+
• Chrome 92+
• Safari 14.1+
• Opera 80+

Supported browsers on mobile depend on the OS version. Here the supported OS: 

• iOS 14+
• Android 8+

1.2 Back office side (Conversation panel, iAdvize Administration,...)

Recommended browsers :

• Edge, the last two versions
• Firefox, the last two versions
• Chrome, the last two versions
• Safari, last version

Supported browsers : 

• Edge 92+
• Firefox 78+
• Chrome 92+
• Safari 14.1+
• Opera 80+

1.3 Browsers required configurations

• Javascript must be enabled
• Cookies must be accepted
• LocalStorage must be enabled
• Websockets must be accepted. The conversation panel uses them, with no fallback, to exchange messages in real time, reconnect after a connection drop and show agents' presence: if your network blocks them, the conversation panel cannot connect.

Note : If this configuration is not respected, we cannot guarantee that iAdvize will work properly.

2. Screen resolution requirement

The iAdvize conversation panel has a lot of information. In order to have a clear vision on important information at any time, and a better access to important actions and interactions as well, we recommend you a high screen resolution.
 

Note : The following recommendations of screen sizes correspond to the dimensions of the viewport of your browser used to display the iAdvize user interface and NOT the resolution of your actual screen. Keep in mind that you might be able to use the full width of your screen if your browser is set in full screen mode, however the browser itself most certainly uses some vertical space that won’t be available for the Desk user interface. Moreover, if the User interface is used in an iframe (for example when integrated in other software like Salesforce) our recommendations concern the dimensions of that iFrame.

Optimal viewport resolution:

• Width >= 1920px
• Height >= 930px

Recommended viewport resolution :

• Width >= 1440px
• Height >= 750px

Minimal viewport resolution :

• Width = 1280px
• Height = 650px

Note : The mirroring functionality is based on the actual size of the visitor's screen, but is not a 100% reliable reproduction of the visitor's experience.
For mobile devices, some visitor preferences are not taken into account, such as dark mode and we strongly recommend a responsive site: if a visitor manually zooms in or out of a non-responsive web page from a smartphone, the agent side display will not be reproduced.

3. Network and domains requirement

We require broadened access to provide for our future developments in terms of protocols and network infrastructure, and to avoid you having to systematically change your configuration at each change on our side.
 

3.1 Domains, protocols and ports required to run iAdvize

Note :
- We are using dynamic IP ranges. Please refer to domain name exclusively if you need to apply filtering.
- If these ports or protocols are not open on your network, we cannot guarantee that iAdvize will work properly.
- You can test the compatibility of your network configuration with the iAdvize solution from this page: https://networktest.iadvize.com/
- You can also test the compatibility of your network configuration with the Twilio solution from this page: https://networktest.twilio.com/

3.2 Optional domains, protocols and ports for running iAdvize

Note :
- We are using dynamic IP ranges. Please refer to domain name exclusively if you need to apply filtering.
- You can test the compatibility of your network configuration with the iAdvize solution from this page: https://networktest.iadvize.com/

3.3 Specific configuration for automatic rich link generation from the conversation panel

• If you want to use the rich link generation feature on the conversation panel you need to bypass these ip's on your website to authorize our robots to browse the metadata on your pages : 35.158.241.155, 35.158.90.142, 35.156.32.28 

Note : If access from these IPs is blocked, rich link generation from the conversation panel may be degraded, or even not functional.

4. iAdvize implementation requirements on your website

iAdvize provides a set of Javascript tags to implement on your site to install the solution.
We invite you not to modify the structure of these tags to avoid any loading errors.
Once the iAdvize Javascript tags are implemented, a set of HTML/CSS/Javascript resources is loaded to display the contact elements on your site. As for the Javascript tags, we invite you not to change the nature of these resources.

We also recommend that you do not use the structure of the HTML/CSS IDs or CLASSes of the iAdvize contact elements for any specific development on your site. Indeed, our HTML/CSS structure is not fixed in time and can change at any time.

4.1 Compatibility with third-party Javascript libraries

Despite all the iAdvize's efforts to minimise this type of conflict, certain old third-party libraries potentially used on your site can prevent iAdvize to work well. 
These libraries override the definition of certain javascript native methods (e.g. Array.prototype.toJSON) used by iAdvize solution.

If your website uses prototype.js below version 1.7 and was created in iAdvize after 17 July 2019, the iAdvize tag does not load: no notification or chatbox is displayed. Otherwise, these libraries can cause random Javascript errors: notifications not displayed, messages disappearing from the chatbox, a blank page instead of the visitor's page, mirroring and co-browsing not working.

These libraries have been identified as not compatible with iAdvize :
- prototype.js : all versions less than 1.7 (http://prototypejs.org/)
- xdomain.js : all versions (https://github.com/jpillora/xdomain)

Note: If you use this kind of old Javascript libraries, we cannot guarantee that iAdvize will work properly. That is why we do not undertake to make systematically fixes on these libraries.

4.2 iFrames

iframes are used to display certain contents (notifications, chatbox,...).
Therefore, it is necessary not to block iframes and their content (HTML, CSS, JS).

If your internal policy is to hide iframes and their content, you can make an exception for iAdvize iframes by using this CSS:

iframe[name*='iAdvize'],iframe[title*='iAdvize']{display:block;}

4.3 CSP configuration

Content Security Policy (CSP) is a security mechanism that helps protect against content injection attacks, such as Cross Site Scripting (XSS). 

If you want to know more about CSP, you can check these articles :

• https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP
• https://developers.google.com/web/fundamentals/security/csp

4.3.1 CSP configuration compatible with iAdvize

To ensure no breaking in the iAdvize working on your website, we recommend you to update the "default-src" directive (the "default-src" serving as a fallback for all the other directives), and not each one of the CSP directives ("connect-src", "object-src", "script-src", "frame-src", "script-src", "style-src", "font-src", ...).

iAdvize use two different web protocols:

• HTTPS : https://*.iadvize.com
• WSS : wss://*.iadvize.com

Therefore you will need to bypass these two protocols.

Here an example:

Content-Security-Policy:
default-src 'unsafe-inline' https://*.iadvize.com wss://*.iadvize.com;

If you really can't rely on the "default-src" directive, we would recommend you to specify each one with a wildcard.

Here an example : 

Content-Security-Policy:
connect-src https://*.iadvize.com wss://*.iadvize.com;
frame-src https://*.iadvize.com;
img-src https://*.iadvize.com;
script-src 'unsafe-inline' https://*.iadvize.com;
style-src 'unsafe-inline' https://*.iadvize.com;

4.3.2 Example of advanced CSP configuration compatible with the iAdvize solution

Without the"Unsafe-inline" keyword
It is possible to call the 'script-src' and 'style-src' directives without the keyword 'unsafe-inline'. This action allows to make the CSP stricter.
If you use this option, the implementation of iAdvize tags must be adapted. We invite you to call iAdvize tags from external scripts loaded via the SRC attribute of the SCRIPT tag.
Example : <script defer type="text/javascript" src="https://halc.iadvize.com/iadvize.js?sid=XXXX"></script>

With the keyword "Nonce"
The nonce attribute allows you to "whitelist" certain inline script and style elements on your site. This avoids the use of the "Unsafe-inline" keyword which allows all inline script and style elements to run on your site.
Here an example :

Content-Security-Policy:
connect-src https://*.iadvize.com wss://*.iadvize.com wss://*.twilio.com;
frame-src https://*.iadvize.com;
img-src https://*.iadvize.com;
script-src https://*.iadvize.com 'nonce-5109fc35-8f6c-4e20-b987-d6eed7c73415';
style-src https://*.iadvize.com;

<script type="text/javascript" nonce="5109fc35-8f6c-4e20-b987-d6eed7c73415"> 
// iAdvize Javascript main tag 
</script>

Make sure that the hash used to list your authorized resources is auto-generated and not predictable by a third party.

5. Compatible OS with iAdvize mobile app 

First things first, please download the latest mobile version app on the App Store or on the Play Store according to the operating system you are using.

The iAdvize mobile application is compatible with the following OS:

• Apple iOS 15 and more
• Android 7 and more

6. Technical requirements for iAdvize mobile SDK integration

The iAdvize mobile SDK described in this page (https://developers.iadvize.com/documentation/mobile-sdk#mobile-sdk) is compatible with these following OS:

• Apple iOS 15 and more
• Android 7.0 (API 24) and above

7. Bandwidth requirement for iAdvize users

In order to guarantee a smooth use of the iAdvize platform, we advise you a minimum bandwidth on agents internet connection.

These values are for one agent and depend on the channel used.

• Chat/Call/Social :
  
  Download :

  • average : 0.5 Mbps
  • max : 1,5 Mbps

  Upload :

  • average : 0.5 Mbps
  • max : 1,5 Mbps

Note : We advise you to use the maximal value in your network configuration and then multiply it with the number of agents using the iAdvize solution.
 
Regarding the mirroring/cobrowsing case between agents and visitors, the display time of visitors pages may vary from few second to dozens of seconds due to the websites weight and visitor internet speed connection.