Requirements for Using Appcues

There are three things you need in order to use Appcues:

  1. A web application that your users can access using a web browser.
  2. The ability to install a snippet of code into that application.
  3. Google Chrome (for authoring). Don't worry, we support a wide range of browsers for your end users (see more below).

Most websites will fit these requirements, but keep reading if you have additional questions or concerns.

Network Connectivity

Your application must be accessible over the internet by a URL. If you're not sure, you can use to test your site out.

Browser Support

Creating Appcues flows:

Google Chrome is the only browser we support for authoring (or creating your flows). To create your flows you'll need to use the  Appcues Chrome Extension which will allow you to create flows on your application.

Viewing Appcues flows:

Our Javascript SDK is designed to cover every modern browser as well as the more popular legacy browsers.

  • Most versions of Chrome, Safari, Firefox and Edge
  • Internet Explorer 11

Special exceptions:

Special Limitations

In addition to the above, Appcues does not work particularly well on web applications:

  • that are composed of many iframes. Not sure what an iframe is? Learn more here!
  • that rely on elements in a "shadow dom". This affects tooltips and hotspots not modals and slideouts
  • where the URL does not change as the user navigates
  • built on Magento platform are built using Polymer or use prototype.js
  • is a progressive webapp or desktop application
  • that use Material UI Select
    • Instead enable native prop select. Otherwise the Material UI component won’t let the click event access and work with other libraries. However, the same behavior doesn’t apply for Select’s items, so events will work on items as expected even without the native prop enabled, they just won’t work on the Select’s wrapper.
  • When you’re trying to build a flow or event on a dialog that uses  Focus trap APIs, inputs in the builder can’t be focused, making the builder unusable. This is due to the API’s aggressive focus handling, which is considered an accessibility feature. Note that setting those configs affects accessibility on your site (not Appcues content) since focus will no longer be trapped within the dialog in question
    • for Material-UI’s unstable TrapFocus API, it could be overridden on your site by setting disableEnforceFocus to true.
    • for MS Fabric’s (now also named as Fluent-UI) Accessible Popup props, it could be overridden on your site by setting isClickableOutsideFocusTrap to true and forceFocusInsideTrap to false.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.